Widget Edit Links Extension

What you can do

You already published Maya's homepage hero and embedded it. A headline tweak on the live page still means remembering which organization, team, project, and widget to open. This page is the skip: click the R on that hero and land in its composer.

Two everyday jobs:

• Fix the live hero without hunting the widget list. Maya's Production snapshot is already on the homepage. Turn on Link to RuleCMS, click the R on that hero, edit the draft, and publish again.
• Review the Staging hero the same way. QA loaded the Staging snapshot. The badge on that page opens the Staging composer — not a generic dashboard, and not Production by accident.

Share the store listing with every editor on the team. The extension is free. There is no seat limit.

How Link to RuleCMS thinks

The extension does one job. When Link to RuleCMS is on, it looks for data-rulecms-published-key on the page and pins a small R on each match. That is the only attribute it reads. Official Staging and Production embeds — @rulecms/widget-react and the hosted HTML custom element — put that attribute on automatically.

Each badge's editor URL is built from that widget's own key: https://rulecms.com/edit-published-widget/{publishedKey}. A page with Maya's hero and a footer widget gets two badges. The hero's R cannot open the footer.

The published-key wrapper is display: contents. It generates no box of its own, so the extension measures the hero's visible children and sits the badge on that content. If the hero has not painted yet, there is no badge — it is hidden, not a broken link.

Here is the case that surprises people. Maya opens a Development draft preview and looks for the R. Development is a different workflow. Those embeds use a draft widget key, not a published snapshot. The badge's destination is a published-widget editor. Preview a live draft with Development Integration instead.

Clicking the R opens rulecms.com in a new tab. Sign in if Chrome asks. RuleCMS checks you can open that widget, then takes you to its composer. A short “taking you to your widget” screen is normal. You need a Widget Access group — View, Manage, or Admin — for that environment, or a RuleCMS admin account. View can follow the badge into the composer. Manage is enough to change the draft. Publishing the snapshot again uses Publish to Staging or Publish to Production, the same grants as Publishing.

Click the R on Maya's hero

Picture the homepage hero already published to Production and embedded on the live site — the same hero from Widgets and Publishing. This is the path from that page back into the composer.

1. Open the RuleCMS Widget Edit Links listing on the Chrome Web Store. Click Add to Chrome and confirm. The extension is free and works in Google Chrome and other Chromium browsers that support the store.
2. The first install opens the dashboard so you see the toggle. Turn on Link to RuleCMS. You can also flip it from the toolbar popup. Pin the extension from Chrome's puzzle-piece menu so it stays easy to reach.
3. Visit Maya's live homepage — or the Staging page, if you are reviewing a release — with the published hero on it.
4. Look for the R on that hero. Click it. The badge title is Edit this widget in RuleCMS.
5. Sign in if RuleCMS asks. Wait through the short loader. You land in that widget's composer — the draft for the environment that published key belongs to.
6. Change the headline. Save. Then publish again. The live embed does not move until you publish. That is a safe stop.

If a badge is missing, confirm Link to RuleCMS is on, refresh, and check that the page is rendering a RuleCMS published widget — not a static copy of old markup. Use Staging first when you are reviewing a release. Use Production when the live hero needs a fast fix.

What to read next

This page is the story and the first walkthrough. Publishing the snapshot, previewing a Development draft, and how the embed exposes the published key live on the pages below.

• Publishing — The composer is still the draft after you click the R. Publish is the snapshot the live site fetches.
• Development Integration — Preview the live Development draft with a dev. token. That path does not use a published snapshot.
• HTML Custom Element Embed — How <rulecms-widget> lands on the page and why data-rulecms-published-key is there for the badge to find.
• Widgets — Open Maya's hero from the dashboard when you are not on the live page.

How this fits

The extension does not replace a widget, and it does not publish. It is the one-click path from a Staging or Production embed back into that widget's composer. Widgets is how Maya builds the hero. Publishing is how the site gets the snapshot. This page is how she opens that snapshot's draft from the page visitors already see.

Install. Turn on Link to RuleCMS. Click the R. Edit. Publish again.