Projects

Projects organize your documentation — one per product, team, or topic. Each has its own documents, access level, and collaborators.

Common projects: product docs, API reference, internal wiki, knowledge base. Dundler Paper Co. keeps their DundlerOS API docs in one project and their Warehouse Service docs in another.

Create one

Select Create project on the workspace Overview or the projects list. You give it a name, and optionally a short description and an alias. A new project starts empty and private — you decide who can see it afterwards, in Project Access Control.

Name is the label across the workspace and on any public URL, up to 100 characters.

Description is an optional summary shown on project cards, up to 500 characters.

Alias is the URL-friendly identifier — letters, numbers, hyphens and underscores, up to 100 characters — used for public URLs, CLI sync and cross-project links. It has to be unique within your workspace; another workspace can use the same one. Leave it empty and one is generated from the name.

Renaming the alias later is safe: the old one is retired rather than dropped, and links written against it keep resolving. That is the same mechanism documents use — see Renaming & Redirects.

How many projects you can have depends on your plan; the allowance is under Settings → Plan & Billing.

In this section

Project Settings — Edit general settings, change the alias, or delete the project.

Project Access Control — Choose who can see your project: private, unlisted, or public.

Project Collaborators — Give Members elevated access on a single project — write, delete, or admin — without changing their workspace role.

Custom Fields — Add structured fields — status, owner, version — to every document in the project.

What’s next?

Documents — Fill your project with documents.

Public Showcase — Reorder public projects on your showcase page.