**As a product page owner, I want to write roadmap item descriptions as rich content (like blog posts) instead of filling out separate fields so that I can communicate feature ideas more effectively and engagingly.**

## Description

Replace the current structured roadmap item form (separate fields for description, acceptance criteria, etc.) with a rich content editor identical to the blog post editor. Product page owners can write a free-form article about a planned feature, embed images, format text, and tell a compelling story — just like they would in a blog post. This makes roadmap items more engaging for supporters and lowers the barrier for product page owners to describe their vision.

## Scope

- Replace roadmap item description with rich text editor (same as blog editor)
- Support for formatted text, images, links, code blocks
- Preview mode before publishing
- Existing roadmap item metadata (status, complexity, etc.) remains as structured fields alongside the rich content
- Migration path for existing roadmap items with plain text descriptions

## What Are Your Thoughts?

Would rich content make roadmap items more engaging for you? What content types (images, videos, code examples) would you want to see? Share your thoughts in the comments below or on our social media channels!

### AC1: Rich Content Editing

- GIVEN a product page owner creates or edits a roadmap item
WHEN they write the description
THEN they have access to the same rich text editor used for blog posts (formatting, images, links, code blocks)

### AC2: Rich Content Display

- GIVEN a roadmap item has rich content
WHEN a user views the roadmap item
THEN the content is rendered with full formatting, just like a blog post

### AC3: Metadata Preserved

- GIVEN a product page owner edits a roadmap item
WHEN they use the rich content editor
THEN structured metadata (status, complexity estimate, voting) remains available as separate fields alongside the content

### AC4: Backward Compatibility

- GIVEN existing roadmap items have plain text descriptions
WHEN the feature is deployed
THEN existing descriptions are displayed correctly and can be edited with the new rich content editor