# Zuwiki

## Rich Content Blocks

> Category: Editor Guide

---

## 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)

---

# Rich Content Blocks

The editor is more than plain Markdown. On top of the basics covered in [Markdown Basics](/editor-guide/markdown-basics), it offers a set of richer blocks that render as proper components for the reader, while still living inside the page as content.

## The slash menu

Type `/` on an empty line to open the block menu, then keep typing to filter. Pick a block and it is inserted where your cursor is. This is the fastest way to add anything beyond a paragraph.

The menu covers the everyday structure you already know:

- **Headings** (levels 1 to 3)
- **Bullet list**, **Numbered list**, and **Task list** with checkboxes
- **Quote**, **Code block**, **Table**, and a **Divider**
- **Image**

## Components

Alongside the basics, the editor provides components that make documentation easier to scan:

- **Alert**: a callout box for an info, success, warning, or error note. Use it to pull one important sentence out of the flow.
- **Steps**: a numbered, vertical sequence for setup guides and procedures, where order matters.
- **Tabs**: switch between panels in place, for example one tab per operating system or per language.
- **Button**: a prominent call to action that links somewhere, internal or external.
- **Keyboard**: render a key or shortcut, like a real keycap, for documenting hotkeys.
- **Book shelf**: a row of linked cards, handy as a landing section that points readers at the next pages.

## Themed blocks

For game and community wikis there is also a set of Minecraft themed blocks, including inventories, items, commands, advancements, a HUD, and signs. They are there when you need them and stay out of the way when you do not.

## Keeping it readable

Rich blocks are seasoning, not the meal. A page that is all callouts and tabs is as hard to read as one with none. Reach for a component when it genuinely clarifies something: steps for a real procedure, an alert for a real warning, tabs for a real either or. Otherwise, plain prose wins.