Generate-time toggle for organizations that may have stopped, with an investigation view
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Read PreferencesViewModelHTML and OrganizationsPage+makeOrgTable.swift, using showFormerMembers as the stated example. First confirm Data#91 is released and resolved in Package.resolved, and check the iOS issue for the expected organization statuses and warning details. Done when generated sites hide flagged organizations by default, the investigation view shows the specified details without linking badWebsite, and the published site uses the toggle off.
Written by the indexing model from the issue text.
Description
Status
Planned alongside iOS 3.0.5. Hiding former organizations on the public website is HTML#279, which comes first, together with the Data package (Data#91) and the iOS filter (#891). The details below are a starting point, to be settled when the work starts.
What maintainers get
A static site has no runtime settings, so seeing the former organizations is a choice made when the site is generated. A localhost build with the toggle on becomes the investigation view: every former organization is listed with a visible warning and its full logbook from Data#91 (date, author and text of each log entry). Apart from a future editor, that is the one place the logbook is shown.
Proposed change
- A generate-time preference in
PreferencesViewModelHTML, modelled onshowFormerMembers, off by default. OrganizationsPage+makeOrgTable.swift: when the preference is on, include former organizations (which HTML#279 skips) with the warning and logbook.badWebsitesfrom Data#91 may be shown as plain text, for whoever is re-checking the club. It is never a link, also not in the investigation view.- The published site at fcdegender.nl/hub is always generated with the toggle off.
Depends on
- Dominant language
- Swift
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from vdhamer/Photo-Club-Hub-HTML
-
Enhancement Localization
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vdhamer/Photo-Club-Hub-HTML#242 · 1 comment ·
-
Bug Good first issue Refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vdhamer/Photo-Club-Hub-HTML#237 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
vdhamer/Photo-Club-Hub-HTML#282 ·
-
Enhancement Ignite
Difficulty 4/5 1-2 days Newbie friendliness 45/100
vdhamer/Photo-Club-Hub-HTML#281 ·
-
Enhancement Ignite
Difficulty 3/5 1-2 days Newbie friendliness 56/100
vdhamer/Photo-Club-Hub-HTML#279 · 1 comment ·
All issues in vdhamer/Photo-Club-Hub-HTML
Similar issues
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 86/100
ajithrnayak/xpunge#7 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YahiaAngelo/vphone-linux#70 ·
Maintainers usually reply within 1 day
-
follow-up needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
manaflow-ai/cmux#49164 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100