SSWConsulting / SSWConsulting/SSW.Website

✨ Investigate Feasibility of Using Rich Text for Titles, Headings, and Descriptions on Reusable Components

Open
#3,473 0 comments 0 reactions 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: @bettybondoc via YakShaver.ai 🦬
cc: @Calinator444, Louis Roa, @wicksipedia, @adamcogan, @brookjeynes-ssw

Hi Team!

Watch the video

Url: https://app-sswwebbie-9eb3-pr-3420.azurewebsites.net/admin/index.html/#/consulting/aiworkshopv2

Pain

Investigate whether we should use rich text for all the titles, headings, and descriptions on the reusable components of the SSW Website (Dev - Next.js). Currently, some components like descriptions allow rich text formatting (e.g., bold, italic, links), but headings and titles do not. The goal is to determine the feasibility, effort required, and pros and cons of making all text blocks editable with rich text.

Acceptance Criteria
  1. Investigate the feasibility of implementing rich text for all titles, headings, and descriptions.
  2. Estimate the amount of work required to implement this change.
  3. Evaluate the pros and cons of using rich text for all text blocks.
  4. Provide a recommendation on whether to proceed with this change.
Screenshot

Image
Figure: A key decision is requested to investigate whether all headings and descriptions on reusable components should use rich text.

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

Review the linked admin URL and video, then inspect the reusable components in the SSW Website's Dev Next.js implementation. Document feasibility, estimated effort, pros and cons, and a recommendation for applying rich text to titles, headings, and descriptions; the issue names no files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs
Domain
content, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.