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.
Give the next team enough context
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 guideDecision
Explain the choice
Say what the team considered, what it chose, and which limitation or cost came with that decision.
Compare optionsEditors
Report what changed
Describe the observed effect on publishing, maintenance, handover, or the public site. Keep it factual and leave out ratings.
See editor fitFollow-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