# Publish your first Cloud project

> Create a Nibleaf Cloud workspace, replace the starter content, publish two pages, and verify the reader experience while signed out.

This tutorial takes you from an empty account to a searchable two-page public
site. It takes about 10 minutes and does not require a credit card.

## Prerequisites

You need an email address that can receive a verification message and a modern
browser. Nibleaf Cloud is a free beta; export important content and do not use
the tutorial project for confidential material.

## Create the workspace

1. Open [Nibleaf sign up](https://nibleaf.com/sign-up).
2. Create an account and complete email verification when prompted.
3. Open the workspace and starter documentation project created for the new
   account.
4. In project settings, replace the starter project name and description.

If the verification message does not arrive, check spam and confirm that the
address is correct before requesting another message. Use the support path in
[troubleshooting](/self-hosting/troubleshooting) only for self-hosted mail; for
Cloud, report the failed delivery without posting account tokens publicly.

## Write two useful pages

Keep the first page short. State what the documentation covers, who it is for,
and the first result the reader can reach. Add a second page named **First task**
under a **Getting started** group.

Link from the introduction to the new page. The second page should contain one
real workflow or command, an expected result, and a recovery note. Placeholder
marketing text does not test navigation or search.

Wait for the editor status to report **Saved** after each substantial edit. See
[authoring](/use-nibleaf/authoring) for the safe editing workflow and
[Markdown and MDX](/use-nibleaf/markdown-mdx) for supported syntax.

## Preview and publish

1. Open **Preview** for both pages.
2. Test the internal link, code blocks, heading outline, and mobile width.
3. Select **Publish** and wait for the deployment to become ready.
4. Open the public URL in a private or signed-out browser window.

The publish is successful when the homepage and deep link return content, a
phrase from the second page appears in search, and an unknown path returns a
404. A ready deployment badge alone does not test access or routing.

## Prepare to share the site

Review the logo and favicon, top and footer links, call to action, site title,
description, indexing setting, analytics preference, languages, and public
domain. Add a custom domain only after the default project URL works.

Cloud remains a beta service. Before moving business-critical documentation,
read [known limitations](/reference/known-limitations) and export a recovery
copy of the project.