Show clubs' last and next exhibitions on the site, and past ones on the members page
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Read Photo-Club-Hub#834’s “Website, from the HTML app” and “Data model” sections, then confirm Photo-Club-Hub-Data#67 has been released before starting. Find the Generate flow and the clubs, museums, and members page code; check how EN/NL strings and live data are handled. Done means the requested exhibition columns and members-page table appear with the specified links and counts, and the regenerated site has been checked against live data.
Written by the indexing model from the issue text.
Description
What
The website part of Photo-Club-Hub#834: show
each club's last and next exhibition on the generated site, and a club's past exhibitions on its
members page.
The spec lives in Photo-Club-Hub#834 (section "Website, from the HTML app", plus "Data model"). It is not repeated
here, so it cannot drift. What follows is only this repo's share of the work.
Depends on Photo-Club-Hub-Data#67
being released. Planned after the iOS app's version (Photo-Club-Hub#834), and after the App Store upload (#254).
In short
- Clubs page: two new columns, last and next exhibition, each a name with its date. The Fotobond id
column goes; the member count moves into the club name, "Myclub (2x)", and is left out when it is zero. The museums page gets the same
two columns. - Next links to the poster. Last links to the club's members page, to a new exhibitions table at
the top, above current and past members, listing every past exhibition with a link to its gallery. - "Next" is decided at Generate time. Dates in the cells show readers when it is over; a script that
moves entries by today's date is a later nice-to-have.
Steps
Estimates are author's days.
| # | Step | Days |
|---|---|---|
| 1 | Resolve the Data release that adds Exhibition |
¼ |
| 2 | Clubs and museums pages: the two columns, drop the Fotobond id, member count in the name (none when zero) | 1½–2 |
| 3 | Members page: the optional exhibitions table at the top | 1–1½ |
| 4 | EN and NL strings; regenerate and check against the live data; release notes | ½ |
Total: roughly 3 to 4 days.
- 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