# Zuwiki

## Create your first wiki

> Category: Getting started

---

## Pages

- [Welcome to Zuwiki](https://docs.zuwiki.com/welcome-to-zuwiki)

### Getting started

- [Create your first wiki](https://docs.zuwiki.com/getting-started/create-your-first-wiki)

### Core concepts

- [Wikis, categories, and pages](https://docs.zuwiki.com/core-concepts/wikis-categories-and-pages)
- [Page lifecycle](https://docs.zuwiki.com/core-concepts/page-lifecycle)
- [Page history and restore](https://docs.zuwiki.com/core-concepts/page-history-and-restore)

### Access & Sharing

- [Public vs internal wikis](https://docs.zuwiki.com/access-sharing/public-vs-internal-wikis)
- [Visibility for public wikis](https://docs.zuwiki.com/access-sharing/visibility-and-access)
- [Share links](https://docs.zuwiki.com/access-sharing/share-links)
- [Access grants](https://docs.zuwiki.com/access-sharing/access-grants)
- [Classification and sensitivity](https://docs.zuwiki.com/access-sharing/classification-and-sensitivity)

### Editor guide

- [Markdown basics](https://docs.zuwiki.com/editor-guide/markdown-basics)
- [Linking between pages](https://docs.zuwiki.com/editor-guide/linking-between-pages)
- [Icons and images](https://docs.zuwiki.com/editor-guide/icons-and-images)
- [Rich content blocks](https://docs.zuwiki.com/editor-guide/rich-content-blocks)
- [OpenAPI pages](https://docs.zuwiki.com/editor-guide/openapi-pages)

### Plans & Account

- [Custom domain](https://docs.zuwiki.com/plans-account/custom-domain)
- [Zuwiki for open source](https://docs.zuwiki.com/plans-account/zuwiki-for-open-source)

### Integrations

- [MCP Server](https://docs.zuwiki.com/integrations/mcp-server)

---

# Create your first wiki

From an empty account to a published page takes a few minutes. The only decision that is hard to take back later is the mode, so start there.

## 1. Create the wiki

Open the wiki list and choose **New wiki**. Pick the organization it belongs to, because your role in that organization decides what you can do there. Then choose a mode and a title.

The **mode** decides who can read the wiki:

- **Public documentation** is served on the web for an outside audience. Product docs, help centers and API references belong here.
- **Internal knowledge** stays inside your organization. Onboarding, runbooks and anything else that shouldn't be public belongs here.

You can switch later, but with guardrails, so it is worth a moment of thought. If you are unsure, start internal. Opening a wiki up later is a single switch, and nothing gets published by accident in the meantime. The full comparison is on [Public vs internal wikis](/access-sharing/public-vs-internal-wikis).

For the title, name the audience or topic rather than the format: **Customer onboarding** is better than **Onboarding wiki**. Keep it short, since the sidebar is narrow, and leave version numbers out. You can also upload a square icon, which helps when several wikis sit next to each other. 256 by 256 pixels is plenty.

How many wikis you can have depends on your plan, see the [pricing page](https://zuwiki.com/pricing).

## 2. Write a page

Add a page in the editor sidebar, give it a title and start writing. A new page is a **draft**, so only editors can see it.

## 3. Publish it

Read the page once from top to bottom, then switch its status from **Draft** to **Published**. There is no approval step, so think of it as saving for readers rather than shipping a release.

Before you do, check that:

- the title says what the page is about
- the first paragraph tells readers what they will learn
- code blocks have a language, so they get syntax highlighting
- related pages are linked where a reader would ask what comes next

You can keep editing a published page. Every save is kept in the [history](/core-concepts/page-history-and-restore).

## 4. Add structure when you need it

Don't plan the sidebar up front. Once you have two or three pages that belong together, group them in a category. How to decide is covered in [Wikis, categories, and pages](/core-concepts/wikis-categories-and-pages).
