SSWConsulting / SSWConsulting/SSW.Website

✨ Develop the Case Study Body Component

Open
#3,324 0 comments 0 reactions 0 assignees View on GitHub

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 Body component for Consulting Pages. This component should allow users to present detailed case study content in a structured and visually appealing way. The component must include WYSIWYG (What You See Is What You Get) functionality to enable rich-text editing and formatting. It should prioritize flexibility, accessibility, and responsiveness for optimal readability across all devices.

This component will be used to build the Case Study Page - Case Study - Desktop

Acceptance Criteria:

  • The Case Study Body component includes the following functionality:
  • WYSIWYG editor for rich-text content.
  • Support for headings, paragraphs, lists (ordered and unordered), links, and inline formatting (bold, italic, etc.).
  • Ability to insert and format technical content such as code snippets or inline text highlights.
  • Fully responsive across desktop, tablet, and mobile.
  • Works seamlessly on all major browsers (Chrome, Firefox, Safari, Edge).
  • 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

Image
Figure: Case Study Body

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

No implementation file, test, or entry point is named. Start by reviewing the linked Figma Case Study Body design and the existing Next.js/TinaCMS component conventions in SSW.Website. Done means a responsive, accessible rich-text body supports the listed formatting and code content, works across the named browsers, and is approved by Wicksy, Louis, and Betty.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs
Domain
accessibility, content, design, frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.