Localization life cycle, account-level permissions, and a more reliable editor
P1 · September 2026
New features and improvements
Better localization lifecycle: Building on top of the localization capabilities from previous releases that allowed to define locales from your site and translate content, users can now utilize a powerful system that allows to keep in synch translations with their source documents all along the lifecycle of the content, while leaving full freedom to adapt and modify the localized content. Freedom with control.
Starter components now available in the create site CLI: When creating a new site, you're now asked whether to include the p1-starter-components library. Teams building their own components can cleanly opt out instead of having demo components forced in.
Clearer data source UX in the page editor: The data source panel has a clearer database icon (replacing the old "AI" glyph), an updated look and feel, and a short description explaining what data sources are for.
User permissions and role: P1 simple permissions and roles have been fixed and applied consistently on both dashboard and visual editor as documented.
Fixes and refinements
Editor and Visual Editor
- Fixed P1 sign-in and welcome screens being unreadable on dark-themed host sites.
- Fixed adding a Button component crashing page load and stranding the editor on "please select a page" with the workstream reset to main.
- Dynamic pages rendered from a data source now appear in Site Structure.
- The "Create Page" modal no longer strips colons from the URL Slug field, so dynamic route params work.
- Fixed two unrelated block types both showing as "List"; only the Data List block type is maintained.
- The List block sidebar now reflects the auto-detected field mapping instead of showing "None."
- Fixed a "Changes pending publishing" badge appearing on a non-current version in Version History preview.
- Fixed clipped dropdown fields on the right dropdown
Workstreams, publishing, and localization
- Fixed ?branch=main being classified as a non-main branch, which had denied by-path published reads.
- Fixed a merge discarding a translation review that the receiving workstream had recorded while the merging workstream was open.
Accounts and permissions
- New sites now land in the currently selected organization / Business Account instead of the creator's own org.
- Fixed organization resolution sending new sites to archived or inactive Business Accounts.
- Fixed defects found while testing the new permissions across the Visual Editor and Dashboard.
SDK and starter kit
- New starter-kit scaffolds no longer fail to install due to unresolved workspace dependencies.
- Published npm packages no longer ship dead sourcemaps, removing noisy warnings on a fresh project.
- Continued SDK consolidation: moved the SEO/metadata layer into p1-next-sdk, made puck-css styling self-contained and exported its rich-text sanitizer, added a createP1EditorClient factory with customization slots, and moved the merge-review UI into the SDK.