Skip to main content
Capell home
My account

We use cookies for essential features and optional analytics.

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalization for the Capell marketing site.

Cookie policy

Clean, fast public output

The public page is the product. Capell prepares structured render data and leaves your team in control of the markup, so what reaches a visitor is clean HTML, fast delivery, and no admin internals. This page gathers the proof a frontend developer wants to see.

Clean DOM No leaked metadata Cache and performance control
Capell public output surface showing clean rendered DOM, cache headers, accessibility checks, and no editor metadata in the page source.
See render rules See performance

Frontend developers judge a CMS by what it does to the public page. Capell is built to stay out of the way: it prepares structured render data, your project renders the markup, and constraints keep admin concerns from leaking into output.

That separation is what delivers clean DOM, strong performance, and pages with no editor metadata for a visitor to find.

What you can confirm

  • The public DOM is the markup your team wrote, not CMS scaffolding.
  • No IDs, field paths, permissions, or preview data reach the page source.
  • Pages cache well and can be tuned for Core Web Vitals.
  • Output stays semantic and friendly to search engines.

Open a page, read the source, and run the audits. The output should match the claims.

What the public page guarantees

Capell does not take over your frontend. It hydrates render data and your project renders the markup, with limits that keep admin concerns out of public output. The result is HTML you would be happy to ship by hand.

Markup you control Your Blade renders the page, so the public DOM stays lean and free of CMS scaffolding or editor widgets. Own your frontend
No editor or runtime metadata Public output carries no admin IDs, field paths, permissions, or preview metadata for a visitor to find. See render constraints
Cache and performance control Public pages can be cached and tuned for Core Web Vitals, so delivery stays fast as traffic grows. See performance
Clean, indexable pages Semantic markup and SEO controls keep public pages readable for visitors and search engines alike. See SEO and performance

How to verify it yourself

Claims about clean output should be testable. A developer can open the page source, run an accessibility audit, check cache headers, and measure Core Web Vitals to confirm Capell delivers what it promises.

Read the rendered HTML Open view-source on a public page and confirm there is no admin metadata, only the markup your team wrote. See render rules
Audit accessibility Run an accessibility check against a public page and confirm semantic, labelled markup. See performance
Inspect cache headers Check the response headers to see how Capell caches public pages for fast repeat delivery. See SEO and performance
Confirm frontend control The own-your-frontend page shows how your project keeps Blade, components, and rendering. Own your frontend
Questions

Output questions?

Does Capell inject its own markup into my pages?
No. Your project renders the public markup from hydrated data, so the DOM stays yours with no CMS scaffolding.
Can a visitor see editor or admin data in the source?
No. Render constraints keep IDs, field paths, permissions, and preview metadata out of public output.
How fast are public pages?
Public pages can be cached and tuned for Core Web Vitals, so performance holds up as traffic grows.
Is the output good for SEO?
Yes. Semantic markup and SEO controls keep pages readable for search engines and visitors.
Next step

Ship public pages you would write by hand.

If clean, fast public output is non-negotiable, the render constraints and own-your-frontend pages show how Capell keeps the visitor-facing page entirely yours.

Clean output Lean DOM, fast delivery, and no admin internals in the page source.

See render constraints Own your frontend

Capell learning journey

Step 1 of 4: Learn

Guides for evaluating, planning, and operating Capell.

Keep moving through Foundations

Fit, architecture, content model, and output quality.

Loading footer