Give structured data its own page It outgrew a section inside SEO: there is a settings screen, a page type select with nine types, an FAQ editor, breadcrumb modes, a block hook and a partial for routes Atelier does not own. Leads with what a real page emits, because the graph is easier to understand from one example than from a list of node types. Ends with how to check it, and which schemas stopped earning rich results, since half the advice online predates those changes.
Document structured data, both ways in A block can describe itself with structuredData(), and the shipped FAQ block does. But a site's blocks are usually written by whoever installed this, so typing schema on the page is the normal path rather than a fallback, and the docs now say so. Also removes the 'no JSON-LD' lines from four pages, which stopped being true, and replaces them with what is genuinely still missing: Review, opening hours, and nodes from a host app's own models.
Tidy the locale ordering section
Document changing the default locale Reordering the locales array is the whole change, and the docs never said so. Also states the trap: on a site that already has pages it rewrites every URL and writes no redirects, because the slugs themselves never changed.
Rework the wiki: six new pages, and stop the duplication Everything past installation lived in two half-pages and a lot of it was nowhere. Adds Blocks, Design tokens, Bilingual and RTL, Publishing, Configuration and Troubleshooting, each covering what was previously scattered or missing entirely. Troubleshooting is the one worth having: almost every failure mode in this package is silent, so it lists them in the order they catch people rather than by subsystem. Usage stops repeating the block-writing guide and points at it. How it works gains the pieces built since it was written: the revisions and redirects tables, layout resolution, and why tokens are stored as references. Home becomes a real index, and the sidebar is grouped rather than a flat list.
Document layouts A page can now be wrapped in whichever shell suits it, so document registering them, writing one, and the four things that bite: both partials, the data-atelier-canvas hook, guarding $page, and what happens to a page whose layout was deleted.
Add an SEO page, with a worked example for non-Atelier URLs Everything the SEO layer does was scattered across Installation and nothing documented sitemap sources, which is the part a real client site needs: a blog or a services resource with its own model and routes has URLs that belong in the same sitemap. Includes the whole example end to end, the three shapes a source can return, when to move from a closure to an invokable class, and the four behaviours that surprise people.
Updated Home (markdown)
Document using your own layout atelier.layout invites an app to replace Atelier's view, and doing so used to lose the whole head. The head now lives in two includes, so document them and the fact that leaving either out fails silently. Drops the known limit about meta tags being trapped in the layout, which is no longer true.
Name v0.1.2 as the release that needs a migration
Document re-publishing migrations when upgrading New tables ship as new migration files, so an existing install has to publish migrations again after an update. Skipping it fails late rather than loudly. Also refreshes the known limits, which said revisions did not exist, and adds the tokens key to the config reference.
Close the gaps a test agent found in the quickstart Gave the page to a model with no other context and asked what it would still have to guess. Three answers were fair: how to find the panel provider, whether Vite has to be running, and what implementing FilamentUser actually looks like. All three now answered on the page.
It is on Packagist now, so drop the VCS repository workaround
Fix the agent quickstart failing on its first command The package is not on Packagist yet, so 'composer require safi/filament-atelier' fails with 'could not be found'. The Installation page said so; the quickstart did not, and an agent following only the quickstart would stop dead at step one. Also names what to do when Filament or a panel is missing, rather than assuming both exist.
Document setup, usage and an agent quickstart
Initial Home page