Since Notifuse 17, every workspace can run a blog. You write posts in the console, Notifuse serves them on your own domain with RSS and JSON feeds, and the subscription form under each post adds readers to your lists. Your articles and your newsletter live in the same place, and you have no separate CMS to host and keep in sync. The blog you are reading runs on it.

Your domain

The blog answers at the root of the workspace's Custom Endpoint URL, the domain the links in your emails already use for unsubscribing and tracking. Set it to https://blog.example.com and the blog serves:

  • /, the latest posts, with /?page=2 and on for older ones.

  • /announcements, the posts of one category.

  • /announcements/hello-world, a single post.

The console lives at /console. On a domain whose workspace has no blog, / redirects there.

The editor

Posts are written in a block editor, in the spirit of Notion. Type / to insert text, headings, lists, a quote, a code block with syntax highlighting, a separator, an image or a YouTube video. Select text to make it bold, italic, underlined, struck through, code, a link or coloured. Each block has a handle to drag it elsewhere, duplicate it or copy a link to it. Images come from your file manager, with a caption and alt text.

Beside the text are the slug, category, reading time, authors with their avatar, excerpt, featured image and SEO fields. A table of contents follows your headings, undo and redo sit above the editor, and a copy kept in the browser restores text from a closed tab. If someone else saved the same post while you were writing, saving asks whether to overwrite their version or load it.

Since Notifuse 22, an AI assistant beside the editor can also write a whole post with its title, excerpt and SEO fields, using your own Anthropic, OpenAI or Gemini key. The OpenAI integration accepts any OpenAI-compatible endpoint, such as OpenRouter. The assistant has its own post on this blog.

Publishing

A new post is a draft, visible only in the console. Publish it now, or choose Set Publication Date with a date, a time and a timezone. A past date back-dates the post, for an article brought over from another blog. A future date marks the post as Scheduled in the console, and the post appears on the blog and in its feeds on that date. Unpublish takes a post offline; to change a published post's date, unpublish it and publish it again. Every post belongs to one category, and deleting a category deletes its posts with it.

Pages are cached for five minutes; editing, publishing, unpublishing or deleting a post, publishing a theme or changing a list empties the cache. Everything the console does is also in the API, from blogPosts.create to blogPosts.publish, documented in the API reference since Notifuse 42. Under the Blog permission, write access also lets a member turn the blog on and change its settings.

Feeds

Since Notifuse 29.4, the blog publishes an RSS feed at /feed.xml and a JSON Feed at /feed.json, plus one of each per category, such as /announcements/feed.xml. Every page carries the autodiscovery links, so a feed reader finds them from the blog's address. A feed holds the latest 20 posts with their full text, links made absolute and scripts removed; Settings → Blog lowers that number or switches to excerpts only. A post enters the feeds on its publication date. Since Notifuse 44, the blog's sitemap.xml lists every post with the date of its last change, and the page and feed of each category.

Themes

The look of the blog comes from a theme, eight files you edit in the console: home.liquid, category.liquid and post.liquid for the pages, a header, a footer and shared snippets, styles.css and scripts.js. They are written in Liquid, the language of your email templates, and you control every tag of the HTML, CSS and JavaScript. A theme reads the blog's settings, the post with its table of contents, the posts and pagination of list pages, the categories and the public lists.

Next to the code, a sandboxed preview renders the Home, Category and Post pages with sample content as you type.

Versions

Saving changes to the live theme creates a new version, with optional notes, and leaves the live one untouched. Add ?preview_theme_version=4 to any page of the blog to see version 4 on your real posts, without the cache. Publishing a version switches every page at once, and to roll back you publish the previous one.

Default theme

Turning the blog on creates and publishes a Default theme, inspired by Medium: a featured post above a grid, a category bar, pagination, a table of contents beside long posts on wide screens, and a subscription form.

Newsletter sign-ups

The Default theme's form subscribes the visitor to every public list of the workspace. On a double opt-in list, the address lands pending and receives the confirmation email. An existing contact is not overwritten, and repeated attempts from one email or one IP are rate-limited. If no list is public, the form says so. To promote a single list, make only that one public, or narrow the list IDs in the theme's scripts.js.

Search engines

Each post and category carries its own meta title and description, social share title, description and image, canonical URL and keywords. Settings → Blog holds the defaults for the whole blog, robots directive included, with its title, logo, favicon and posts per page. The blog also serves a robots.txt that lets every crawler in and names its sitemap.xml.

Two examples

Product updates

This blog is one: two categories, product and engineering, one post per big feature dated at its release, and the newsletter form under each post. Readers who prefer a feed reader follow /feed.xml.

Your own design

Open the theme, add a call to action to post.liquid with your brand colours in styles.css, and save: that makes version 2. Check it on a real post with ?preview_theme_version=2, then publish it.

Not yet

  • A post page receives no list of related posts to suggest.

  • The Default theme is the only one to start from, so other designs mean editing it.

  • The blog runs only at the root of a domain and can't live under a path such as /blog of an existing website.

  • Once a post is created, its slug can't be changed in the console.

Getting started

If you self-host, upgrade to Notifuse 44. In Settings → General, set the Custom Endpoint URL to a domain that points to your instance: the blog can't be turned on without it. Then, as the owner or a member with Blog write access, open Settings → Blog and click Enable Blog: the Default theme is created and published. Create a category in Blog, write your first post and publish it. The setup guide, the posts documentation and the theme documentation, with every Liquid variable, cover the rest.