SSWConsulting / SSWConsulting/SSW.Website

✨ Agenda - Add structured agenda support to event pages

Open
#4,852 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Needs Refinement YakShaver
Dominant language
HTML
Stars
14
Forks
10
Avg merge
13h 51m
Merged PRs (30d)
38

Description

Requested by: @tiagov8 via YakShaver.ai 🦬
cc: @tiagov8, @isaaclombardssw, @babakamyljanovssw

Hi Team!

  🟥  Watch the video (1 min 24 sec)

  Url from screen share: https://ssw.com.au/admin/index.html#-/events/2026/ai-hack-day---sydney

Pain

The new events page on the ⭐ SSW Website (Dev - Next.js) currently does not provide a suitable way to add agendas within TinaCMS. Attempting to use tables inside the event description results in formatting limitations such as broken layouts, inability to add line breaks, and lack of support for lists within table cells. A dedicated agenda component should be introduced to allow editors to easily create and manage event agendas in a structured and user-friendly way. The component could be displayed below the About Us section or within the sidebar beneath the event widget.

Acceptance Criteria
  1. A reusable agenda component is available for event pages.
  2. Content editors can add agenda items through TinaCMS without using raw tables.
  3. Agenda entries support structured content including time, title, description, line breaks, and bullet lists.
  4. The agenda renders consistently and responsively on the frontend.
  5. The agenda component placement is configurable for the event page layout.
  6. Existing event page content continues to render correctly without regression.
  7. The editing experience in TinaCMS is intuitive and does not require manual HTML formatting.
Screenshot

Screenshot
Figure: Missing agenda component for event pages

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Next.js event-page implementation and its TinaCMS editing configuration from the existing event description. Review how event content is rendered and how the layout places the About Us section and event widget. Done means editors can create structured agenda items without raw tables, the placement is configurable, and existing event pages remain responsive and unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs
Domain
content, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.