CEDX Pages · Marketing
Pages are assembled from a 300-section library, and every section carries its exit rate and conversion lift. Publish risk is scored before go-live — slow mobile LCP, missing CTAs and empty SEO fields do not ship quietly.
A section with 46% exit and negative lift is not a design opinion. It is a row in a table, with sessions next to it.
Runs on demo data. The storefront, sections and session figures are the demo's.
What it is
Describe the page — winter clearance landing with urgency banner — and the draft is assembled from the section library: pattern matched from the bank, SEO title, description and handle pre-filled, predicted CVR band on the row. The screen says it plainly: deterministic demo, no live model.
Every section carries uses, position, exit rate, CVR delta and sessions. The buy box runs on 48 pages at 14% exit and +1.6 lift. One reviews block exits 59% of visitors — and the table says so next to its 151,425 sessions.
18 themes with versions, status, templates, sections, pages and owners. The main storefront runs 2.4.1 across 248 pages; five themes sit in preview, staged; older releases stay archived, not deleted.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/pages.
01 — Overview
91 pages carry publish risk, 13 of them critical — SEO gaps, missing CTAs, mobile LCP over 3.5 seconds on go-live candidates. The root-caused alerts name the offenders: a scheduled fall landing with empty discovery metadata, a collection template at 3.6s mobile LCP.
02 — Generate
Three drafts in the queue — fall drop teaser, holiday gift guide, outlet clearance — each with its section stack and predicted CVR band, each pushable into the pages library with a Generated badge.
03 — Sections
Sorted by sessions, the table is a league of reusable parts: promo bar on 12 pages, trust-badges strip on 30, a footer that exits 55% with zero lift. Sections that hurt get found because they are measured.
04 — Themes
Theme versions move from preview to live with their templates, sections and pages attached — 2.4.1 on 248 pages, a locales pack on 86, a wholesale theme on 55. Rollbacks exist because archives do.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Writes against the section scores — retires the block that exits 59% instead of debating it.
300 sections · 145 hurting
Owns the templates and the theme releases, and keeps the collection pages under the LCP line the gate enforces.
18 themes · 7 live
Runs the A/B queue and reads publish risk before anything is scheduled — 13 critical pages is a to-do list.
17 experiments · risk 91The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
A draft is built from the section library — stack pattern, SEO fields and predicted CVR band attached.
The publish-risk gate reads SEO gaps, missing CTAs and mobile LCP before the page can be scheduled.
A/B experiments run against live traffic — 17 in flight on the demo storefront.
Conversion-drop rankings surface the sections that leak, and the library gets edited, not the excuse.
One record
The storefront is not an island of templates. Its sections, forms, search terms and session data are the same ones the rest of the estate uses.
The keywords the pages are built to win, and the site audit that reads the same URLs.
CEDX FormsThe capture sections inside the pages — spam-scored before a submission reaches anyone.
CEDX AssetsHero media and brand files come from the governed library, rights status attached.
CEDX Web AnalyticsThe sessions and conversion rates the sections are scored against.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your pages, your library
Pages with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/pages. It runs on demo data — the storefront in the captures is the demo one.
No, and it says so on screen: deterministic demo, no live model. A brief is matched to a section-stack pattern from the library, SEO fields are pre-filled, and the draft lands in the queue with a predicted CVR band.
A score computed before go-live — SEO gaps, missing CTAs, slow mobile LCP on candidates. 91 pages carry it in the demo, 13 critical, and the alerts name the pages.
By what they cost: exit rate, CVR delta and sessions on every row of the library. 145 sections currently show negative lift, which is precisely the point of measuring them.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask which of your sections would show up with negative lift.