The schedule of talks and workshops will likely be the most complex and critical part of this website — basically the final boss we’ll need to defeat, especially in terms of accessibility, usability, and future maintainability.
Before we move too far ahead, we should start tackling this now, instead of treating it as a last-minute integration.
Why this matters
- The schedule will be content-heavy and dynamic
- It must work well for keyboard navigation, screen readers, and responsive layouts
- Small early decisions (data format, structure, tooling) will have a big impact later
Open questions to resolve early
- How will we receive the schedule data?
- JSON?
- From a CMS?
- From a third-party service?
- What will the data schema look like?
- Talks vs workshops
- Time slots, rooms, speakers
- Overlaps, tracks, language, etc.
- Do we want / need a third-party schedule component or service?
- If yes, we should evaluate its accessibility guarantees
- Can we start prototyping or validating the schedule logic now, even with mock data?
Next steps
- Define or request a sample JSON / data contract
- Evaluate existing libraries or services (if any)
- Start an early accessibility review focused on schedule interaction patterns
If we get this right early, everything else will feel much easier.
If we don’t… well, we know who the boss is 😉
The schedule of talks and workshops will likely be the most complex and critical part of this website — basically the final boss we’ll need to defeat, especially in terms of accessibility, usability, and future maintainability.
Before we move too far ahead, we should start tackling this now, instead of treating it as a last-minute integration.
Why this matters
Open questions to resolve early
Next steps
If we get this right early, everything else will feel much easier.
If we don’t… well, we know who the boss is 😉