Published vs. visible menu entries
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 551
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 21
Description

Visibility can be toggled from menu customization in the management area but this doesn't ensure the menu entry will appear in the display view of the event. For example, **Participant list** will only be ACTUALLY displayed if one of the registration forms has the option _"Publish registrations"_ enabled. This is very confusing for users as they don't know what they have to do to get the menu entry appear.
I propose we have a clearer distinction between **visible** and **published** state and that we inform about them both on the same view.
- Published: The page essentially exists and there is a URL that will render it.
- Visible: There is a menu entry on the side menu with a link to that URL.
The thing is, the concept of "published" can be more complex than just a toggle and it will usually depend from several different conditions that should probably live outside of the menu customization page. Open questions:
- Should we move those settings/conditions somehow to the menu customization page?
- Should we simply explain how to get a un-published page published? i.e. tooltip, warning, link, ...
- Should we not display un-published pages on the menu customization page altogether?
Contributor guide
Research direction
Start with menu customization in the management area and the event display view, using the Participant list example and its “Publish registrations” condition. Clarify how published and visible states should be represented and which proposed approach to use; done means users can understand why a menu entry is absent and how to make it appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100