# 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)
- [Organize with Categories](https://docs.zuwiki.com/getting-started/organize-with-categories)
- [Publish Your First Page](https://docs.zuwiki.com/getting-started/publish-your-first-page)

### 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 Visual Touches](https://docs.zuwiki.com/editor-guide/icons-and-visual-touches)
- [Rich Content Blocks](https://docs.zuwiki.com/editor-guide/rich-content-blocks)
- [OpenAPI Pages](https://docs.zuwiki.com/editor-guide/openapi-pages)

### Plans & Account

- [Plans and Limits](https://docs.zuwiki.com/plans-account/plans-and-limits)
- [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

A wiki is the top level container in Zuwiki. Most teams keep one wiki per product, team, or topic, so feel free to start small and split later if a wiki gets too crowded. How many wikis you can have depends on your plan, see [Plans and Limits](/plans-account/plans-and-limits).

## Before you start

Pick an organization. Every wiki lives inside an organization, and your role in that organization decides what you can do. If you do not see an organization you expect, ask an admin to invite you.

## Choose a mode

When you create a wiki you pick its **mode**, and this is the most important early decision:

- **Public documentation** is served on the web and read by an outside audience. Use it for product docs, help centers, and API references.
- **Internal knowledge** stays inside your organization and is read in the app. Use it for onboarding, runbooks, and anything that should not be public.

The mode shapes how access works for the whole wiki, so pick it deliberately. You can change it later, with guardrails, but it is easier to start in the right place. See [Public vs Internal Wikis](/access-sharing/public-vs-internal-wikis) for the full picture.

## Steps

1. Open the wiki list and choose **New wiki**.
2. Choose the mode: **Public documentation** or **Internal knowledge**.
3. Give it a clear title. The title is what teammates see in the sidebar, so prefer something like **Engineering Handbook** over **Wiki 1**.
4. Save. The wiki opens with an empty editor and a welcome placeholder.
5. Optional: upload an icon. A small visual cue helps when several wikis sit next to each other.

## Naming tips

- Use names that describe the audience or topic, not the format. **Customer Onboarding** is better than **Onboarding Wiki**.
- Keep it short. Sidebar space is limited.
- Avoid version numbers in the title. Pages change, the wiki itself usually does not need to be renamed.

## What comes next

A fresh wiki has no structure. Before you write a long page, take five minutes to sketch the categories you will need. The next page, **Organize with Categories**, covers that.