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.

Business Account (BA) refinement

Current behavior Scenario 1 - Self-serve signup If Person A signs up, they select the BA name and the BA is created with them as Owner. Under the hood, we entitle in Stigg, making the user a customer on Stigg (on a free plan for self-served). Scenario 2 - Invited by an existing org member If Person A is invited by Hitanshu to "Hitanshu's Org", Person A does not get their own BA and is added as member/admin to Hitanshu's Org. Under the hood, no Stigg customer entitlement is created. There is an option somewhere in the UI to "Create my own business account". Scenario 3 - Create my own BA When the user goes through "Create my own business account", they are doing a regular owner signup (same as Scenario 1). This includes the Stigg free-plan entitlement. Problem: The BA concept is still unclear to users landing on the dashboard in any BA Sites which might be created in one BA need to be capable of moving to another BA This epics includes proper UI to allow to do the minumum required management to allow agencies and customers to see which BA they can work in and to transfer sites from one BA to another. UI for landing page - select which BA you want to work on - https://claude.ai/design/p/07104b22-fba0-4f32-90cd-d22fd0ad1cf5?via=share&file=BA+Landing+Home.dc.html|smart-link UI to transfer SITE/migrate BA, migrate BA will be bulk transfer of all sites to target BA and archive the BA

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.

Commenting on pages in Visual Editor

Problem Without this feature, user can only comment on blocks and there no place to create a comment that would relate to the entire page. Proposed Solution As a user, I can create a comment thread attached to the full page. The comment should show on the Visual Editor in a way that makes it clear it's a comment about all the page content. Design To be added here

Thread management and inbox

Problem As a user, I don't have a simple way to access all the comments I am involved in, either as created by me or in which I was tagged. For the thread created by me, I don't have a way to edit or delete them. Proposed Solution As a user, I can access an inbox from both the Visual Editor and the P1 Dashboard where I can see and manage all the threads I am involved in. Once in a thread in the inbox, I can click on a button or link to look at the comment in context. The inbox allows me to see the unseen comments, the seen comments and the archived comments distinctly. As a user I have the ability to go back to the messages of any thread I have contributed to and can edit the message to update it and save it or to delete it. When a message is deleted, it is replaced by a dotted line / greyed message saying "message deleted". Design To be added here

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 on selected content in Visual Editor

Problem Without this feature, user can only comment on blocks and it can be unclear what the comment refers to, especially when blocks are big or when the user wants to comment on a very specific part of a page. Proposed Solution As a user, I can create a comment thread attached to any selected content (text or media) on the Canvas of the Visual editor. Commenting thread will show next to the selected content. Design To be added here

Commenting on the site live pages (without /p1 editor)

Problem Users don't always want to load the visual editor and load each given page to make a comment, they might prefer to go faster, simply browsing a site live (or a workstream preview) and commenting directly on the site. Proposed Solution As a P1 user authenticated to a P1 site visual editor (eg. mysite.com/p1), I can comment directly on the site pages on selected content (eg. loading mysite.com /anypage , authenticated to the P1 sdk for that site, I can comment directly on the page by selecting some content. Similarly, I can see a comment icon for any comment having be made on the page. Design To be added here Note: we could use a keyboard shortcut to enter "commenting" mode or use a button in the "P1 command center".... competition: https://vercel.com/docs/comments/using-comments

User notifications about P1 events

Problem As a user, it is difficult to keep track of comments, as we are not always opening or checking all the threads that have been created. It become very easy to miss a discussion or a request. Proposed Solution As a user, I receive notifications for events that happen in P1 that are worth alerting me. these events may include different things: Activity on comments and threads, such as someone tagging me in a comment or someone replying to one of my comments. Activity in the editor or in P1 that is worth me being notified about, such as when content is about to be published (it was scheduled), when a merge of a workstream failed, when my user reached the limits of my entitlement when it comes to tokens, or when it comes to the number of workstreams or the number of sites, and so on and so forth. Activity related to user management, such as: I have been invited to be admin of a site. I have been invited to be a member of a site. Someone tried to transfer a site to my business account. Notifications are pushed: as a new event brought to my attention in a widget appearing in the visual editor or the dashboard if I am working there. by emails. possibly in Slack if my organization uses it. possibly in MS Teams if my organization uses it. possibly by SMS if it is my choice. possibly in other collaboration tools... Some channels, such as text message, are probably not required for the initial phases, but possibly in the future. We have the requirement for one tenant to be able to define which channels to use. For instance, customer A might want to use Slack, and customer B might want to use MS Teams Technical solution: Dashboard team is working on selecting and contracting with a company providing such a service, the idea would be to leverage that service more than developing our own notification infrastructure. Initial list of events to be implemented: Someone tagged me in a comment. The notification should include a link that brings me to the comment. Someone replied to a comment I created in the editor. The notification needs to include a link to get back to the comment. Someone archived a thread I have commented in. As a business account owner, I am notified about the usage on my business account reaching the limit (as of the number of sites). The notification includes the list and a link to the P1 dashboard where metering is displayed. similarly, I am notified about reaching the limit of my token usage credits Zappy notification: When Zappy has finished the task I asked him to do, I am notified about it. The notification includes a link to the Zapier interaction Out of initial scope but for next iteration, and the technical solution should allow it: allowing for feedback within the notification channel. As an example, I'm notified about a new comment to one of my threads in Slack. I can reply in Slack to that comment. As another example, I'm notified about a new user being invited. I have to approve the new user. I can approve in the message. This is a fictional example because we don't have this feature yet, but it could be then we should also include a whole set of events that relate to preflight checks: Accessibility issue detected Brand compliance issue detected Translation drift detected on my translation Update available on the component library to install Fictional example. This might be automated, or this might never be the case, but that's an example. And Metmo Design To be added here

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.