- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Secure Development Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- strategy
- values
- Operations
- Product
- Feedback
- Metrics
- Node-RED Dashboard
- personas
- Plan
- Pricing Principles
- Product Categories
- Responsibilities
- Strategy
- Versioning
- Customer department
- customer
- Engineering & Design Practices
- Design
- Engineering
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Releases
- Security Policy
- Website A/B Testing
- Internal Operations
- People Ops
- Sales & Marketing
- Marketing
# Blog
# Blogging Process
Content creation and blogging are an effective way to communicate with our community. The process for publishing a blog is as follows:
- Raise an issue for the content in our private Github repository.
- 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.
- If you want to work on the content immediately please triage the issue into our development board.
- 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.
- 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.
- As a document reviewer, you should leave red-line edits in the document or add comments to the document.
- 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.
- 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"]
tags:
- posts
- node-red
- how-to
---
above more
<!--more-->
below more# Title
The title of the page can be seen on both the blog index and the articles.
# Subtitle
The subtitle is only shown on the articles.
# Description
Provides the (OpenGraph) description used when sharing a post on social media. Also used on the /blog page for past articles.
# Date
The data can be seen on both the blog index and the articles.
# Authors
The author can be seen on both the blog index and the articles.
# Tags
Tag your content appropriately from the collection of tags that help us manage our blog content. They are:
node-redflowfusehow-todashboardcommunityreleasesnews
# 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 blog article based on the header above
# 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