Blogging Process

Content creation and blogging are an effective way to communicate with our community. The process for publishing a blog is as follows:

  1. Raise an issue for the content in our private Github repository.
  2. If the content is date specific create an 'all day' event on the Google Calendar FlowFuse Publishing Schedule, include a link to the issue in the event description. If you don't have the permission to create events please ask our Google Workspace admin to give you access.
  3. If you want to work on the content immediately please triage the issue into our development board.
  4. Create the draft blog post in a Google Doc. The document should be stored in the Marketing -> Content folder. Everyone at FlowFuse should be given access to comment on the document. Add a link to the document in the GitHub issue.
  5. Ask people to review the document draft by sharing it directly with them using the Share button in the document. This will send your reviewers an email notification.
  6. As a document reviewer, you should leave red-line edits in the document or add comments to the document.
  7. Once the document is finished, create a new branch of the website repository and then follow our standard development processes. Google Docs has an extension to convert the document to markdown.
  8. It is OK for you to merge your own PR to main without review where the content is urgent or has been reviewed outside of Git but where it is practical to follow the standard process we encourage you to do so.

Blog CMS

When creating a blog post there are several headers which are used by the CMS to populate the blog article as well as the blog index page. e.g:

title: The title
subtitle: The subtitle
description: The description
date: 2022-12-20
authors: ["rob-marcer"]
- posts
- node-red
- how-to

above more
below more


The title of the page can be seen on both the blog index and the articles.


The subtitle is only shown on the articles.


Provides the (OpenGraph) description used when sharing a post on social media. Also used on the /blog page for past articles.


The data can be seen on both the blog index and the articles.

The date field in the blog post front matter serves a crucial role in determining when a blog post is published. You can set this field to a future date if you wish to schedule your blog post for publication on a specific day. See the Scheduling a blog post section for more details.


The author can be seen on both the blog index and the articles.


Tag your content appropriately from the collection of tags that help us manage our blog content. They include:

  • node-red
  • flowfuse
  • how-to
  • dashboard
  • community
  • releases
  • news
  • unified-namespace

There's a page with a collection of posts for each tag in that list.

Custom Tags

You can also add your own custom tags. While these won't create a new page with a collection of posts, they will help suggest related articles. Keep in mind that for an article to be considered related, the majority of tags must match, with allowance for a difference in one tag.

Meta Keywords

Additionally, the tags you assign to your content will also be used as meta keywords for each article, alongside the default keywords.

More tag

The '<!--more-->' tag is used to define the text shown in the blog index from each article.

Example blog index item based on the header above

Example of how the headers are shown on the blog index

Example blog article based on the header above

Example of how the headers are shown on blog articles

Writing content

FlowFuse blog posts are written in markdown. To learn how to style content and have a nice markup for your content, please read the markdown guide

Scheduling a blog post

By setting a future date, the blog post will be automatically scheduled for publication on the specified date. This allows contributors to plan ahead and coordinate blog posts with events or marketing strategies. The post will be published at the next deploy after the date is set, a daily deploy is done at noon GMT.

Feel free to request reviews and merge your blog post when it's ready, even if the publication date is set in the future. This provides the flexibility to collaborate, make revisions, and ensure the content is polished well before it goes live. The post, to be published in the future, will be rendered when developing locally and on deployment previews.

By utilizing the scheduling feature, we can maintain a consistent and organized publishing schedule without the need for last-minute adjustments.