SSWConsulting / SSWConsulting/SSW.Website
🚸 Make future events part of the events page template
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
CC: @wicksipedia, @sethdaily, @camillars
Description
The past events list on our events pages is currently being added as a Tina component.
🤕🌡️🩹The pain:
❌This is bad UX, marketing people havje to manually add events to this component
❌This is a duplicate source of truth, we're retrieving events from the Sharepoint graph API (or will be manually updating them in Tina when the migration is finished). Then we need ot manually go back and add the event in Tina
🤔 The solution
### Todo
- [ ] Refactor past events component into the event page template itself rather than having it as a Tina component
- [ ] Have past events list use a Tina query (or graph API) to retrieve the list of past events
Screenshot
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the events page template and the current Tina past-events component, then review how events are retrieved from the SharePoint Graph API or Tina. Done means the past-events list is part of the template, is populated from the chosen query or API source, and no longer requires manual Tina entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, nextjs
- Domain
- content, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100