SSWConsulting / SSWConsulting/SSW.Website
✨ Develop the Case Study Sidebar List Component
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
cc @wicksipedia @isaaclombardssw @UlyssesMaclaren @adamcogan @miichaelsmedley @louisroa8189
Description:
Create the Case Study Sidebar List component for Consulting Pages to display additional information, such as a tech stack, alongside the main case study content. This component should support a list of items with customizable icons, headings, and body text, allowing users to showcase detailed, structured information in a sidebar format.
This component will be used to build the Case Study page - Case Study - Desktop
Acceptance Criteria
- The Case Study Sidebar List component includes the following customization options:
- Image File Uploader
- Item (Repeatable):
- Icon Selector
- Heading Text Field
- Body Text Field
- Fully responsive across desktop, tablet, and mobile.
- Works seamlessly on all major browsers (Chrome, Firefox, Safari, Edge).
- Fields and sections can be enabled or disabled for flexibility.
- The UI for customization options is grouped logically for ease of use.
- Code is ready for theming (e.g., Light/Dark modes, custom colors – see linked PBI: https://github.com/SSWConsulting/SSW.Website/issues/3300).
- Tested and approved by Wicksy, Louis, and Betty.
Tasks:
- TODO - Developer to update
Figure: Sidebar List
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
Start by reviewing the linked Figma prototype and the related theming issue #3300 to understand the intended sidebar layout and customization scope. Implement the repeatable items, uploader, field toggles, responsive behavior, browser support, and theming readiness described in the acceptance criteria, then obtain the listed stakeholder approval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100