matrix-org / matrix-org/matrix-conf-website
Thoughts on improving the navigation changes based on the conf state
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Astro
- Stars
- 9
- Forks
- 14
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
These are some thought on how we can improve the maintainer burden of changing navigation links and so on when the conf progresses. This can also apply to matrix.org main page and it's banner:
- We probably want a playbook of "when do we need to switch which flag"
- Have custom options in the config file indicating the state
- Possible stages:
- CFP
- CFP ended
- Schedule done
- Live
- After conference
- Each stage can be accessed in templates
- Each state will change the appropriate things in the UI without needing major changes
- Possible stages:
- Define dates of the conference in the config to simplify having it right in all places
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the navigation links, the matrix.org main-page banner, the configuration, and the templates described in the issue. Define the conference stages and dates, then determine how each stage should change the UI and document when flags are switched. Done means the maintainer playbook and state-driven behavior are specified.
Written by the indexing model from the issue text.
Assessment
- 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