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.
Choose which optional cookies Capell may use.
Required for Capell to work — login, security, page rendering.
Anonymous usage telemetry to improve editor performance.
Personalization for the Capell marketing site.
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.
Evaluator scenarios have a different job. They are third-person prompts for assessing Capell and are never presented here as customer experience.
A Field Note starts with a signed-in submission from someone using or testing Capell. It appears only after review and consent to publish.
The prompts below are evaluator guidance, not human experience, customer evidence, or testimonials. Published notes will be clearly identified as reviewed Field Notes.
Inspect how a representative campaign page handles content structure, media, URL changes, preview, and cache invalidation as the site grows.
List the routes, policies, jobs, and product logic that must stay application-owned before deciding where CMS responsibility begins.
Check whether editors can complete routine work and whether the incoming development team can understand the site's structure, packages, and operating checks.
Context
Name the kind of site, the people doing the work, and the pressure that made the decision necessary.
Read Laravel CMS guideDecision
Say what the team considered, what it chose, and which limitation or cost came with that decision.
Compare optionsEditors
Describe the observed effect on publishing, maintenance, handover, or the public site. Keep it factual and leave out ratings.
See editor fitFollow-up
Name the confusing setup, missing capability, support need, or follow-up work that remains after the decision.
Vote on roadmap