philipp/stationslauf
1
0
Fork 0
Code Issues 24 Pull Requests Actions Packages Projects Releases Wiki Activity

Write intro text "don't panic" and concrete next steps. Maybe even dynamic with what's missing #6

New Issue
Open
opened 2025-04-07 23:07:00 +02:00 by philipp · 1 comment
philipp commented 2025-04-07 23:07:00 +02:00
Owner
Copy Link
No description provided.
hannes commented 2025-04-13 18:32:37 +02:00
Collaborator
Copy Link

"Don't panic" in big letters at the center is a good start. :)

Build the Start-page in a way, that it guides the workflow:

  1. separate workflow into three tabs: ratras-setup, ratras-run, ratras-scoring
  2. show the current state of the ratras-setup: number of stations; list of routes (with names and number of stations); Number of Teams. Put an add-button for each of those stats.
  3. the ratras-run tab might want this kind of information: List of stations with the last time you heard of them. List of teams (categorized by routes) with the last time you heard of them. All lists ordered by the last time you heard of them.
  4. the ratras-score tab shows a table for each route with option to easily fill in scores, shows high scores and maybe export as csv
"Don't panic" in big letters at the center is a good start. :) Build the Start-page in a way, that it guides the workflow: 1. separate workflow into three tabs: ratras-setup, ratras-run, ratras-scoring 2. show the current state of the **ratras-setup**: number of stations; list of routes (with names and number of stations); Number of Teams. Put an add-button for each of those stats. 3. the **ratras-run** tab might want this kind of information: List of stations with the last time you heard of them. List of teams (categorized by routes) with the last time you heard of them. All lists ordered by the last time you heard of them. 4. the **ratras-score** tab shows a table for each route with option to easily fill in scores, shows high scores and maybe export as csv
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
after-event
next
ui
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hannes marie philipp
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: philipp/stationslauf#6
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?