P1 Search Backend

The search foundation for P1, indexing your content so both site visitors and your team can find what they're looking for.

Front-end site search via P1 Search Component

Add search to the sites you build with P1, so your visitors can find content --- a table-stakes capability provided out of the box.

Global Search in P1 Dashboard

Search across all your sites' content from the dashboard, so you can jump straight to what needs work instead of clicking through each site's structure.

Page Search in P1 Visual Editor

Find the page you need in the visual editor by its content, not just its title --- a real help on sites with lots of pages.

Search in P1 Dashboard Site Structure

Search within a site's structure in the dashboard to locate pages by their content, not just their name or slug.

Core Upstream for P1 Beta

Package the standard installation of the P1 starter kit with the latest P1 Block Library as a core upstream available for all subscribers. The upstream should show as follow, with a link to request beta access: Upstream should support both GitHub and Gitlab just as the Next.js core upstream does. Acceptance criteria: Upstream is functional. P1 release process is upgraded with an update of the P1 Beta upstream each time we release a new version of the starter kit.

Integrated Site Creation & Build

Create a new P1 site in one simple step from the P1 dashboard, instead of juggling both the hosting platform and P1 separately.

Bulk import of P1 Content at site creation

Start a new site preloaded with example content from a blueprint, so users get a ready-to-explore site rather than an empty one.

Guided Tour for sandbox site

Add a guided, in-product tour on top of a sandbox site, walking new users through key tasks so they quickly see how P1 delivers value.

Instant private sandbox access

Create site blueprints --- with your own components, templates, and content --- to invite prospects into a ready-made P1 site they can try out instantly.

Management of global site blocks

Reusing content from some specific pages on new pages can somehow be done by binding props or even the whole block and dynamically reusing it. This is however not providing the expected editorial experience when looking at using blocks that are used across many pages. It’s complex and not natural and won’t be adopted by users. The expected experience is more for site administrators to manage a centralized repository of global site blocks not yet placed on any page. From there, to edit specific pages, browse the global list of blocks built from the site components, pick and place these blocks. A global site block can be based on one of the site component (example: a menu), it could also be build from several components, possibly nested. Editors can use the P1 Editor (or another P1 tool) to manage the content of that block, content is managed once and published, automatically used in all the pages it has been placed.

Manual creation of redirect for a site

Create redirects yourself in the dashboard, pointing any old URL to a new destination --- not just the automatic ones P1 makes when you move a page.

Menu & Navigation Builder

Build the menus that guide people through your site. Link to your own pages, point to external URLs, or let a menu fill itself from a section --- like listing every post under /blog automatically.

Support file upload and distribution

Offer file downloads on your pages --- upload files directly in P1 and share them, with access control, instead of relying on an external system and manual links.

Scheduling Live page publishing

Schedule a page to go live at an exact day and time, so time-sensitive content publishes on its own even when no one's available to hit publish.

Manually connect P1 workstream to multi-dev environment

Keep code and content in step by linking a P1 content workstream to its matching development environment, so changes on both sides move together instead of drifting apart.

Automated multidev creation for workstreams

When you create a new workstream, P1 can automatically spin up a matching development environment, so work can be previewed and code changed without manual setup.

Scheduling Workstream releases

Schedule a whole workstream release for a set day and time, so time-sensitive content goes out without someone needing to trigger it manually.

Commenting and Collaboration System (threads mvp)

Comment and collaborate right where you work --- in the visual editor, on the preview, and on the live site --- the way you would in Google Docs or Figma. Leave feedback in context and resolve it together.

Portfolio level workstreams

Run initiatives that span several sites at once --- managing the content, design, and code changes for a cross-site project like a rebrand in one coordinated workflow.

Centralized User Management Interface

One screen to manage a person's access across your organization --- which sites and workstreams they can work on and in what role, including 'all sites' in a click.

Audit Trail for website and portfolio owners and managers

A searchable history of who did what, when, and where across your whole portfolio --- see every change and action, not one site at a time.

Configurable role and permission system

Tailor roles and permissions to how your organization works --- from a few simple roles to fine-grained control down to the document level.

Webops Quality Check, Fix & Optimize

Use AI to spot and fix content issues across accessibility, SEO, branding and tone, compliance, and translation --- keeping your site healthy without manual audits. Use AI to spot and fix content issues across accessibility, SEO, branding and tone, compliance, and translation --- keeping your site healthy without manual audits.

Backup, export and restore site content

Back up your content --- manually or automatically, per site or across your whole portfolio --- and export or restore it whenever you need to.

P1 Content Portability

Own your content: export and move it out of P1 whenever you need to, so you're never locked in --- the reassurance teams expect from open ecosystems.

JSON-LD automatic generation

Automatically generate valid JSON-LD from the blocks on each page, improving how search and AI platforms discover your content without hand-writing markup.

Automated OG metadata based on page content

Get Open Graph metadata suggested automatically from a page's content when you publish, saving time and keeping social previews consistent.

Form Builder

Build forms to capture visitor information and connect it to other services --- create them in the visual editor or dashboard, then drag them onto any page.

Media Management in Dashboard

Goal: provide dashboard level access to the Media assets being used by a site. Acceptance: One place to see all media assets used by a given website Ability to upload new assets one by one or bulk upload Ability to update assets with new files and push updates to all components using the asset Ability to delete the assets with a clear active confirmation when assets are used, so that users could first update the pages using the asset Ability to update metadata linked to the assets Ability to push metadata updates to all components using the assets

Portfolio level asset management

Reuse images across all your sites, not just one --- upload once and use the same optimized, CDN-delivered asset anywhere in your portfolio.