Skip to main content
Capell home
Live demo

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

Field Notes record the awkward middle of CMS work: a migration surprise, an editor workflow lesson, a launch check, a package decision, or a shortcut the contributor would avoid next time.

What qualifies

  • A real decision or problem from work the contributor took part in.
  • Enough context to understand the tradeoff and result.
  • Permission to publish the contributor's name and note.
  • A review before the note becomes public.

Evaluator scenarios have a different job. They are third-person prompts for assessing Capell and are never presented here as customer experience.

Field Notes

Human notes, published with permission.

A Field Note starts with a signed-in submission from someone using or testing Capell. It appears only after review and consent to publish.

Workshop table reviewing a dated Field Note and its contributor approval.
No published notes yet

No submitted Field Notes are public yet.

The prompts below are evaluator guidance, not human experience, customer evidence, or testimonials. Published notes will be clearly identified as reviewed Field Notes.

Evaluation prompt

Follow a campaign page through change

Inspect how a representative campaign page handles content structure, media, URL changes, preview, and cache invalidation as the site grows.

Evaluation prompt

Map the existing application boundary

List the routes, policies, jobs, and product logic that must stay application-owned before deciding where CMS responsibility begins.

Evaluation prompt

Test the next client handover

Check whether editors can complete routine work and whether the incoming development team can understand the site's structure, packages, and operating checks.

Publishing signal

Give the next team enough context

surface cms surface
route https://capell.app/laravel-cms
state structured

Context

Describe the starting point

Name the kind of site, the people doing the work, and the pressure that made the decision necessary.

Read Laravel CMS guide
surface cms surface
route https://capell.app/resources/comparisons
state structured

Decision

Explain the choice

Say what the team considered, what it chose, and which limitation or cost came with that decision.

Compare options
surface cms surface
state structured

Editors

Report what changed

Describe the observed effect on publishing, maintenance, handover, or the public site. Keep it factual and leave out ratings.

See editor fit
surface cms surface
route https://capell.app/roadmap
state structured

Follow-up

Include the unfinished part

Name the confusing setup, missing capability, support need, or follow-up work that remains after the decision.

Vote on roadmap
Loading footer