René's URL Explorer Experiment


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

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@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-profiling0
react-import-mapreact,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-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:e2fc35db-a159-348c-027c-00aba8daa0ee
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-id9EF6:214941:2B4181:3AD65D:6AFE3DAD
html-safe-nonce31576742826c09e26b0816f9510f54427392454f894f54ff8412eeca99858d43
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5RUY2OjIxNDk0MToyQjQxODE6M0FENjVEOjZBRkUzREFEIiwidmlzaXRvcl9pZCI6IjcxNDA5MzM0OTI3OTkzMjM1NjUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac1d6883155833b852aaec3e331265ab2fab87130ef03830d22b0274f9be7e0b71
hovercard-subject-tagissue:4000166324
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/ycode/ycode/3/issue_layout
twitter:imagehttps://opengraph.githubassets.com/9073e51c626f3553bd22e4e3084274ea4b9f8ca77964a20843525360bf082c03/ycode/ycode/issues/3
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/9073e51c626f3553bd22e4e3084274ea4b9f8ca77964a20843525360bf082c03/ycode/ycode/issues/3
og:image:altProblem 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:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameysamcode
hostnamegithub.com
expected-hostnamegithub.com
Nonef1a5901e2377b0af2a0b303f9528678f1475d04b9219dca1e993344196eaa07c
turbo-cache-controlno-preview
go-importgithub.com/ycode/ycode git https://github.com/ycode/ycode.git
octolytics-dimension-user_id65892203
octolytics-dimension-user_loginycode
octolytics-dimension-repository_id1165452593
octolytics-dimension-repository_nwoycode/ycode
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id1165452593
octolytics-dimension-repository_network_root_nwoycode/ycode
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
releasec4447fdce9ed0f33af959d2b6680d0bc18212a6a
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/ycode/ycode/issues/3#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fycode%2Fycode%2Fissues%2F3
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fycode%2Fycode%2Fissues%2F3
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=ycode%2Fycode
Reloadhttps://github.com/ycode/ycode/issues/3
Reloadhttps://github.com/ycode/ycode/issues/3
Reloadhttps://github.com/ycode/ycode/issues/3
ycodehttps://github.com/ycode
ycodehttps://github.com/ycode/ycode
Codehttps://github.com/ycode/ycode
Issues7 (7)https://github.com/ycode/ycode/issues
Pull requests1 (1)https://github.com/ycode/ycode/pulls
Discussionshttps://github.com/ycode/ycode/discussions
Actionshttps://github.com/ycode/ycode/actions
Projectshttps://github.com/ycode/ycode/projects
Security and quality1 (1)https://github.com/ycode/ycode/security
Insightshttps://github.com/ycode/ycode/insights
https://github.com/ycode/ycode
New issuehttps://github.com/login?return_to=https://github.com/ycode/ycode/issues/3
New issuehttps://github.com/login?return_to=https://github.com/ycode/ycode/issues/3
feat: support components inside rich-text CMS fieldshttps://github.com/ycode/ycode/issues/3#top
Feature requestA new feature requesthttps://github.com/ycode/ycode/issues?q=state%3Aopen%20label%3A%22Feature%20request%22
https://github.com/ysamcode
ysamcodehttps://github.com/ysamcode
on Feb 27, 2026https://github.com/ycode/ycode/issues/3#issue-4000166324
ycode.com/updates/components-inside-rich-texthttps://www.ycode.com/updates/components-inside-rich-text
ysamcodehttps://github.com/ysamcode
Feature requestA new feature requesthttps://github.com/ycode/ycode/issues?q=state%3Aopen%20label%3A%22Feature%20request%22
on Feb 27, 2026https://github.com/ycode/ycode/issues/3#event-23131236472
liamwalderhttps://github.com/liamwalder
on Mar 3, 2026https://github.com/ycode/ycode/issues/3#event-23221117474
Merge pull request #3 from ycode/templates-in-welcomehttps://github.com/ycode/ycode/commit/981fac46bfaf7a26a2c94f02e95097a6bec8cbeb
#3https://github.com/ycode/ycode/issues/3
981fac4https://github.com/ycode/ycode/commit/981fac46bfaf7a26a2c94f02e95097a6bec8cbeb
ysamcodehttps://github.com/ysamcode
completedhttps://github.com/ycode/ycode/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
on Mar 3, 2026https://github.com/ycode/ycode/issues/3#event-23222022985
Sign up for freehttps://github.com/signup?return_to=https://github.com/ycode/ycode/issues/3
Sign in to commenthttps://github.com/login?return_to=https://github.com/ycode/ycode/issues/3
Feature requestA new feature requesthttps://github.com/ycode/ycode/issues?q=state%3Aopen%20label%3A%22Feature%20request%22
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.