From b8f6f2a1ba6743e735420a200c8939d59103b844 Mon Sep 17 00:00:00 2001 From: Sabine Maennel <5292683+sabinem@users.noreply.github.com> Date: Fri, 23 Oct 2026 16:14:47 +0200 Subject: [PATCH 1/5] docs: add content to pages --- docs/src/participant/member-overview.md | 39 +++++++++++++++++++++++-- docs/src/participant/member-projects.md | 14 +++++++++ 2 files changed, 51 insertions(+), 2 deletions(-) diff --git a/docs/src/participant/member-overview.md b/docs/src/participant/member-overview.md index 23b63b7b..d50e1b55 100644 --- a/docs/src/participant/member-overview.md +++ b/docs/src/participant/member-overview.md @@ -1,6 +1,41 @@ # Overview -The first page of a hackathon: its dates, the phase it is in, what you can do -right now, and your team. +:::{admonition} Participant's Overview + +This is page provides orientation to you about: + +- [the hackathon you are in](#your-hackathon): start and end data, number of participants +- [what you can currently do](#what-you-can-do): provides direct link to the activities that are open + +It might also show: + +- [the phase you are in](#phases): if the hackathon has defined phases +- [the team you are in](#team): in case you have already been assigned to a team. +- [the projects in the hackathon](#projects): in case the hackathon has already approved projects + +::: ![The Overview page of a hackathon, as a participant sees it](../static/screenshots/member-overview.png) + + +## Your hackathon + +- How many participants it has +- Start and end time + +## What you can do + +Not all hackathons have phases. Phases are just information for an orientation of where you are in the hackathon, see [timeline](member-timeline.md) + +## Phases + +Not all hackathons have phases. Phases are just information for an orientation of where you are in the hackathon, see [timeline](member-timeline.md) + +## Your team + +In case you have already been assigned to a team, you will see this assignment here + +## Projects + +In case projects have been already defined you can also see the number of projects and directly [access them](member-projects.md) from here. + diff --git a/docs/src/participant/member-projects.md b/docs/src/participant/member-projects.md index f5d041ea..ae49f507 100644 --- a/docs/src/participant/member-projects.md +++ b/docs/src/participant/member-projects.md @@ -1,5 +1,19 @@ # Projects +:::{admonition} The hackagons' Projects + +Here you can see all the projects participants can work on during the hackagom + +- [the hackathon you are in](#your-hackathon) +- [what you can currently do](#what-you-can-do) + +It might also show: + +- [A button to express your preferences](#preferences): this button is available when the hackathon owners decide so +- [the team you are in](#team): in case you have already been assigned to a team. + +::: + The hackathon's projects, and, while proposing is open, where you propose your own. From 46521abae41afa226911efd81e8656fe0f5c8247 Mon Sep 17 00:00:00 2001 From: Sabine Maennel <5292683+sabinem@users.noreply.github.com> Date: Fri, 23 Oct 2026 21:19:43 +0200 Subject: [PATCH 2/5] docs: describe every sidebar page, with links between them Each page opens with a box listing its sections, and what only appears sometimes, then short bullets that link to the related owner and participant pages. Written from what the pages show today. The Settings table follows the current voting flow: close voting by switching it off, make the results final on Manage Voting, then publish them. Jury categories are no longer mentioned there, since the app cannot create them. --- docs/src/owner/manage-forms.md | 33 ++++++++++++- docs/src/owner/manage-invites.md | 31 +++++++++++- docs/src/owner/manage-pages.md | 22 ++++++++- docs/src/owner/manage-participants.md | 34 ++++++++++++- docs/src/owner/manage-projects.md | 29 ++++++++++- docs/src/owner/manage-public.md | 22 ++++++++- docs/src/owner/manage-settings.md | 35 ++++++++----- docs/src/owner/manage-submissions.md | 25 +++++++++- docs/src/owner/manage-teams.md | 54 ++++++++++++++++++++- docs/src/owner/manage-timeline.md | 26 ++++++++-- docs/src/owner/manage-tracks.md | 25 ++++++++-- docs/src/owner/manage-voting.md | 39 ++++++++++++++- docs/src/participant/member-overview.md | 43 ++++++++++------ docs/src/participant/member-participants.md | 28 ++++++++++- docs/src/participant/member-projects.md | 39 +++++++++++---- docs/src/participant/member-results.md | 19 +++++++- docs/src/participant/member-submissions.md | 26 +++++++++- docs/src/participant/member-teams.md | 23 ++++++++- docs/src/participant/member-timeline.md | 17 ++++++- docs/src/participant/member-voting.md | 20 +++++++- 20 files changed, 526 insertions(+), 64 deletions(-) diff --git a/docs/src/owner/manage-forms.md b/docs/src/owner/manage-forms.md index 97a52e8c..1b3ea03b 100644 --- a/docs/src/owner/manage-forms.md +++ b/docs/src/owner/manage-forms.md @@ -1,5 +1,36 @@ # Manage Forms -The questions people answer when they register, and their answers. +:::{admonition} Owner's Manage Forms + +The questions people answer when they register. It shows: + +- [Registration form](#registration-form): the questions, in order +- [A question](#a-question): its type, options and settings + +It might also show: + +- [Answers](#answers): once someone has answered + +::: ![The Manage Forms page of a hackathon, as its owner sees it](../static/screenshots/manage-forms.png) + +## Registration form + +- **New question**; **Edit** and **Delete** per question. +- Once people have answered, type, options and **Required** are locked, and + deleting a question discards its answers. + +## A question + +- **Key**, **Question**, **Answer type**, **Position**, **Required**. +- **Show answers to participants**: answers are shared on + [Participants](../participant/member-participants.md). +- **Options** for choice questions, one per line. + +## Answers + +- **See the answers**: per question, who answered and what. +- Each person's answers are also on + [Manage Participants](manage-participants.md). +- Answers help you form teams, see [Manage Teams](manage-teams.md). diff --git a/docs/src/owner/manage-invites.md b/docs/src/owner/manage-invites.md index 074b0d20..bf61bb75 100644 --- a/docs/src/owner/manage-invites.md +++ b/docs/src/owner/manage-invites.md @@ -1,6 +1,33 @@ # Invitations -Only in a private hackathon: the links that let invited people see it and ask to -join. +:::{admonition} Owner's Invitations + +The links that let people into a private hackathon. Only for private hackathons. +It shows: + +- [Live links](#live-links): links that work, to copy or revoke +- [New link](#new-link): create another one + +It might also show: + +- [No longer working](#no-longer-working): revoked and expired links + +::: ![The Invitations page of a hackathon, as its owner sees it](../static/screenshots/manage-invites.png) + +## Live links + +- Copy a link into an email; **Revoke** it if it spreads. +- Someone with a valid link joins straight away, without the waitlist. +- Links work only while registration is open, see + [Settings](manage-settings.md). + +## New link + +- An optional note on who it is for; **Create link**. +- A link stops working when the hackathon ends. + +## No longer working + +- Revoked or expired links, for reference. diff --git a/docs/src/owner/manage-pages.md b/docs/src/owner/manage-pages.md index ce053514..9fb1bf2d 100644 --- a/docs/src/owner/manage-pages.md +++ b/docs/src/owner/manage-pages.md @@ -1,6 +1,24 @@ # Manage Pages -The hackathon's own pages, such as rules or a schedule, which participants find -in the menu. +:::{admonition} Owner's Manage Pages + +The hackathon's own pages, such as rules or a schedule. It shows: + +- [Pages](#pages): every page, in menu order +- [A page](#a-page): title, visibility and content + +::: ![The Manage Pages page of a hackathon, as its owner sees it](../static/screenshots/manage-pages.png) + +## Pages + +- Drag or use the arrows to change the order in the menu. +- The eye shows or hides a page for participants. +- **View** shows it as participants see it; **Edit** changes it. + +## A page + +- **New page**: **Title**, **Visible to participants**, **Content** in Markdown. +- Visible pages appear in every participant's menu. +- **Delete this page**. diff --git a/docs/src/owner/manage-participants.md b/docs/src/owner/manage-participants.md index 2ffb9147..d89fd21b 100644 --- a/docs/src/owner/manage-participants.md +++ b/docs/src/owner/manage-participants.md @@ -1,5 +1,37 @@ # Manage Participants -Everyone who registered, and the people waiting for your approval. +:::{admonition} Owner's Manage Participants + +Everyone who registered. It shows: + +- [Participants](#participants): the roster, with search and CSV download +- [A person](#a-person): answers, teams, and what you can change + +It might also show: + +- [Waitlist](#waitlist): people waiting for your approval + +::: ![The Manage Participants page of a hackathon, as its owner sees it](../static/screenshots/manage-participants.png) + +## Participants + +- How many there are, who has no email address, who answered the + [registration form](manage-forms.md). +- **Download CSV**: everyone, waitlist included. +- **Manage** opens a person. + +## Waitlist + +- On a public hackathon, everyone who registers waits here. +- **Review** opens the person, so you can approve or decline them. +- Only owners see the waitlist. + +## A person + +- All registration answers, including those not shared. +- Their teams, see [Manage Teams](manage-teams.md). +- **Approve** or **Decline** someone waiting. +- **Make owner** / **Remove owner**. +- **Remove from hackathon**; for an owner, remove the owner role first. diff --git a/docs/src/owner/manage-projects.md b/docs/src/owner/manage-projects.md index eace8e93..41a4f15c 100644 --- a/docs/src/owner/manage-projects.md +++ b/docs/src/owner/manage-projects.md @@ -1,5 +1,32 @@ # Manage Projects -Every project, including proposals waiting for your review. +:::{admonition} Owner's Manage Projects + +Every project, whatever its status. It shows: + +- [Projects by status](#projects-by-status): approved, awaiting review, rejected +- [Review](#review): approve or reject a project +- [New project](#new-project): add one yourself + +::: ![The Manage Projects page of a hackathon, as its owner sees it](../static/screenshots/manage-projects.png) + +## Projects by status + +- Tabs **Approved**, **Awaiting review**, **Rejected**. +- **Download CSV**: all projects. +- **Review** or **Edit** per project. + +## Review + +- **Approve**, **Reject** (with an optional reason), **Revoke approval** or + **Reconsider**. +- Only approved projects appear on [Projects](../participant/member-projects.md) + and on [Manage Teams](manage-teams.md). + +## New project + +- **New Project**: the same form participants use to propose. +- Participants propose only while you allow it, see + [Settings](manage-settings.md). diff --git a/docs/src/owner/manage-public.md b/docs/src/owner/manage-public.md index a1bb3f11..b2ca28a0 100644 --- a/docs/src/owner/manage-public.md +++ b/docs/src/owner/manage-public.md @@ -1,6 +1,24 @@ # Manage Public Page -The hackathon as everyone outside it sees it: its name, dates, picture and -description, with a preview beside the fields. +:::{admonition} Owner's Manage Public Page + +The hackathon as everyone outside it sees it. It shows: + +- [The form](#the-form): name, visibility, dates, logo and description +- [The preview](#the-preview): what visitors will see + +::: ![The Manage Public Page page of a hackathon, as its owner sees it](../static/screenshots/manage-public.png) + +## The form + +- **Name**, **Visibility** (public or private), **Starts at**, **Ends at**, + **Logo URL**, **Description**. +- Private hackathons are reached through [Invitations](manage-invites.md). +- Dates can be changed but not removed once set. +- **Save changes** returns to [Settings](manage-settings.md). + +## The preview + +- Updates as you type. diff --git a/docs/src/owner/manage-settings.md b/docs/src/owner/manage-settings.md index 9ff5ebdb..76b6fa5e 100644 --- a/docs/src/owner/manage-settings.md +++ b/docs/src/owner/manage-settings.md @@ -1,6 +1,17 @@ # Settings -Settings is the first page under **Manage Hackathon** in your hackathon's menu. +:::{admonition} Owner's Settings + +The first page under **Manage Hackathon**. It shows: + +- [What participants can do](#what-participants-can-do): the checkboxes that + steer the hackathon +- **Where the hackathon is**: the current and next phase, see + [Manage Timeline](manage-timeline.md) +- **Tracks**: optional, see [Manage Tracks](manage-tracks.md) +- **Manage**: a tile for every other page under **Manage Hackathon** + +::: ![The Settings page of a hackathon, as its owner sees it](../static/screenshots/manage-settings.png) @@ -18,14 +29,14 @@ The checkboxes are grouped into steps, in the order a hackathon usually runs. Some steps are optional, and some only point you to the page where you prepare the next one. Moving the hackathon to another phase never changes them. -| Step | Checkbox | When it is on, participants can … | Good to know | -| ---------------------- | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 1. Register | Open registration | join the hackathon. On a public hackathon they wait until you approve them; on a private one, a valid invitation lets them straight in. | While it is off, invitation links don't work either. Nobody can join once the end date has passed. See [Manage Forms](manage-forms.md), [Invitations](manage-invites.md) and [Manage Participants](manage-participants.md). | -| 2. Projects | Participants can propose projects | propose projects for you to review. | Optional: leave it off if you add all projects yourself. See [Manage Projects](manage-projects.md) and [Projects](../participant/member-projects.md). | -| 3. Project preferences | Participants can voice preferences | mark the projects they would like to work on. | Turning it off freezes the preferences as they are. See [Projects](../participant/member-projects.md). | -| 4. Team assignments | — | — | You form the teams. Participants don't see them until the next step. See [Manage Teams](manage-teams.md). | -| 5. Hacking starts | Participants can see teams | see the teams and who is on them. | While it is off, participants can't see even their own team. See [Teams](../participant/member-teams.md). | -| | Participants can submit for their team | hand in work for their team's project. | Only people on a team can submit. Turning it off stops new submissions, but a team can still finalize a draft it has started. See [Manage Submissions](manage-submissions.md) and [Submissions](../participant/member-submissions.md). | -| 6. Set up voting | — | — | Create the vote categories and decide who votes in them. See [Manage Voting](manage-voting.md). | -| 7. Voting starts | Participants can vote | vote, and see every team's submissions instead of only their own team's. | This opens all vote categories at once. Only its jury votes in a jury category, and nobody can vote for their own team. See [Voting](../participant/member-voting.md). | -| 8. Publish results | Publish results | see the vote results. | There is no separate step to publish a single result: everything recorded becomes visible the moment this is on. You always see the results yourself. See [Manage Voting](manage-voting.md) and [Results](../participant/member-results.md). | +| Step | Checkbox | When it is on, participants can … | Good to know | +| ---------------------- | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1. Register | Open registration | join the hackathon. On a public hackathon they wait until you approve them; on a private one, a valid invitation lets them straight in. | While it is off, invitation links don't work either. Nobody can join once the end date has passed. See [Manage Forms](manage-forms.md), [Invitations](manage-invites.md) and [Manage Participants](manage-participants.md). | +| 2. Projects | Participants can propose projects | propose projects for you to review. | Optional: leave it off if you add all projects yourself. See [Manage Projects](manage-projects.md) and [Projects](../participant/member-projects.md). | +| 3. Project preferences | Participants can voice preferences | mark the projects they would like to work on. | Turning it off freezes the preferences as they are. See [Projects](../participant/member-projects.md). | +| 4. Team assignments | — | — | You form the teams. Participants don't see them until the next step. See [Manage Teams](manage-teams.md). | +| 5. Hacking starts | Participants can see teams | see the teams and who is on them. | While it is off, participants can't see even their own team. See [Teams](../participant/member-teams.md). | +| | Participants can submit for their team | hand in work for their team's project. | Only people on a team can submit. Turning it off stops new submissions, but a team can still finalize a draft it has started. See [Manage Submissions](manage-submissions.md) and [Submissions](../participant/member-submissions.md). | +| 6. Set up voting | — | — | Create the vote categories and decide who votes in them. See [Manage Voting](manage-voting.md). | +| 7. Voting starts | Participants can vote | vote, and see every team's submissions instead of only their own team's. | This opens all vote categories at once, and nobody can vote for their own team. Switch it off to close voting before you make the results final. See [Manage Voting](manage-voting.md) and [Voting](../participant/member-voting.md). | +| 8. Publish results | Publish results | see the vote results. | Make the results final on [Manage Voting](manage-voting.md) first; this then shows them. You always see the results yourself. See [Results](../participant/member-results.md). | diff --git a/docs/src/owner/manage-submissions.md b/docs/src/owner/manage-submissions.md index 2a13da30..88d56c48 100644 --- a/docs/src/owner/manage-submissions.md +++ b/docs/src/owner/manage-submissions.md @@ -1,5 +1,28 @@ # Manage Submissions -Every team and where it stands with its submission. +:::{admonition} Owner's Manage Submissions + +Every team and where it stands with its work. It shows: + +- [Status](#status): whether submitting is open +- [Teams](#teams): each team's entry and drafts + +::: ![The Manage Submissions page of a hackathon, as its owner sees it](../static/screenshots/manage-submissions.png) + +## Status + +- **Submissions are open** or **closed**; change it on + [Settings](manage-settings.md). + +## Teams + +- Tabs **All**, **No submission**, **Draft only**, **Final**; search by team, + project or person. +- **Download CSV**: all teams. +- Per team: members, the entry, its version and who submitted it; earlier + versions folded away. +- Read-only: teams hand in and finalize themselves on + [Submissions](../participant/member-submissions.md). +- No teams yet: **Set up teams** leads to [Manage Teams](manage-teams.md). diff --git a/docs/src/owner/manage-teams.md b/docs/src/owner/manage-teams.md index e2aef5de..c4e847f0 100644 --- a/docs/src/owner/manage-teams.md +++ b/docs/src/owner/manage-teams.md @@ -1,5 +1,57 @@ # Manage Teams -Forming the teams and deciding who is on which. +:::{admonition} Owner's Manage Teams + +Where you form the teams. It shows: + +- [Projects](#projects): each approved project with its teams +- [Unassigned](#unassigned): confirmed participants without a team +- [Filters and cards](#filters-and-cards): registration answers and preferences +- [Spreadsheet](#spreadsheet): download and upload a CSV + +It might also show: + +- [Teams are fixed](#teams-are-fixed): once teams are published or work is + handed in + +::: ![The Manage Teams page of a hackathon, as its owner sees it](../static/screenshots/manage-teams.png) + +## Projects + +- One card per [approved project](manage-projects.md), with **N want in** and + its teams. +- **+ Add Team**; rename or delete a team. +- Drag people between teams. + +## Unassigned + +- Filter by registration answer or preferred project; **Reset filters**. + +## Filters and cards + +- **Registration questions**: short names, filters and **Show on cards**, see + [Manage Forms](manage-forms.md). +- **Project preferences**: what participants chose on + [Projects](../participant/member-projects.md#preferences). +- **Find a person** searches the page. + +## Spreadsheet + +- **Download CSV**: everyone with preferences and answers. +- Edit the `project` and `team` columns, then **Upload CSV**; it replaces all + teams. +- **How assignment works** explains the format. + +## Saving + +- Nothing is stored until **Save**; **Discard** drops your changes. +- Saving deletes empty teams. +- Participants see the teams only once you let them, see + [Settings](manage-settings.md). + +## Teams are fixed + +- Once teams are published or a team has handed in work: no upload, no deleting + teams. Moving people, renaming and adding teams still work. diff --git a/docs/src/owner/manage-timeline.md b/docs/src/owner/manage-timeline.md index d865c637..77441362 100644 --- a/docs/src/owner/manage-timeline.md +++ b/docs/src/owner/manage-timeline.md @@ -1,6 +1,13 @@ # Manage Timeline -Adding, editing and removing phases. It appears once the hackathon has a phase. +:::{admonition} Owner's Manage Timeline + +The hackathon's phases. Appears once the hackathon has a phase. It shows: + +- [Phases](#phases): each phase with its dates and status +- [A phase](#a-phase): add, edit or delete one + +::: ![The Manage Timeline page of a hackathon, as its owner sees it](../static/screenshots/manage-timeline.png) @@ -11,6 +18,17 @@ participants can do. That is decided on [Settings](manage-settings.md). ::: -Phases show participants where the hackathon stands. Each has a title, a -description, and a start and an end time. Participants see them on the -[Timeline](../participant/member-timeline.md). +## Phases + +- Status per phase: **Completed**, **In progress**, **Upcoming** or **Current + phase**. +- **Make current** / **Clear current phase** moves the marker; so does + [Settings](manage-settings.md). +- Participants see the phases on [Timeline](../participant/member-timeline.md). + +## A phase + +- **Add phase**: name and description, then its dates. +- **Starts** and **Ends**: both or neither; once set they can be changed but not + removed. +- **Delete this phase**. diff --git a/docs/src/owner/manage-tracks.md b/docs/src/owner/manage-tracks.md index 9f04dbbd..d5122134 100644 --- a/docs/src/owner/manage-tracks.md +++ b/docs/src/owner/manage-tracks.md @@ -1,15 +1,30 @@ # Manage Tracks -Adding, changing and removing tracks. It appears once the hackathon has a track. +:::{admonition} Owner's Manage Tracks + +The hackathon's tracks. Appears once the hackathon has a track. It shows: + +- [Tracks](#tracks): each track with its description +- [A track](#a-track): add, edit or delete one + +::: ![The Manage Tracks page of a hackathon, as its owner sees it](../static/screenshots/manage-tracks.png) :::{admonition} Tracks are optional -Hackathons without tracks are perfectly fine. +Hackathons without tracks are perfectly fine. Add the first one on +[Settings](manage-settings.md). ::: -Tracks group projects, for example by theme. Once a hackathon has a track, -**Manage Tracks** appears in the menu, where you add tracks and edit their -descriptions. +## Tracks + +- Tracks group projects, for example by theme. +- A project picks its track when it is proposed or edited, see + [Manage Projects](manage-projects.md). + +## A track + +- **New track**: name and description. +- **Delete this track**: its projects stay, without a track. diff --git a/docs/src/owner/manage-voting.md b/docs/src/owner/manage-voting.md index 2cf35650..c6fa7564 100644 --- a/docs/src/owner/manage-voting.md +++ b/docs/src/owner/manage-voting.md @@ -1,5 +1,42 @@ # Manage Voting -Vote categories, who votes in them, and the results. +:::{admonition} Owner's Manage Voting + +Vote categories and results. It shows: + +- [How voting works](#how-voting-works): the four steps and where each stands +- [Categories](#categories): what participants vote on +- [Count so far](#count-so-far): the live tally, for owners only + +It might also show: + +- [Final results](#final-results): once you make the results final + +::: ![The Manage Voting page of a hackathon, as its owner sees it](../static/screenshots/manage-voting.png) + +## How voting works + +1. Set up the categories. +2. Open voting, then close it: **Participants can vote** on + [Settings](manage-settings.md). +3. Make the results final, here. +4. Publish them: **Publish results** on [Settings](manage-settings.md). + +## Categories + +- **New category**: name, description and how people vote: **Single choice** + (pick one) or **Points** (spread a budget, 10 by default). +- **Edit** and **Delete** until someone has voted in it; then it is **Locked**. +- Participants vote on [Voting](../participant/member-voting.md). + +## Count so far + +- The ranking per category as votes come in; participants don't see it. +- **Make results final**: only once voting is closed; it cannot be undone. + +## Final results + +- Participants see them on [Results](../participant/member-results.md) once you + publish them. diff --git a/docs/src/participant/member-overview.md b/docs/src/participant/member-overview.md index d50e1b55..dc797326 100644 --- a/docs/src/participant/member-overview.md +++ b/docs/src/participant/member-overview.md @@ -2,40 +2,55 @@ :::{admonition} Participant's Overview -This is page provides orientation to you about: +The first page of a hackathon. It shows: -- [the hackathon you are in](#your-hackathon): start and end data, number of participants -- [what you can currently do](#what-you-can-do): provides direct link to the activities that are open +- [Your hackathon](#your-hackathon): its dates and number of participants +- [What you can do](#what-you-can-do): links to everything that is open now +- [Your team](#your-team): your team, or how to find one It might also show: -- [the phase you are in](#phases): if the hackathon has defined phases -- [the team you are in](#team): in case you have already been assigned to a team. -- [the projects in the hackathon](#projects): in case the hackathon has already approved projects +- [The current phase](#the-current-phase): if the hackathon has phases +- [Projects](#projects): once projects are approved +- [About this hackathon](#about-this-hackathon): if the owners wrote a + description ::: ![The Overview page of a hackathon, as a participant sees it](../static/screenshots/member-overview.png) - ## Your hackathon -- How many participants it has -- Start and end time +- Start and end date, and how many participants it has. ## What you can do -Not all hackathons have phases. Phases are just information for an orientation of where you are in the hackathon, see [timeline](member-timeline.md) +- One link per activity the owners have opened: + [propose projects](member-projects.md#propose-a-project), + [choose preferred projects](member-projects.md#preferences), + [see teams](member-teams.md), [submit work](member-submissions.md), + [vote](member-voting.md), [see results](member-results.md). +- "Nothing is open right now" when the owners have opened nothing. +- On the waitlist the links stay closed until an owner approves you. -## Phases +## The current phase -Not all hackathons have phases. Phases are just information for an orientation of where you are in the hackathon, see [timeline](member-timeline.md) +- Name, dates, countdown and description of the phase that is running. +- Phases are for orientation only, see [Timeline](member-timeline.md). ## Your team -In case you have already been assigned to a team, you will see this assignment here +- Your team's members, its project and whether it has handed in work. +- **Submit your work** leads to [Submissions](member-submissions.md) while + submitting is open. +- Not on a team yet: **Browse the projects** leads to + [Projects](member-projects.md). ## Projects -In case projects have been already defined you can also see the number of projects and directly [access them](member-projects.md) from here. +- The number of approved projects, per track if there are tracks. +- **View all** leads to [Projects](member-projects.md). + +## About this hackathon +- The hackathon's description. diff --git a/docs/src/participant/member-participants.md b/docs/src/participant/member-participants.md index 1a17fcc3..27129f68 100644 --- a/docs/src/participant/member-participants.md +++ b/docs/src/participant/member-participants.md @@ -1,5 +1,31 @@ # Participants -Everyone taking part in the hackathon, with your own entry at the top. +:::{admonition} Participant's Participants + +Everyone taking part in the hackathon. It shows: + +- [All participants](#all-participants): with search, your own entry first +- [A participant's profile](#a-participants-profile): links, shared answers and + teams + +::: ![The Participants page of a hackathon, as a participant sees it](../static/screenshots/member-participants.png) + +## All participants + +- Search by name or role. +- Your own entry is at the top, marked **You**. +- **View** opens a profile; on your own entry it reads **View & edit**. + +## A participant's profile + +- Name, profile links and the date they joined. +- **Shared answers**: the registration answers they chose to share. +- **Teams**: their teams, once teams are published; each links to its + [team](member-teams.md). + +On your own profile: + +- **Edit answers** changes your registration answers. +- **Add your GitHub, LinkedIn or Renku link** leads to your account page. diff --git a/docs/src/participant/member-projects.md b/docs/src/participant/member-projects.md index ae49f507..a789fcba 100644 --- a/docs/src/participant/member-projects.md +++ b/docs/src/participant/member-projects.md @@ -1,20 +1,41 @@ # Projects -:::{admonition} The hackagons' Projects +:::{admonition} Participant's Projects -Here you can see all the projects participants can work on during the hackagom +The projects you can work on. It shows: -- [the hackathon you are in](#your-hackathon) -- [what you can currently do](#what-you-can-do) +- [Approved projects](#approved-projects): the projects of this hackathon It might also show: -- [A button to express your preferences](#preferences): this button is available when the hackathon owners decide so -- [the team you are in](#team): in case you have already been assigned to a team. +- [Propose a project](#propose-a-project): while the owners take proposals +- [Your proposals](#your-proposals): your proposals that are not approved yet +- [Preferences](#preferences): while the owners collect project preferences ::: -The hackathon's projects, and, while proposing is open, where you propose your -own. - ![The Projects page of a hackathon, as a participant sees it](../static/screenshots/member-projects.png) + +## Approved projects + +- Eight per page; each opens its details: description, track and who proposed + it. + +## Propose a project + +- **Propose a Project**: title, description, and a track if the hackathon has + tracks. +- An owner reviews it before it appears in the list, see + [Manage Projects](../owner/manage-projects.md). + +## Your proposals + +- Each with its status, for example **Rejected**, and the owner's reason. +- **Edit** while it is still waiting for review. + +## Preferences + +- **Prefer** marks a project you would like to work on; **★ Preferred** shows + you did. +- The owners use the preferences to form the teams, see + [Manage Teams](../owner/manage-teams.md). diff --git a/docs/src/participant/member-results.md b/docs/src/participant/member-results.md index c6dec1f4..b6195eff 100644 --- a/docs/src/participant/member-results.md +++ b/docs/src/participant/member-results.md @@ -1,5 +1,22 @@ # Results -The vote results. It appears once the owners let participants see them. +:::{admonition} Participant's Results + +The outcome of the voting. Appears once the owners publish the results. It +shows: + +- [Placings](#placings): per vote category +- [All entries](#all-entries): every team that entered + +::: ![The Results page of a hackathon, as a participant sees it](../static/screenshots/member-results.png) + +## Placings + +- Per category: the placed entries with medal and score. +- **View entry** opens the [team](member-teams.md) and its entry. + +## All entries + +- Every team that entered; yours is marked **Your team**. diff --git a/docs/src/participant/member-submissions.md b/docs/src/participant/member-submissions.md index c9149e2a..fbf93d68 100644 --- a/docs/src/participant/member-submissions.md +++ b/docs/src/participant/member-submissions.md @@ -1,5 +1,29 @@ # Submissions -Where your team hands in its work. +:::{admonition} Participant's Submissions + +Where your team hands in its work. It shows, for each of your teams: + +- [Hand in work](#hand-in-work): save a draft +- [Finalize](#finalize): make a version your team's entry +- [Earlier versions](#earlier-versions): everything handed in so far + +::: ![The Submissions page of a hackathon, as a participant sees it](../static/screenshots/member-submissions.png) + +## Hand in work + +- Only while the owners have submitting open, and only once you are on a + [team](member-teams.md). +- A link or notes; **Save draft**. Every draft is a new version. + +## Finalize + +- **Finalize this version** makes a draft your team's entry. +- Anyone on the team can do it, and it cannot be undone. +- The final entry is what others [vote](member-voting.md) on. + +## Earlier versions + +- All versions your team handed in, folded away. diff --git a/docs/src/participant/member-teams.md b/docs/src/participant/member-teams.md index 406e2d76..16c55e42 100644 --- a/docs/src/participant/member-teams.md +++ b/docs/src/participant/member-teams.md @@ -1,6 +1,25 @@ # Teams -The teams and who is on them. It appears once there are teams and the owners let -participants see them. +:::{admonition} Participant's Teams + +Who works on which project. Appears once teams exist and the owners publish +them. It shows: + +- [All teams](#all-teams): grouped by project +- [A team](#a-team): its members and its entry + +::: ![The Teams page of a hackathon, as a participant sees it](../static/screenshots/member-teams.png) + +## All teams + +- Teams grouped under their project; the project title links to its + [project](member-projects.md). +- Each team shows its members and its final entry, if it has one. + +## A team + +- Members, project and **Read the full proposal**. +- The team's final entry, or a note that it has none yet. +- Hand in your own team's work on [Submissions](member-submissions.md). diff --git a/docs/src/participant/member-timeline.md b/docs/src/participant/member-timeline.md index 588d7b3a..3d415b3d 100644 --- a/docs/src/participant/member-timeline.md +++ b/docs/src/participant/member-timeline.md @@ -1,6 +1,19 @@ # Timeline -The hackathon's phases with their dates, and which one is running now. It -appears once the hackathon has a phase. +:::{admonition} Participant's Timeline + +The hackathon's phases, for orientation. Appears once the hackathon has a phase. +It shows: + +- [Phases](#phases): every phase with its dates + +::: ![The Timeline page of a hackathon, as a participant sees it](../static/screenshots/member-timeline.png) + +## Phases + +- The current phase with its dates, countdown, description and what is open now; + **See the details** leads to the [Overview](member-overview.md). +- The other phases with their dates; the next one with a countdown. +- Phases don't open or close anything; the owners do that separately. diff --git a/docs/src/participant/member-voting.md b/docs/src/participant/member-voting.md index 7bf21bb6..8449c605 100644 --- a/docs/src/participant/member-voting.md +++ b/docs/src/participant/member-voting.md @@ -1,5 +1,23 @@ # Voting -Where you cast your votes. It appears while the owners have voting switched on. +:::{admonition} Participant's Voting + +Where you vote on the teams' final entries. Appears while the owners have voting +open. It shows: + +- [Categories](#categories): one ballot per category + +::: ![The Voting page of a hackathon, as a participant sees it](../static/screenshots/member-voting.png) + +## Categories + +- You vote once in each category, and your vote is final. +- **Single choice**: pick one entry. **Points**: spread your points across + entries. +- Your own team is not on the ballot. +- **View entry** opens a [team](member-teams.md) and its entry; votes you have + not submitted are lost. +- After voting the card shows what you chose. Results come later on + [Results](member-results.md). From 34ba3db1cb0e76208e36f4f302133d0f44635403 Mon Sep 17 00:00:00 2001 From: Sabine Maennel <5292683+sabinem@users.noreply.github.com> Date: Sat, 24 Oct 2026 07:44:34 +0200 Subject: [PATCH 3/5] docs: corrections --- docs/src/index.md | 36 ++++++++++----------- docs/src/owner/manage-forms.md | 3 +- docs/src/owner/manage-invites.md | 4 +-- docs/src/owner/manage-pages.md | 2 +- docs/src/owner/manage-participants.md | 2 +- docs/src/owner/manage-settings.md | 4 +-- docs/src/owner/manage-submissions.md | 8 ++--- docs/src/owner/manage-teams.md | 9 +++--- docs/src/owner/manage-timeline.md | 8 ++--- docs/src/owner/manage-voting.md | 6 ++-- docs/src/participant/member-participants.md | 4 +-- docs/src/participant/member-projects.md | 6 ++-- docs/src/participant/member-results.md | 2 +- docs/src/participant/member-submissions.md | 7 ++-- docs/src/participant/member-teams.md | 9 +++--- docs/src/participant/member-timeline.md | 20 ++++++++---- docs/src/participant/member-voting.md | 4 +-- 17 files changed, 73 insertions(+), 61 deletions(-) diff --git a/docs/src/index.md b/docs/src/index.md index 607a35ac..d8de7d19 100644 --- a/docs/src/index.md +++ b/docs/src/index.md @@ -4,22 +4,22 @@ Hackagon is the Swiss Data Science Center's platform for running hackathons. ## What is a hackathon on Hackagon? -On this platform a hackathon is: - -- an **event** that lasts one or several days; -- **run by** one or several **hackathon owners**; -- joined by **participants**, whose registrations the owners approve or reject; -- **public or private**; -- built around **projects**, which owners add or participants propose, and which - the owners approve or reject; -- worked on in **teams**, which the owners form from the participants' - registration answers and their project preferences; -- handed in as **submissions**: every member of a team can submit, submissions - are versioned, and one can be marked as final; other teams can see final - submissions; -- decided by **voting**, which the owners set up in categories: in each category - participants either pick one project or spread a budget of points across the - projects. +On this platform: + +- A hackathon is an **event** that lasts one or several days. +- It is **run by** one or several **hackathon owners**. +- **Participants** join it. The owners approve or reject their registrations. +- A hackathon is **public or private**. +- It is built around **projects**. Owners add projects or participants propose + them, and the owners approve or reject them. +- Participants work in **teams**. The owners form the teams from the + participants' registration answers and project preferences. +- Teams hand in **submissions**. Every team member can submit, submissions are + versioned, and one can be marked as final. Other teams can see final + submissions. +- **Voting** decides the outcome. The owners set it up in categories. In each + category participants either pick one project or spread a budget of points + across the projects. ## Roles @@ -38,11 +38,11 @@ This first version covers hackathon owners and participants. ## Limitations -- The platform is not a place for data and code to live; +- The platform is not a place for data and code to live. [Renku](https://renkulab.io/) is one such place. - The platform does not organize anything on site. To get help organizing a hackathon, email us at - [hackathon@datascience.ch](mailto:hackathon@datascience.ch); we offer + [hackathon@datascience.ch](mailto:hackathon@datascience.ch). We offer different packages. ```{toctree} diff --git a/docs/src/owner/manage-forms.md b/docs/src/owner/manage-forms.md index 1b3ea03b..41d3fa42 100644 --- a/docs/src/owner/manage-forms.md +++ b/docs/src/owner/manage-forms.md @@ -17,7 +17,8 @@ It might also show: ## Registration form -- **New question**; **Edit** and **Delete** per question. +- **New question** adds a question. **Edit** and **Delete** are next to each + question. - Once people have answered, type, options and **Required** are locked, and deleting a question discards its answers. diff --git a/docs/src/owner/manage-invites.md b/docs/src/owner/manage-invites.md index bf61bb75..172cb0bc 100644 --- a/docs/src/owner/manage-invites.md +++ b/docs/src/owner/manage-invites.md @@ -18,14 +18,14 @@ It might also show: ## Live links -- Copy a link into an email; **Revoke** it if it spreads. +- Copy a link into an email. **Revoke** it if it spreads. - Someone with a valid link joins straight away, without the waitlist. - Links work only while registration is open, see [Settings](manage-settings.md). ## New link -- An optional note on who it is for; **Create link**. +- Add an optional note on who it is for, then **Create link**. - A link stops working when the hackathon ends. ## No longer working diff --git a/docs/src/owner/manage-pages.md b/docs/src/owner/manage-pages.md index 9fb1bf2d..6f16d8fc 100644 --- a/docs/src/owner/manage-pages.md +++ b/docs/src/owner/manage-pages.md @@ -15,7 +15,7 @@ The hackathon's own pages, such as rules or a schedule. It shows: - Drag or use the arrows to change the order in the menu. - The eye shows or hides a page for participants. -- **View** shows it as participants see it; **Edit** changes it. +- **View** shows it as participants see it. **Edit** changes it. ## A page diff --git a/docs/src/owner/manage-participants.md b/docs/src/owner/manage-participants.md index d89fd21b..7e369abf 100644 --- a/docs/src/owner/manage-participants.md +++ b/docs/src/owner/manage-participants.md @@ -34,4 +34,4 @@ It might also show: - Their teams, see [Manage Teams](manage-teams.md). - **Approve** or **Decline** someone waiting. - **Make owner** / **Remove owner**. -- **Remove from hackathon**; for an owner, remove the owner role first. +- **Remove from hackathon**. For an owner, remove the owner role first. diff --git a/docs/src/owner/manage-settings.md b/docs/src/owner/manage-settings.md index 76b6fa5e..9e9cc0cb 100644 --- a/docs/src/owner/manage-settings.md +++ b/docs/src/owner/manage-settings.md @@ -31,7 +31,7 @@ the next one. Moving the hackathon to another phase never changes them. | Step | Checkbox | When it is on, participants can … | Good to know | | ---------------------- | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 1. Register | Open registration | join the hackathon. On a public hackathon they wait until you approve them; on a private one, a valid invitation lets them straight in. | While it is off, invitation links don't work either. Nobody can join once the end date has passed. See [Manage Forms](manage-forms.md), [Invitations](manage-invites.md) and [Manage Participants](manage-participants.md). | +| 1. Register | Open registration | join the hackathon. On a public hackathon they wait until you approve them. On a private one, a valid invitation lets them straight in. | While it is off, invitation links don't work either. Nobody can join once the end date has passed. See [Manage Forms](manage-forms.md), [Invitations](manage-invites.md) and [Manage Participants](manage-participants.md). | | 2. Projects | Participants can propose projects | propose projects for you to review. | Optional: leave it off if you add all projects yourself. See [Manage Projects](manage-projects.md) and [Projects](../participant/member-projects.md). | | 3. Project preferences | Participants can voice preferences | mark the projects they would like to work on. | Turning it off freezes the preferences as they are. See [Projects](../participant/member-projects.md). | | 4. Team assignments | — | — | You form the teams. Participants don't see them until the next step. See [Manage Teams](manage-teams.md). | @@ -39,4 +39,4 @@ the next one. Moving the hackathon to another phase never changes them. | | Participants can submit for their team | hand in work for their team's project. | Only people on a team can submit. Turning it off stops new submissions, but a team can still finalize a draft it has started. See [Manage Submissions](manage-submissions.md) and [Submissions](../participant/member-submissions.md). | | 6. Set up voting | — | — | Create the vote categories and decide who votes in them. See [Manage Voting](manage-voting.md). | | 7. Voting starts | Participants can vote | vote, and see every team's submissions instead of only their own team's. | This opens all vote categories at once, and nobody can vote for their own team. Switch it off to close voting before you make the results final. See [Manage Voting](manage-voting.md) and [Voting](../participant/member-voting.md). | -| 8. Publish results | Publish results | see the vote results. | Make the results final on [Manage Voting](manage-voting.md) first; this then shows them. You always see the results yourself. See [Results](../participant/member-results.md). | +| 8. Publish results | Publish results | see the vote results. | Make the results final on [Manage Voting](manage-voting.md) first. This checkbox then shows them. You always see the results yourself. See [Results](../participant/member-results.md). | diff --git a/docs/src/owner/manage-submissions.md b/docs/src/owner/manage-submissions.md index 88d56c48..7ce90bb5 100644 --- a/docs/src/owner/manage-submissions.md +++ b/docs/src/owner/manage-submissions.md @@ -13,16 +13,16 @@ Every team and where it stands with its work. It shows: ## Status -- **Submissions are open** or **closed**; change it on +- **Submissions are open** or **closed**. Change it on [Settings](manage-settings.md). ## Teams -- Tabs **All**, **No submission**, **Draft only**, **Final**; search by team, +- Tabs **All**, **No submission**, **Draft only**, **Final**. Search by team, project or person. - **Download CSV**: all teams. -- Per team: members, the entry, its version and who submitted it; earlier - versions folded away. +- Per team: members, the entry, its version and who submitted it. Earlier + versions are folded away. - Read-only: teams hand in and finalize themselves on [Submissions](../participant/member-submissions.md). - No teams yet: **Set up teams** leads to [Manage Teams](manage-teams.md). diff --git a/docs/src/owner/manage-teams.md b/docs/src/owner/manage-teams.md index c4e847f0..03cb2d15 100644 --- a/docs/src/owner/manage-teams.md +++ b/docs/src/owner/manage-teams.md @@ -22,12 +22,13 @@ It might also show: - One card per [approved project](manage-projects.md), with **N want in** and its teams. -- **+ Add Team**; rename or delete a team. +- **+ Add Team** adds a team. You can also rename or delete a team. - Drag people between teams. ## Unassigned -- Filter by registration answer or preferred project; **Reset filters**. +- Filter by registration answer or preferred project. **Reset filters** clears + them. ## Filters and cards @@ -40,13 +41,13 @@ It might also show: ## Spreadsheet - **Download CSV**: everyone with preferences and answers. -- Edit the `project` and `team` columns, then **Upload CSV**; it replaces all +- Edit the `project` and `team` columns, then **Upload CSV**. It replaces all teams. - **How assignment works** explains the format. ## Saving -- Nothing is stored until **Save**; **Discard** drops your changes. +- Nothing is stored until you **Save**. **Discard** drops your changes. - Saving deletes empty teams. - Participants see the teams only once you let them, see [Settings](manage-settings.md). diff --git a/docs/src/owner/manage-timeline.md b/docs/src/owner/manage-timeline.md index 77441362..5d0a4280 100644 --- a/docs/src/owner/manage-timeline.md +++ b/docs/src/owner/manage-timeline.md @@ -22,13 +22,13 @@ participants can do. That is decided on [Settings](manage-settings.md). - Status per phase: **Completed**, **In progress**, **Upcoming** or **Current phase**. -- **Make current** / **Clear current phase** moves the marker; so does - [Settings](manage-settings.md). +- **Make current** / **Clear current phase** moves the marker. You can also move + it on [Settings](manage-settings.md). - Participants see the phases on [Timeline](../participant/member-timeline.md). ## A phase - **Add phase**: name and description, then its dates. -- **Starts** and **Ends**: both or neither; once set they can be changed but not - removed. +- **Starts** and **Ends**: set both or neither. Once set, they can be changed + but not removed. - **Delete this phase**. diff --git a/docs/src/owner/manage-voting.md b/docs/src/owner/manage-voting.md index c6fa7564..5a4a51ae 100644 --- a/docs/src/owner/manage-voting.md +++ b/docs/src/owner/manage-voting.md @@ -28,13 +28,13 @@ It might also show: - **New category**: name, description and how people vote: **Single choice** (pick one) or **Points** (spread a budget, 10 by default). -- **Edit** and **Delete** until someone has voted in it; then it is **Locked**. +- **Edit** and **Delete** until someone has voted in it. Then it is **Locked**. - Participants vote on [Voting](../participant/member-voting.md). ## Count so far -- The ranking per category as votes come in; participants don't see it. -- **Make results final**: only once voting is closed; it cannot be undone. +- The ranking per category as votes come in. Participants don't see it. +- **Make results final** works only once voting is closed. It cannot be undone. ## Final results diff --git a/docs/src/participant/member-participants.md b/docs/src/participant/member-participants.md index 27129f68..82631fce 100644 --- a/docs/src/participant/member-participants.md +++ b/docs/src/participant/member-participants.md @@ -16,13 +16,13 @@ Everyone taking part in the hackathon. It shows: - Search by name or role. - Your own entry is at the top, marked **You**. -- **View** opens a profile; on your own entry it reads **View & edit**. +- **View** opens a profile. On your own entry it reads **View & edit**. ## A participant's profile - Name, profile links and the date they joined. - **Shared answers**: the registration answers they chose to share. -- **Teams**: their teams, once teams are published; each links to its +- **Teams**: their teams, once teams are published. Each links to its [team](member-teams.md). On your own profile: diff --git a/docs/src/participant/member-projects.md b/docs/src/participant/member-projects.md index a789fcba..1a4ffa7c 100644 --- a/docs/src/participant/member-projects.md +++ b/docs/src/participant/member-projects.md @@ -18,8 +18,8 @@ It might also show: ## Approved projects -- Eight per page; each opens its details: description, track and who proposed - it. +- Eight projects per page. Each opens its details: description, track and who + proposed it. ## Propose a project @@ -35,7 +35,7 @@ It might also show: ## Preferences -- **Prefer** marks a project you would like to work on; **★ Preferred** shows +- **Prefer** marks a project you would like to work on. **★ Preferred** shows you did. - The owners use the preferences to form the teams, see [Manage Teams](../owner/manage-teams.md). diff --git a/docs/src/participant/member-results.md b/docs/src/participant/member-results.md index b6195eff..c9dcc8c1 100644 --- a/docs/src/participant/member-results.md +++ b/docs/src/participant/member-results.md @@ -19,4 +19,4 @@ shows: ## All entries -- Every team that entered; yours is marked **Your team**. +- Every team that entered. Yours is marked **Your team**. diff --git a/docs/src/participant/member-submissions.md b/docs/src/participant/member-submissions.md index fbf93d68..5005f8d3 100644 --- a/docs/src/participant/member-submissions.md +++ b/docs/src/participant/member-submissions.md @@ -14,16 +14,17 @@ Where your team hands in its work. It shows, for each of your teams: ## Hand in work -- Only while the owners have submitting open, and only once you are on a +- Only while submitting is open for the hackathon, see [overview](member-overview.md), and only once you are on a [team](member-teams.md). -- A link or notes; **Save draft**. Every draft is a new version. +- Enter a link or notes, then click on **Save draft**. Every draft is a new version. ## Finalize - **Finalize this version** makes a draft your team's entry. - Anyone on the team can do it, and it cannot be undone. - The final entry is what others [vote](member-voting.md) on. +- There can be several final entries. The last one will be the one that counts for the team during voting. ## Earlier versions -- All versions your team handed in, folded away. +- All versions your team handed in are folded away. diff --git a/docs/src/participant/member-teams.md b/docs/src/participant/member-teams.md index 16c55e42..7ac7da15 100644 --- a/docs/src/participant/member-teams.md +++ b/docs/src/participant/member-teams.md @@ -6,7 +6,7 @@ Who works on which project. Appears once teams exist and the owners publish them. It shows: - [All teams](#all-teams): grouped by project -- [A team](#a-team): its members and its entry +- [A team](#a-team): its members, its project and its final entry ::: @@ -14,12 +14,13 @@ them. It shows: ## All teams -- Teams grouped under their project; the project title links to its +- Teams grouped under their project. The project title links to its [project](member-projects.md). - Each team shows its members and its final entry, if it has one. +- **View** opens [a team](#a-team). ## A team -- Members, project and **Read the full proposal**. -- The team's final entry, or a note that it has none yet. +- Its members, and its project with the full proposal. +- Its final entry, or a note that it has none yet. - Hand in your own team's work on [Submissions](member-submissions.md). diff --git a/docs/src/participant/member-timeline.md b/docs/src/participant/member-timeline.md index 3d415b3d..b3dba9b7 100644 --- a/docs/src/participant/member-timeline.md +++ b/docs/src/participant/member-timeline.md @@ -2,18 +2,26 @@ :::{admonition} Participant's Timeline -The hackathon's phases, for orientation. Appears once the hackathon has a phase. -It shows: +A hackathon can have phases, which show what happens when. This page appears +only if it has some. It shows: - [Phases](#phases): every phase with its dates +It might also show: + +- [The current phase](#the-current-phase): while a phase is running, with what + is open now + ::: ![The Timeline page of a hackathon, as a participant sees it](../static/screenshots/member-timeline.png) ## Phases -- The current phase with its dates, countdown, description and what is open now; - **See the details** leads to the [Overview](member-overview.md). -- The other phases with their dates; the next one with a countdown. -- Phases don't open or close anything; the owners do that separately. +- Every phase with its start and end date. The next one has a countdown. +- Phases don't open or close anything. The owners do that separately. + +## The current phase + +- Its dates, a countdown, its description and what is open now. +- **See the details** leads to the [Overview](member-overview.md). diff --git a/docs/src/participant/member-voting.md b/docs/src/participant/member-voting.md index 8449c605..9460c47a 100644 --- a/docs/src/participant/member-voting.md +++ b/docs/src/participant/member-voting.md @@ -17,7 +17,7 @@ open. It shows: - **Single choice**: pick one entry. **Points**: spread your points across entries. - Your own team is not on the ballot. -- **View entry** opens a [team](member-teams.md) and its entry; votes you have - not submitted are lost. +- **View entry** opens a [team](member-teams.md) and its entry. Votes you have + not submitted yet are lost. - After voting the card shows what you chose. Results come later on [Results](member-results.md). From bcd65a7f813b163adba5923cc41f8c653205f1c9 Mon Sep 17 00:00:00 2001 From: Sabine Maennel <5292683+sabinem@users.noreply.github.com> Date: Sat, 24 Oct 2026 08:06:44 +0200 Subject: [PATCH 4/5] docs: show app controls as labels, and say what to do with them Buttons, fields, tabs and badges are written as {guilabel} instead of bold, so the reader can tell what is on screen, and each action starts with a verb: click, tick, enter, choose. Clauses joined by semicolons are now separate sentences. --- docs/src/owner/index.md | 4 +-- docs/src/owner/manage-forms.md | 17 +++++------ docs/src/owner/manage-invites.md | 4 +-- docs/src/owner/manage-pages.md | 11 ++++--- docs/src/owner/manage-participants.md | 13 +++++---- docs/src/owner/manage-projects.md | 15 ++++++---- docs/src/owner/manage-public.md | 8 ++++-- docs/src/owner/manage-settings.md | 9 +++--- docs/src/owner/manage-submissions.md | 11 ++++--- docs/src/owner/manage-teams.md | 32 ++++++++++++--------- docs/src/owner/manage-timeline.md | 17 +++++------ docs/src/owner/manage-tracks.md | 5 ++-- docs/src/owner/manage-voting.md | 18 +++++++----- docs/src/participant/member-overview.md | 8 +++--- docs/src/participant/member-participants.md | 14 +++++---- docs/src/participant/member-projects.md | 13 +++++---- docs/src/participant/member-results.md | 5 ++-- docs/src/participant/member-submissions.md | 16 ++++++----- docs/src/participant/member-teams.md | 2 +- docs/src/participant/member-timeline.md | 2 +- docs/src/participant/member-voting.md | 8 +++--- 21 files changed, 131 insertions(+), 101 deletions(-) diff --git a/docs/src/owner/index.md b/docs/src/owner/index.md index 478b4867..835a97db 100644 --- a/docs/src/owner/index.md +++ b/docs/src/owner/index.md @@ -2,8 +2,8 @@ This guide is for hackathon owners: the people who set up and run a hackathon. -The pages under **Manage Hackathon** in a hackathon's menu, in the order they -appear there: +The pages under {guilabel}`Manage Hackathon` in a hackathon's menu, in the order +they appear there: ```{toctree} :maxdepth: 1 diff --git a/docs/src/owner/manage-forms.md b/docs/src/owner/manage-forms.md index 41d3fa42..45e527a5 100644 --- a/docs/src/owner/manage-forms.md +++ b/docs/src/owner/manage-forms.md @@ -17,21 +17,22 @@ It might also show: ## Registration form -- **New question** adds a question. **Edit** and **Delete** are next to each - question. -- Once people have answered, type, options and **Required** are locked, and - deleting a question discards its answers. +- Click {guilabel}`New question` to add a question. Click {guilabel}`Edit` or + {guilabel}`Delete` next to a question to change or remove it. +- Once people have answered, type, options and {guilabel}`Required` are locked, + and deleting a question discards its answers. ## A question -- **Key**, **Question**, **Answer type**, **Position**, **Required**. -- **Show answers to participants**: answers are shared on +- Enter the {guilabel}`Key`, {guilabel}`Question`, {guilabel}`Answer type` and + {guilabel}`Position`. Tick {guilabel}`Required` if everyone must answer. +- Tick {guilabel}`Show answers to participants` to share the answers on [Participants](../participant/member-participants.md). -- **Options** for choice questions, one per line. +- For choice questions, enter the {guilabel}`Options`, one per line. ## Answers -- **See the answers**: per question, who answered and what. +- Click {guilabel}`See the answers` to see, per question, who answered and what. - Each person's answers are also on [Manage Participants](manage-participants.md). - Answers help you form teams, see [Manage Teams](manage-teams.md). diff --git a/docs/src/owner/manage-invites.md b/docs/src/owner/manage-invites.md index 172cb0bc..3ec311d5 100644 --- a/docs/src/owner/manage-invites.md +++ b/docs/src/owner/manage-invites.md @@ -18,14 +18,14 @@ It might also show: ## Live links -- Copy a link into an email. **Revoke** it if it spreads. +- Copy a link into an email. Click {guilabel}`Revoke` if it spreads. - Someone with a valid link joins straight away, without the waitlist. - Links work only while registration is open, see [Settings](manage-settings.md). ## New link -- Add an optional note on who it is for, then **Create link**. +- Enter an optional note on who it is for, then click {guilabel}`Create link`. - A link stops working when the hackathon ends. ## No longer working diff --git a/docs/src/owner/manage-pages.md b/docs/src/owner/manage-pages.md index 6f16d8fc..50fc90f8 100644 --- a/docs/src/owner/manage-pages.md +++ b/docs/src/owner/manage-pages.md @@ -14,11 +14,14 @@ The hackathon's own pages, such as rules or a schedule. It shows: ## Pages - Drag or use the arrows to change the order in the menu. -- The eye shows or hides a page for participants. -- **View** shows it as participants see it. **Edit** changes it. +- Click the eye to show or hide a page for participants. +- Click {guilabel}`View` to see a page as participants do, or {guilabel}`Edit` + to change it. ## A page -- **New page**: **Title**, **Visible to participants**, **Content** in Markdown. +- Click {guilabel}`New page`, then enter a {guilabel}`Title` and the + {guilabel}`Content` in Markdown. Tick {guilabel}`Visible to participants` to + show it. - Visible pages appear in every participant's menu. -- **Delete this page**. +- Click {guilabel}`Delete this page` on a page's edit form to remove it. diff --git a/docs/src/owner/manage-participants.md b/docs/src/owner/manage-participants.md index 7e369abf..cada10bd 100644 --- a/docs/src/owner/manage-participants.md +++ b/docs/src/owner/manage-participants.md @@ -19,19 +19,20 @@ It might also show: - How many there are, who has no email address, who answered the [registration form](manage-forms.md). -- **Download CSV**: everyone, waitlist included. -- **Manage** opens a person. +- Click {guilabel}`Download CSV` to get everyone, waitlist included. +- Click {guilabel}`Manage` to open a person. ## Waitlist - On a public hackathon, everyone who registers waits here. -- **Review** opens the person, so you can approve or decline them. +- Click {guilabel}`Review` to open a person and approve or decline them. - Only owners see the waitlist. ## A person - All registration answers, including those not shared. - Their teams, see [Manage Teams](manage-teams.md). -- **Approve** or **Decline** someone waiting. -- **Make owner** / **Remove owner**. -- **Remove from hackathon**. For an owner, remove the owner role first. +- Click {guilabel}`Approve` or {guilabel}`Decline` for someone waiting. +- Click {guilabel}`Make owner` or {guilabel}`Remove owner` to change their role. +- Click {guilabel}`Remove from hackathon` to remove them. For an owner, remove + the owner role first. diff --git a/docs/src/owner/manage-projects.md b/docs/src/owner/manage-projects.md index 41a4f15c..621e02d0 100644 --- a/docs/src/owner/manage-projects.md +++ b/docs/src/owner/manage-projects.md @@ -14,19 +14,22 @@ Every project, whatever its status. It shows: ## Projects by status -- Tabs **Approved**, **Awaiting review**, **Rejected**. -- **Download CSV**: all projects. -- **Review** or **Edit** per project. +- Click the tabs {guilabel}`Approved`, {guilabel}`Awaiting review` and + {guilabel}`Rejected` to switch between statuses. +- Click {guilabel}`Download CSV` to get all projects as a spreadsheet. +- Click {guilabel}`Review` or {guilabel}`Edit` next to a project. ## Review -- **Approve**, **Reject** (with an optional reason), **Revoke approval** or - **Reconsider**. +- Click {guilabel}`Approve` or {guilabel}`Reject`. When you reject, you can give + a reason. {guilabel}`Revoke approval` and {guilabel}`Reconsider` undo a + decision. - Only approved projects appear on [Projects](../participant/member-projects.md) and on [Manage Teams](manage-teams.md). ## New project -- **New Project**: the same form participants use to propose. +- Click {guilabel}`New Project` to add one. It is the same form participants use + to propose. - Participants propose only while you allow it, see [Settings](manage-settings.md). diff --git a/docs/src/owner/manage-public.md b/docs/src/owner/manage-public.md index b2ca28a0..cd72b666 100644 --- a/docs/src/owner/manage-public.md +++ b/docs/src/owner/manage-public.md @@ -13,11 +13,13 @@ The hackathon as everyone outside it sees it. It shows: ## The form -- **Name**, **Visibility** (public or private), **Starts at**, **Ends at**, - **Logo URL**, **Description**. +- Enter the {guilabel}`Name`, {guilabel}`Starts at`, {guilabel}`Ends at`, + {guilabel}`Logo URL` and {guilabel}`Description`. Choose the + {guilabel}`Visibility`: public or private. - Private hackathons are reached through [Invitations](manage-invites.md). - Dates can be changed but not removed once set. -- **Save changes** returns to [Settings](manage-settings.md). +- Click {guilabel}`Save changes` to save and return to + [Settings](manage-settings.md). ## The preview diff --git a/docs/src/owner/manage-settings.md b/docs/src/owner/manage-settings.md index 9e9cc0cb..7f87e2c4 100644 --- a/docs/src/owner/manage-settings.md +++ b/docs/src/owner/manage-settings.md @@ -2,14 +2,15 @@ :::{admonition} Owner's Settings -The first page under **Manage Hackathon**. It shows: +The first page under {guilabel}`Manage Hackathon`. It shows: - [What participants can do](#what-participants-can-do): the checkboxes that steer the hackathon -- **Where the hackathon is**: the current and next phase, see +- {guilabel}`Where the hackathon is`: the current and next phase, see [Manage Timeline](manage-timeline.md) -- **Tracks**: optional, see [Manage Tracks](manage-tracks.md) -- **Manage**: a tile for every other page under **Manage Hackathon** +- {guilabel}`Tracks`: optional, see [Manage Tracks](manage-tracks.md) +- {guilabel}`Manage`: a tile for every other page under + {guilabel}`Manage Hackathon` ::: diff --git a/docs/src/owner/manage-submissions.md b/docs/src/owner/manage-submissions.md index 7ce90bb5..0fb16e1e 100644 --- a/docs/src/owner/manage-submissions.md +++ b/docs/src/owner/manage-submissions.md @@ -13,16 +13,19 @@ Every team and where it stands with its work. It shows: ## Status -- **Submissions are open** or **closed**. Change it on +- The page says {guilabel}`Submissions are open` or + {guilabel}`Submissions are closed`. Change it on [Settings](manage-settings.md). ## Teams -- Tabs **All**, **No submission**, **Draft only**, **Final**. Search by team, +- Click the tabs {guilabel}`All`, {guilabel}`No submission`, + {guilabel}`Draft only` and {guilabel}`Final` to filter. Search by team, project or person. -- **Download CSV**: all teams. +- Click {guilabel}`Download CSV` to get all teams. - Per team: members, the entry, its version and who submitted it. Earlier versions are folded away. - Read-only: teams hand in and finalize themselves on [Submissions](../participant/member-submissions.md). -- No teams yet: **Set up teams** leads to [Manage Teams](manage-teams.md). +- No teams yet: click {guilabel}`Set up teams` to go to + [Manage Teams](manage-teams.md). diff --git a/docs/src/owner/manage-teams.md b/docs/src/owner/manage-teams.md index 03cb2d15..e6005a91 100644 --- a/docs/src/owner/manage-teams.md +++ b/docs/src/owner/manage-teams.md @@ -20,34 +20,38 @@ It might also show: ## Projects -- One card per [approved project](manage-projects.md), with **N want in** and - its teams. -- **+ Add Team** adds a team. You can also rename or delete a team. +- One card per [approved project](manage-projects.md), with + {guilabel}`N want in` and its teams. +- Click {guilabel}`+ Add Team` to add a team. You can also rename or delete a + team. - Drag people between teams. ## Unassigned -- Filter by registration answer or preferred project. **Reset filters** clears - them. +- Filter by registration answer or preferred project. Click + {guilabel}`Reset filters` to clear them. ## Filters and cards -- **Registration questions**: short names, filters and **Show on cards**, see - [Manage Forms](manage-forms.md). -- **Project preferences**: what participants chose on +- {guilabel}`Registration questions`: give each question a short name and filter + by its answers. Tick {guilabel}`Show on cards` to show the answers on each + person. See [Manage Forms](manage-forms.md). +- {guilabel}`Project preferences`: what participants chose on [Projects](../participant/member-projects.md#preferences). -- **Find a person** searches the page. +- Enter a name in {guilabel}`Find a person` to search the page. ## Spreadsheet -- **Download CSV**: everyone with preferences and answers. -- Edit the `project` and `team` columns, then **Upload CSV**. It replaces all - teams. -- **How assignment works** explains the format. +- Click {guilabel}`Download CSV` to get everyone with their preferences and + answers. +- Edit the `project` and `team` columns, then click {guilabel}`Upload CSV`. It + replaces all teams. +- Click {guilabel}`How assignment works` for the format. ## Saving -- Nothing is stored until you **Save**. **Discard** drops your changes. +- Nothing is stored until you click {guilabel}`Save`. Click {guilabel}`Discard` + to drop your changes. - Saving deletes empty teams. - Participants see the teams only once you let them, see [Settings](manage-settings.md). diff --git a/docs/src/owner/manage-timeline.md b/docs/src/owner/manage-timeline.md index 5d0a4280..c46b22e9 100644 --- a/docs/src/owner/manage-timeline.md +++ b/docs/src/owner/manage-timeline.md @@ -20,15 +20,16 @@ participants can do. That is decided on [Settings](manage-settings.md). ## Phases -- Status per phase: **Completed**, **In progress**, **Upcoming** or **Current - phase**. -- **Make current** / **Clear current phase** moves the marker. You can also move - it on [Settings](manage-settings.md). +- Status per phase: {guilabel}`Completed`, {guilabel}`In progress`, + {guilabel}`Upcoming` or {guilabel}`Current phase`. +- Click {guilabel}`Make current` or {guilabel}`Clear current phase` to move the + marker. You can also move it on [Settings](manage-settings.md). - Participants see the phases on [Timeline](../participant/member-timeline.md). ## A phase -- **Add phase**: name and description, then its dates. -- **Starts** and **Ends**: set both or neither. Once set, they can be changed - but not removed. -- **Delete this phase**. +- Click {guilabel}`Add phase` and enter a name and description. Add its dates + afterwards. +- Enter both {guilabel}`Starts` and {guilabel}`Ends`, or neither. Once set, they + can be changed but not removed. +- Click {guilabel}`Delete this phase` to remove it. diff --git a/docs/src/owner/manage-tracks.md b/docs/src/owner/manage-tracks.md index d5122134..77a27774 100644 --- a/docs/src/owner/manage-tracks.md +++ b/docs/src/owner/manage-tracks.md @@ -26,5 +26,6 @@ Hackathons without tracks are perfectly fine. Add the first one on ## A track -- **New track**: name and description. -- **Delete this track**: its projects stay, without a track. +- Click {guilabel}`New track` and enter a name and description. +- Click {guilabel}`Delete this track` to remove it. Its projects stay, without a + track. diff --git a/docs/src/owner/manage-voting.md b/docs/src/owner/manage-voting.md index 5a4a51ae..a07a21df 100644 --- a/docs/src/owner/manage-voting.md +++ b/docs/src/owner/manage-voting.md @@ -19,22 +19,26 @@ It might also show: ## How voting works 1. Set up the categories. -2. Open voting, then close it: **Participants can vote** on - [Settings](manage-settings.md). +2. Open voting, then close it: tick, then untick + {guilabel}`Participants can vote` on [Settings](manage-settings.md). 3. Make the results final, here. -4. Publish them: **Publish results** on [Settings](manage-settings.md). +4. Publish them: tick {guilabel}`Publish results` on + [Settings](manage-settings.md). ## Categories -- **New category**: name, description and how people vote: **Single choice** - (pick one) or **Points** (spread a budget, 10 by default). -- **Edit** and **Delete** until someone has voted in it. Then it is **Locked**. +- Click {guilabel}`New category` and enter a name and description. Choose how + people vote: {guilabel}`Single choice` (pick one) or {guilabel}`Points` + (spread a budget, 10 by default). +- Click {guilabel}`Edit` or {guilabel}`Delete` to change or remove a category, + until someone has voted in it. Then it is {guilabel}`Locked`. - Participants vote on [Voting](../participant/member-voting.md). ## Count so far - The ranking per category as votes come in. Participants don't see it. -- **Make results final** works only once voting is closed. It cannot be undone. +- Click {guilabel}`Make results final` once voting is closed. It cannot be + undone. ## Final results diff --git a/docs/src/participant/member-overview.md b/docs/src/participant/member-overview.md index dc797326..ae2b5d3b 100644 --- a/docs/src/participant/member-overview.md +++ b/docs/src/participant/member-overview.md @@ -41,15 +41,15 @@ It might also show: ## Your team - Your team's members, its project and whether it has handed in work. -- **Submit your work** leads to [Submissions](member-submissions.md) while - submitting is open. -- Not on a team yet: **Browse the projects** leads to +- Click {guilabel}`Submit your work` to go to + [Submissions](member-submissions.md) while submitting is open. +- Not on a team yet: click {guilabel}`Browse the projects` to go to [Projects](member-projects.md). ## Projects - The number of approved projects, per track if there are tracks. -- **View all** leads to [Projects](member-projects.md). +- Click {guilabel}`View all` to go to [Projects](member-projects.md). ## About this hackathon diff --git a/docs/src/participant/member-participants.md b/docs/src/participant/member-participants.md index 82631fce..24b57f63 100644 --- a/docs/src/participant/member-participants.md +++ b/docs/src/participant/member-participants.md @@ -15,17 +15,19 @@ Everyone taking part in the hackathon. It shows: ## All participants - Search by name or role. -- Your own entry is at the top, marked **You**. -- **View** opens a profile. On your own entry it reads **View & edit**. +- Your own entry is at the top, marked {guilabel}`You`. +- Click {guilabel}`View` to open a profile. On your own entry the button reads + {guilabel}`View & edit`. ## A participant's profile - Name, profile links and the date they joined. -- **Shared answers**: the registration answers they chose to share. -- **Teams**: their teams, once teams are published. Each links to its +- {guilabel}`Shared answers`: the registration answers they chose to share. +- {guilabel}`Teams`: their teams, once teams are published. Each links to its [team](member-teams.md). On your own profile: -- **Edit answers** changes your registration answers. -- **Add your GitHub, LinkedIn or Renku link** leads to your account page. +- Click {guilabel}`Edit answers` to change your registration answers. +- Click {guilabel}`Add your GitHub, LinkedIn or Renku link` to go to your + account page. diff --git a/docs/src/participant/member-projects.md b/docs/src/participant/member-projects.md index 1a4ffa7c..ff96d12d 100644 --- a/docs/src/participant/member-projects.md +++ b/docs/src/participant/member-projects.md @@ -23,19 +23,20 @@ It might also show: ## Propose a project -- **Propose a Project**: title, description, and a track if the hackathon has - tracks. +- Click {guilabel}`Propose a Project`, then enter a title, a description, and a + track if the hackathon has tracks. - An owner reviews it before it appears in the list, see [Manage Projects](../owner/manage-projects.md). ## Your proposals -- Each with its status, for example **Rejected**, and the owner's reason. -- **Edit** while it is still waiting for review. +- Each with its status, for example {guilabel}`Rejected`, and the owner's + reason. +- Click {guilabel}`Edit` to change it while it is still waiting for review. ## Preferences -- **Prefer** marks a project you would like to work on. **★ Preferred** shows - you did. +- Click {guilabel}`Prefer` to mark a project you would like to work on. + {guilabel}`★ Preferred` shows you did. - The owners use the preferences to form the teams, see [Manage Teams](../owner/manage-teams.md). diff --git a/docs/src/participant/member-results.md b/docs/src/participant/member-results.md index c9dcc8c1..1ae1e4f6 100644 --- a/docs/src/participant/member-results.md +++ b/docs/src/participant/member-results.md @@ -15,8 +15,9 @@ shows: ## Placings - Per category: the placed entries with medal and score. -- **View entry** opens the [team](member-teams.md) and its entry. +- Click {guilabel}`View entry` to open the [team](member-teams.md) and its + entry. ## All entries -- Every team that entered. Yours is marked **Your team**. +- Every team that entered. Yours is marked {guilabel}`Your team`. diff --git a/docs/src/participant/member-submissions.md b/docs/src/participant/member-submissions.md index 5005f8d3..d18eb863 100644 --- a/docs/src/participant/member-submissions.md +++ b/docs/src/participant/member-submissions.md @@ -14,17 +14,19 @@ Where your team hands in its work. It shows, for each of your teams: ## Hand in work -- Only while submitting is open for the hackathon, see [overview](member-overview.md), and only once you are on a - [team](member-teams.md). -- Enter a link or notes, then click on **Save draft**. Every draft is a new version. +- You can hand in work once you are on a [team](member-teams.md), and only while + submitting is open. The [Overview](member-overview.md) shows whether it is. +- Enter a link or notes, then click {guilabel}`Save draft`. Every draft is a new + version. ## Finalize -- **Finalize this version** makes a draft your team's entry. +- Click {guilabel}`Finalize this version` to make a draft your team's entry. - Anyone on the team can do it, and it cannot be undone. -- The final entry is what others [vote](member-voting.md) on. -- There can be several final entries. The last one will be the one that counts for the team during voting. +- You can finalize a newer draft later. The latest final version is your team's + entry. +- The entry is what others [vote](member-voting.md) on. ## Earlier versions -- All versions your team handed in are folded away. +- All versions your team handed in, folded away. Click them to unfold. diff --git a/docs/src/participant/member-teams.md b/docs/src/participant/member-teams.md index 7ac7da15..ba40d70e 100644 --- a/docs/src/participant/member-teams.md +++ b/docs/src/participant/member-teams.md @@ -17,7 +17,7 @@ them. It shows: - Teams grouped under their project. The project title links to its [project](member-projects.md). - Each team shows its members and its final entry, if it has one. -- **View** opens [a team](#a-team). +- Click {guilabel}`View` to open [a team](#a-team). ## A team diff --git a/docs/src/participant/member-timeline.md b/docs/src/participant/member-timeline.md index b3dba9b7..ca8de18c 100644 --- a/docs/src/participant/member-timeline.md +++ b/docs/src/participant/member-timeline.md @@ -24,4 +24,4 @@ It might also show: ## The current phase - Its dates, a countdown, its description and what is open now. -- **See the details** leads to the [Overview](member-overview.md). +- Click {guilabel}`See the details` to go to the [Overview](member-overview.md). diff --git a/docs/src/participant/member-voting.md b/docs/src/participant/member-voting.md index 9460c47a..ed12cc12 100644 --- a/docs/src/participant/member-voting.md +++ b/docs/src/participant/member-voting.md @@ -14,10 +14,10 @@ open. It shows: ## Categories - You vote once in each category, and your vote is final. -- **Single choice**: pick one entry. **Points**: spread your points across - entries. +- {guilabel}`Single choice`: pick one entry. {guilabel}`Points`: spread your + points across entries. - Your own team is not on the ballot. -- **View entry** opens a [team](member-teams.md) and its entry. Votes you have - not submitted yet are lost. +- Click {guilabel}`View entry` to open a [team](member-teams.md) and its entry. + Votes you have not submitted yet are lost. - After voting the card shows what you chose. Results come later on [Results](member-results.md). From 65e690b4f16c6036490167d99171352c70d1f8f5 Mon Sep 17 00:00:00 2001 From: Sabine Maennel <5292683+sabinem@users.noreply.github.com> Date: Sat, 24 Oct 2026 08:10:26 +0200 Subject: [PATCH 5/5] docs: corrections --- docs/src/owner/manage-participants.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/owner/manage-participants.md b/docs/src/owner/manage-participants.md index cada10bd..4cb1b4d8 100644 --- a/docs/src/owner/manage-participants.md +++ b/docs/src/owner/manage-participants.md @@ -20,7 +20,7 @@ It might also show: - How many there are, who has no email address, who answered the [registration form](manage-forms.md). - Click {guilabel}`Download CSV` to get everyone, waitlist included. -- Click {guilabel}`Manage` to open a person. +- Click {guilabel}`Manage` to open a [person's details](#a-person) ## Waitlist