WYSIWYG

## Summary
'What you see is what you get' text editor. Complex component for text editing and styling.
Explore OOTB options. Wrap in our own component.

## 💰 User value
Describe why this is important and how it will help users (either developers, designers or the end-users). Think about how it makes people's lives easier, more accessible or quicker to build stuff.

## 📚 User Stories
If relevant, describe the high-level functionality as user stories.

*As an* ICDS user:
*I need*
*So that*

## 📝 Acceptance Criteria
If relevant, describe in full detail the different interactions and edge cases that the component or patterns needs to fulfil.

*Given*
*When*
*Then*

## ✏ Designs
If there's a Figma design file (or other mock-up), include it here.

## 🧾 Guidance
If there's written guidance or documentation, include it here.

The issue proposes a WYSIWYG text editor component but does not identify files, entry points, designs, guidance, or acceptance criteria. Start by reviewing the existing component structure and available out-of-the-box editor options. Before implementation, define the user stories, interactions, edge cases, and completion criteria.

Written by the indexing model from the issue text.