A PDF goes stale the day after you send it. A published site doesn't: Publish turns the documentation into a read-only web page that anyone you give the link to can open — no Odara account needed — and you decide how much it shows and who gets in.
Goal
A published version of the course project, protected by a password, and a clear idea of what a reader without an account can see.
You'll need
- Level 8.1 done.
- About 15 minutes.
Steps
1. Choose what goes out
In Documentation, click Publish.

| Field | What it does |
|---|---|
| Title | The heading readers see |
| URL slug | Part of the address — lowercase letters, digits, hyphens |
| Include | Project overview on/off; Pipelines, Maestros and Resources each All, Selected… or None |
| Access | Public (anyone with the link) · Link + password · Expiring link (7, 30 or 90 days) |
| Screenshots | Render any missing diagram before publishing |
Set Access to Link + password and choose a password. Keep Include on All for now.
2. Publish
Click Publish. A Published! box shows the link, and the publication appears under Existing Publications with three buttons:

- Copy — the link.
- Bump — publish a new version with today's content; the link keeps working and shows the latest.
- Revoke — take it offline.
3. Open it as a reader
Open the link in a private window — as someone without an account would:

A wrong password is refused. The right one opens the documentation:

The same overview, sidebar and pages as inside Odara — read-only, and with connection details
(host, port, user) shown as (hidden). There's no session: whoever opens the link types the password each time.
Expected result
- The link opens a password prompt; the right password shows the documentation.
- Revoke makes the link stop working.
- After you change a pipeline, Bump puts the change on the same link.
Common pitfalls
The link says localhost and doesn't open for anyone else.
The link uses the address you opened Odara at — so if that's localhost, so is the link. Readers
open the page on the Odara server: if Odara runs on your laptop, nobody else can reach it.
Publishing is for an Odara on a server your readers can reach; open Odara at that server's address
before publishing (or have whoever runs it set ODARA_PUBLIC_BASE_URL, which always wins).
Public shows more than you think.
Published pages hide where your systems live — host, port, user and connection strings read
(hidden), and passwords are never shown — but they still show file paths, queries and every
included pipeline's logic. Use Link + password or an expiring link, and Include → Selected… to
publish only what a reader needs.
Someone still has an old link. A link stays valid until you Revoke it or it expires. Revoke is the way to take something back.
What you built
A live, access-controlled view of your project for people who will never open Odara. That's the end of World 8 — and of the main track's content. The capstone puts all eight worlds into one pipeline.
Check yourself
One question, drawn from a larger bank. Get it right to pass.
Which access mode keeps a link from working after a while?