Improve workshop page UX by separating current status from history#2340
Improve workshop page UX by separating current status from history#2340Walpurga03 wants to merge 2 commits intobitcoinops:masterfrom
Conversation
Walpurga03
commented
May 27, 2025
Walpurga03
commented
- Update main workshops page to prominently display current status
- Move historical workshop information (2018-2020) to separate page
- Improve user perception by highlighting that site is actively maintained
- Preserve all historical workshop content in dedicated history page
There was a problem hiding this comment.
@Walpurga03 I dont personally like the idea of hiding and javascript showing the items on the page.
That said I think adding this text before the workshop list is helpful:
Currently, no workshops are scheduled. We are evaluating potential future workshop topics and formats based on community feedback and technical developments in the Bitcoin ecosystem.
And then having a Previous Workshops header before listing the old workshops would be helpful.
Also curious what others think.
… with reusable Jekyll include - Removes previous JavaScript and HTML-based toggle for the "Previous Workshops" section. - Introduces a parameterized Jekyll include (`functions/details-list-workshops.md`) to render the workshop history as a native HTML <details> element. - Improves maintainability and consistency with other site sections (e.g., newsletter review club). - Adds clear comments for future maintainers. - No functional JavaScript is required; all logic is handled via Jekyll and HTML. Improve workshop page UX by separating current status from history - Update main workshops page to prominently display current status - Move historical workshop information (2018-2020) to separate page - Improve user perception by highlighting that site is actively maintained - Preserve all historical workshop content in dedicated history page Improve workshop page UX with dedicated layout and toggle functionality - Show current status prominently: no workshops currently scheduled - Hide historical workshop information (2018-2020) in collapsible section - Maintain all existing #taproot-workshop anchor links functionality - Use dedicated layout following Publications pattern for consistency - Remove separate workshop-history.md file (integrated into main page) - Improve user perception that site is actively maintained Improve workshop page UX with dedicated layout and fix localization links - Show current status prominently: no workshops currently scheduled - Hide historical workshop information (2018-2020) in collapsible section - Maintain all existing #taproot-workshop anchor links functionality - Use dedicated layout following Publications pattern for consistency - Fix broken localization links by removing non-existent language pages - Improve user perception that site is actively maintained add workshops.md
Walpurga03
force-pushed
the
feature/workshop-history-toggle
branch
from
2c92b06 to
31d65b4
Compare
… history with Jekyll include
|
@bitschmidty |
| ## Current Status | ||
|
|
||
| **Currently, no workshops are scheduled.** We are evaluating potential future workshop topics and formats based on community feedback and technical developments in the Bitcoin ecosystem. |
There was a problem hiding this comment.
I think the addition of the Current Status saying that we currently don’t plan any workshops is a great improvement. I don’t think the Previous Workshops section need to be hidden, it seems alright to me to just list them under a second section at the same level as Current Status, i.e.:
Current Status
Not planning anything at this time.
Previous Workshops
Workshop 3–5
Bla
Workshop 2
…
Could you explain why you think it would be better to hide the old workshops, @Walpurga03?
There was a problem hiding this comment.
In my view, displaying old workshops that happened long ago gives your website an outdated or neglected impression. A streamlined first impression with less but more current content often looks more professional and inviting.
There was a problem hiding this comment.
Im still share Murch's opinion of listening them under the current status as is without hiding
3 participants
