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.

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.

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.

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.

Improved Site Localization Toolkit

Problem: We shipped a very powerful localization framework with P1, focused on CCR and on the editor, but the way localization is implemented on the sites build with P1 is still complex and unclear to users and developers. Among others, the localization as implemented hard code how localized document are stored, postfixing the documents with a ".locale" string, which rarely is what the users are expecting. Solution: While keeping different options for the routing of localized content (could be dedicated subdomain, /locale route before the document route, or possibly others) provide a default that is what most people expect, and make it configurable: Most users we interviewed expect that having source content at mysite.com/document-route, a good option for localization could be mysite.com/locale/document-route (eg: mysite.com/fr-fr/document-route ) Provide a site setting that could disable this option and offer the "postfix" ( document-route.locale ) or a different domain mapping ( myfrenchdomain/document-route ) The tool should also allow developers to use a REACT /Next.js utility to build navigation options such as: local selector for end user (eg. a modal letting the user select in which language she wants to browse the site) localized navigation elements (menu, footer. etc...) storing user preferences...

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.

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.