Some things a team needs aren't a task, a note, or a board. They're a page — a printer directory with everyone's IP addresses, a links hub for a department, a runbook, a one-page policy that people need to find rather than read in a thread.
Page is a new project item for exactly that. You write HTML, you get a page. It lives with the project it belongs to, so it's found where people are already looking rather than in a folder someone shared once in 2023.
What it is
An editor and a live preview. Write or paste HTML, watch it render as you type, save. Out of edit mode it's just the page.
It's raw HTML on purpose. Not a block editor, not a restricted subset — real markup, real CSS, and real JavaScript if you want it. That means a printer directory can have a working search box and a sort control, because those are twenty lines of script and no amount of block editing gets you there.
If you want somewhere to start, we built a printer directory as the first one: search across name, model, room and IP; group by building; sort A–Z or by status so the broken ones float up; and a copy button on every address, because copying an IP is the single most common thing anyone does with a page like that.
How we made it safe
This is the part worth being straight about, because "paste in any HTML" and "shared team workspace" are two things that don't obviously belong together.
A page's HTML never touches the app. It renders inside a sandboxed frame with no access to the page around it — no cookies, no session token, no reading of anything in your workspace. Scripts still run, so your search box works, but they run in an isolated origin that can't see out.
We tested that rather than assuming it. In a real browser, a page's script can execute; its origin reads as null; and any attempt to reach the parent document, local storage or cookies throws. It also can't reach out and remove its own sandbox, which is the usual way this kind of isolation gets defeated.
We deliberately don't strip anything from your HTML on the way in. Filtering <script> would break the feature, and worse, it would imply the stored markup is safe to use somewhere else one day. It isn't, and it never will be. The frame is the boundary, and it's the only one we rely on.
Limits
A page can be up to 250 KB, and a project can hold ten. Both are enforced on the server, and the editor shows you the count as you type rather than failing when you save.
Page content is encrypted at rest like your notes are. A printer directory is a map of an internal network, and it's treated that way.
Availability
Page is on Pro and Max individual plans, and on Team org plans and above.