Docs

Notelog is a published changelog with email subscribers attached. You write entries in a focused editor, hit publish, and a digest goes out to anyone who opted in. There is no project setup ceremony beyond picking a name.

1. Sign in with a magic link. The email arrives in seconds; no password to remember.
2. From the dashboard, create a project. Give it a name and a slug — the slug becomes your public URL at notelog.dev/changelog/your-slug.
3. Open the editor and write your first entry. Pick a category (new, improved, fixed, or announcement) so readers can scan. Drafts autosave; there is no save button.
4. When the entry feels right, flip the publish toggle. Subscribers get the digest right after you publish. The public page updates immediately.

Subscriptions are double opt-in. A reader enters their email on your public changelog page; we send a confirmation link; only after they click does the address join your list. This keeps the list clean and the inbox-provider reputation healthy.

The fastest way to grow the list is to share the public URL. Drop it in your launch posts, your email signature, your docs nav, your README. The subscribe field sits inline on the page — readers do not have to leave to opt in.

When you need to migrate or back up, the subscribers page exports the full list as CSV — email, status, and subscription date. Unsubscribes are handled automatically; you can also remove a subscriber manually from the same page.

By default, your changelog lives at notelog.dev/changelog/your-slug. On Pro or Business, you can point your own domain at it — usually changelog.yourcompany.com.

From your DNS provider, add a CNAME record on the subdomain (or apex) pointing to the Notelog app host. Save it in your project settings under Custom domain. Propagation usually finishes in minutes.

One honest caveat: today we do not require DNS verification. You bring a domain you control, we trust you. The hostname is unique across all projects — the second project trying to claim a domain gets a clear error and has to pick a different one. Reserved hostnames (the Notelog app, vercel.app subdomains, localhost) are blocked at the form.

The embed renders your changelog inside any page on your site — a docs sidebar, a marketing landing, an in-app “What’s new” tab. It is a sandboxed iframe, lazy loaded, with the same editorial layout as the public page.

Find the snippet in project settings → Embed. Copy it once and paste it where you want the changelog to appear:

<iframe
  src="https://notelog.dev/embed/your-slug"
  style="width:100%;border:0;min-height:600px"
  loading="lazy"
  title="Changelog"
></iframe>

The iframe inherits your visitor’s color scheme automatically. Height is fluid; set min-height to whatever fits your layout.

Business plans can override the design tokens we expose without forking the public page. You write a small CSS block in project settings; the server runs it through a sanitizer that strips anything dangerous before it reaches the public page.

The variables you can override:

:root {
  --bone-150: #f4f1ea;
  --bone-800: #1a1814;
  --accent-500: #c8472a;
  --radius-2xl: 14px;
}

The sanitizer strips <script>, <style>, @import, and any url(...) referencing javascript:, data:, or other dangerous protocols. If you need a token we do not expose yet, email us — we add them when they are requested.

Free includes one project, one hundred subscribers, and our subdomain. Pro lifts the limits, adds custom domain and the embed widget. Business adds custom CSS and removes all Notelog branding.

When you downgrade, nothing is destroyed. Entries stay. Subscribers stay. Custom domain and custom CSS get disabled — your public page falls back to the Notelog subdomain and the default design — but the underlying records remain so re-upgrading restores everything in a click.

The only hard limit on the free tier is sending: if you cross the subscriber cap, new subscribes are rejected at the form, and we email you. Existing subscribers keep receiving entries until you decide what to do.