Title: feat: support components inside rich-text CMS fields · Issue #3 · ycode/ycode · GitHub
Open Graph Title: feat: support components inside rich-text CMS fields · Issue #3 · ycode/ycode
X Title: feat: support components inside rich-text CMS fields · Issue #3 · ycode/ycode
Description: Problem or motivation Rich-text fields in CMS collections currently only support standard text formatting (headings, paragraphs, lists, links, etc.). There is no way to insert reusable components — like newsletter forms, CTAs, testimonia...
Open Graph Description: Problem or motivation Rich-text fields in CMS collections currently only support standard text formatting (headings, paragraphs, lists, links, etc.). There is no way to insert reusable components —...
X Description: Problem or motivation Rich-text fields in CMS collections currently only support standard text formatting (headings, paragraphs, lists, links, etc.). There is no way to insert reusable components —...
Opengraph URL: https://github.com/ycode/ycode/issues/3
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: support components inside rich-text CMS fields","articleBody":"### Problem or motivation\n\nRich-text fields in CMS collections currently only support standard text formatting (headings, paragraphs, lists, links, etc.). There is no way to insert reusable components — like newsletter forms, CTAs, testimonial blocks, or FAQ sections — directly within rich-text content. This limits the expressiveness of long-form content such as blog posts, articles, and resource pages, forcing builders to choose between dynamic layouts and CMS-driven content.\n\n### Proposed solution\n\nAllow **any component to be inserted directly inside rich-text CMS fields**. When editing a CMS item's rich-text content, users should be able to place a component between paragraphs or other block-level elements.\n\n**How it should work:**\n1. The builder creates a component in the editor as usual\n2. When editing a rich-text field in a CMS item, a \"Component\" option is available in the toolbar\n3. Clicking it opens a picker showing all available components\n4. The selected component is embedded inline within the rich-text content and rendered on the published page\n\n**Use cases:**\n- Insert a **newsletter subscribe form** between paragraphs to capture leads mid-article\n- Embed an **FAQ accordion** within a help article for quick answers\n- Place a **call-to-action button or banner** inside a resource guide to drive conversions\n- Add a **testimonial or quote block** inside long-form content for credibility\n- Insert a **code snippet component** with syntax highlighting in technical posts\n\nComponents inside rich-text should respect their own design properties and variables, just as they do when placed on a page directly.\n\n### Alternatives considered\n\n- **HTML embed inside rich-text**: Users could paste raw HTML, but this bypasses the visual builder, is hard to maintain, and doesn't support component variables or design properties.\n- **Breaking content into multiple CMS fields**: Splitting an article into \"intro\", \"component slot\", \"body\" etc., but this is rigid, doesn't scale, and creates a poor editing experience.\n\n### Area\n\nCollections / CMS\n\n### Additional context\n\nThis feature was available in the legacy hosted version of Ycode (see [ycode.com/updates/components-inside-rich-text](https://www.ycode.com/updates/components-inside-rich-text)) and was well received. Bringing it to the self-hosted edition would restore an important content authoring capability and keep feature parity with the original platform.","author":{"url":"https://github.com/ysamcode","@type":"Person","name":"ysamcode"},"datePublished":"2026-02-27T09:53:45Z","url":"https://github.com/ycode/ycode/issues/3"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:e2fc35db-a159-348c-027c-00aba8daa0ee |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9EF6:214941:2B4181:3AD65D:6AFE3DAD |
| html-safe-nonce | 31576742826c09e26b0816f9510f54427392454f894f54ff8412eeca99858d43 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5RUY2OjIxNDk0MToyQjQxODE6M0FENjVEOjZBRkUzREFEIiwidmlzaXRvcl9pZCI6IjcxNDA5MzM0OTI3OTkzMjM1NjUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 1d6883155833b852aaec3e331265ab2fab87130ef03830d22b0274f9be7e0b71 |
| hovercard-subject-tag | issue:4000166324 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/ycode/ycode/3/issue_layout |
| twitter:image | https://opengraph.githubassets.com/9073e51c626f3553bd22e4e3084274ea4b9f8ca77964a20843525360bf082c03/ycode/ycode/issues/3 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/9073e51c626f3553bd22e4e3084274ea4b9f8ca77964a20843525360bf082c03/ycode/ycode/issues/3 |
| og:image:alt | Problem or motivation Rich-text fields in CMS collections currently only support standard text formatting (headings, paragraphs, lists, links, etc.). There is no way to insert reusable components —... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | ysamcode |
| hostname | github.com |
| expected-hostname | github.com |
| None | f1a5901e2377b0af2a0b303f9528678f1475d04b9219dca1e993344196eaa07c |
| turbo-cache-control | no-preview |
| go-import | github.com/ycode/ycode git https://github.com/ycode/ycode.git |
| octolytics-dimension-user_id | 65892203 |
| octolytics-dimension-user_login | ycode |
| octolytics-dimension-repository_id | 1165452593 |
| octolytics-dimension-repository_nwo | ycode/ycode |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1165452593 |
| octolytics-dimension-repository_network_root_nwo | ycode/ycode |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | c4447fdce9ed0f33af959d2b6680d0bc18212a6a |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width