Getting Started

Install on a standard Statamic site with composer require. Composer runs statamic:install, which publishes the addon’s front-end assets under the statamic-inline-edit tag using --force. If your site does not publish from Composer, run php artisan vendor:publish --tag=statamic-inline-edit --force. The older statamic-inline-edit-assets tag still works.
Look first at public/vendor/statamic-inline-edit/ for the published JS/CSS, then at the Statamic templates/fieldsets where inline editing is enabled. Check that each editable field renders a proper label—the package now uses aria-labelledby for several controls.
First use case: add inline editing to a simple front-end page with a text field. Toggle edit mode, press Enter to open the field, edit and save, then verify focus stays on the field, the status message is announced, and Escape returns focus correctly after closing the rich editor.

Implementation Patterns

Use inline editing to let content editors update front-end content without opening the control panel. Wrap the editable regions in your templates, keep field labels stable, and test both narrow and wide fields.
Keyboard-first workflow: Tab to a field, press Enter to open it, Escape or Enter to leave a text field, and Escape in the rich editor to return focus to the underlying field. When toggling edit mode from the keyboard, focus moves to the first visible field; toggling it off moves focus to the button that turns it on.
Style the editor from your own stylesheet. The focus ring is now visible on every field, offset from the dashed “editable” outline, including fields narrower than 140px that never receive the kind badge.
Rely on the status message’s role="status" live region for “Saved” and validation refusals. Save errors now wrap to a second line instead of being cut at 40 characters; test long refusal messages in your layouts.
On phones, save messages get their own row above the buttons. Verify the small panel, markdown source box, and single-value windows on mobile, since their controls are now named after their field via aria-labelledby.

Because assets are published with --force, hand edits in public/vendor/statamic-inline-edit/ are replaced on every composer install and composer update. Put style overrides in your own stylesheet instead of editing published vendor files.
Focus management is now deliberate: focus no longer drops to the top of the page, and the field that opened an overlay or in-place field is refocused after the page reloads. Avoid custom JavaScript that steals focus or rewrites DOM IDs; stable field IDs are needed for aria-labelledby.
The select, date input, switch, markdown source box, and single-value window rely on field labels for aria-labelledby. If you customize labels, keep the referenced element IDs intact or screen readers will announce the wrong field.
Debug asset issues by confirming which publish tag ran and clearing caches. If focus or announcements misbehave, check for duplicate IDs, JavaScript errors, or multiple role="status" regions competing for announcements.
MARKETPLACE.md is no longer in the Composer package. That is not a runtime concern, but update any internal docs or deployment notes that reference it.