Documentation

These guides cover the whole product, screen by screen: making an account, writing a post, putting the blog on a domain you own, changing how it looks, adding the pages that are not posts, giving readers a feed, taking your work back out again, and doing all of it from a terminal instead. Each one is written against the real interface, so the field names and buttons here are the field names and buttons you will see.

Nothing here assumes you have used a blogging platform before. Nothing here assumes you know what a CNAME record is either — the guide that needs one explains it. If you want the list of what the product does rather than how to do it, that is thefeatures page.

Start here:Getting startedtakes you from no account to a published post in one sitting. Everything else assumes you have done that first.

The guides

• Getting started

  Create an account, make your first blog, publish a post.

• Writing and publishing

  The editor, drafts, slugs, tags, images, and excerpts.

• Custom domains

  Point a domain at your blog and get SSL automatically.

• Themes and design

  Pick a theme, set typography, colours, and reading layout.

• Pages beyond posts

  Albums, recipes, bookshelves, guestbooks, now pages.

• Feeds and discovery

  RSS, Atom, JSON, per-tag feeds, and the web ring.

• Export and backup

  Take everything with you, whenever you want.

• Using the terminal client

  Install the CLI, sign in, and publish from the shell.

Reference, not guides

Three things on this site are documentation but are not part of the eight guides above, because they are reference material rather than something to read start to finish.

• The REST API reference— endpoints, Bearer-token authentication, and the JSON each one returns. Useful if you want to publish from your own script.
• The terminal client— what the Rust CLI is, what its full-screen interface looks like, and how to install it. TheCLI guideis the walkthrough; that page is the tour.
• Importing an existing blog— one page per source, since moving in from WordPress is a different job from moving in from Substack.

If a guide does not answer it

Write to hello@ultrv.com. A person reads it. If the answer turns out to be something these pages should have said, it gets added here rather than just sent back to you.