Projects and CMS become Sites.

One fewer boundary

A project often begins with a page. Knowledge grows there, tasks emerge from it and eventually something is ready for others to see. Separating project management from content management no longer reflected that journey.

The value becomes clear in an ordinary publishing workflow: a team gathers background knowledge, agrees on statements and prepares a page for customers. Different versions serve different purposes. A shared foundation helps preserve the relationship between the brief, sources and public result. The team still decides which content should actually be shared outside the organization.

A shared foundation

Sites unifies these product areas. Website projects, public pages and the native site runtime build on the shared environment. Existing website data moves into the new structure through durable migrations.

Treat the move to publishing as a distinct editorial step. Read the page as a new visitor would: Is it understandable, are its statements supported by the underlying information, and have internal notes been removed? Also check the intended links and access. An internally shared address is not yet a public page; available publishing options depend on the object.

AIOS

01One fewer boundary

02A shared foundation

03More context for people and agents

04What comes next

More context for people and agents

When content and projects are connected, their origins remain traceable. Teams can reuse knowledge, and agents gain clearer context for the next task.

Bringing projects and CMS together is also a structural change. Existing website data moves to the new foundation through the migrations described here. For teams, the practical question afterward is whether the content still makes sense in context and the required pages can be found. Use a few familiar publications as review examples and record open questions about content, access and ownership.

What comes next

We’re developing Sites around real workflows. Our focus is clear transitions between internal knowledge, collaborative execution and public outcomes.

Try it yourself

Adapt the placeholders to your task. This example is a template for your work with AIOS.

Prepare a draft public page from [pages and files].

Audience: [Who will read the page?]
Goal: [What should visitors understand or be able to do?]
Statements that may be used: [Approved basis]
Internal context: [For understanding only; do not publish]

Provide a page title, a short introduction and a clear content structure. Flag statements that still need evidence or a decision. List the intended links and desired next step for visitors.

Create the draft first. Keep unresolved points for editorial review separate.

Three perspectives on the same content