Notes
Leave the next editor the context they need.
- Version
- 1.1.0-beta.52
- Released
- 18 November 2026
- Licence
- Free
Price Free
Check access and installationCheck compatibility before using this Beta extension
Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
On this page
- Price and access
Review the price, licence and availability before deciding what to adopt.
- What it solves
See the problem this extension removes, what your site gets, and the answers to common questions.
- Your workflow
Read how the package is used and what your application needs to provide.
- Product captures
Review the available captures and see which part of the workflow each screen demonstrates.
- Capabilities
See which jobs this extension supports and which parts it adds to your site.
- Project fit
Decide what this removes from your workload and what your application still needs to supply.
- Installation
Check the setup steps before adding the package to a project.
- Release evidence
Review the available release, maintenance and package-review information.
Check your application before checkout
What it solves
The problem
Editors lose the context of handovers when talk happens away from the page.
What your site gets
Handover notes stay attached to the page, with an inbox for whoever is responsible.
Questions buyers ask
- Can I leave notes on things other than pages?
- Not in a standard install. Notes work on pages only, unless another package registers its own records and edit screens with Notes.
- Can colleagues reply to a note, or can I edit one I saved?
- No to both. A note is a single message with no replies, and a saved note can't be edited, so add a new note instead.
- Who can read a note?
- With Record editors visibility, anyone who can edit that page can read it. With Private, only the author, the people assigned and the people mentioned can. Notes never show on the public site.
- Can a note remind someone later?
- Only after your developer turns reminders on, and until then a note saved with a reminder date is refused. Once on, a reminder can repeat and reaches the people assigned as an admin notification, as long as background jobs and the scheduler are running.
Use it in your project
Add a private note beside the record being discussed. Assign a colleague or set a reminder so follow-up appears in the right person's inbox.
Picture it on your site
For a record needing follow-up, write the context beside it and assign the colleague who can take the next action. Check that the reminder points back to the right work. Private notes are useful when they prevent context being lost between people; they should not become a second, disconnected source of customer-facing information.
Keep publishing work moving
- Add record notes with mentions and assignments.
- Track reminders and completion from a personal inbox.
Is this right for your project?
A publishing process people can follow
Start with the journey from a draft to a published page, not a list of status names. Who writes it, who checks it and who is responsible for the publication date? Choose the controls that match that journey. The benefit is a repeatable editorial process with fewer changes made outside the CMS; your team still supplies the content standards and the people who make publishing decisions.
Prove one complete release
Use a representative article or page to check editing, review, publication and the public result together. Include the site, language and related content that matter to your project. A scheduled record or approved status is only part of the result: visitors must see the right content at the right URL, and editors need to know how to correct it afterwards.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Add this free package to your account, then review compatibility and site impact before installing it.
See this extension running on the demo site.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Uses package-local configuration and Capell metadata needed to enable the feature.
- Background work
- Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
- Access controls
- Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with Capell support before removal.
-
01
Require the package
composer require capell-app/notes:^1.1.0@beta -
02
Install the extension
php artisan capell:extension-install capell-app/notes
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.0-beta.52 18 November 2026
- Recent activity
- 11 approved releases in the last 12 months
Review evidence for this release
Internal notes package reviewed with no defects found; note bodies are stored encrypted and the whole surface is admin-only with no public routes.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.52
- Approval date
- 17 November 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Reminder delivery depends on the site's scheduler and queue being running. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Capell is the trading name of Ben Johnson, a sole trader in Wakefield, UK. Capell writes, releases and supports every first-party package listed here, and replies to support requests within two UK business days.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 11 approved releasesv1.1.0-beta.5218 November 2026v1.1.0-beta.5110 November 2026v1.1.0-beta.502 November 2026v1.1.0-beta.4928 October 2026v1.1.0-beta.4820 October 2026v1.1.0-beta.4717 October 2026v1.1.0-beta.459 October 2026v1.1.0-beta.448 October 2026v1.1.0-beta.438 October 2026v1.1.0-beta.427 October 2026
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout. Lemon Squeezy is the seller of record. It adds any VAT or sales tax due at checkout and makes the VAT invoice available for each order. Purchase orders are not offered. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. When Lemon Squeezy has supplied a receipt link, Capell shows it beside the purchase; if it is missing, use the receipt help link on that purchase and support will find it for you. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.