Skip to content

Release blog post: FlowFuse 2.28#4686

Merged
dimitrieh merged 13 commits intomainfrom
feature/blog-release-2-28
Mar 12, 2026
Merged

Release blog post: FlowFuse 2.28#4686
dimitrieh merged 13 commits intomainfrom
feature/blog-release-2-28

Conversation

@dimitrieh
Copy link
Contributor

@dimitrieh dimitrieh commented Mar 12, 2026

Summary

  • Release blog post for FlowFuse 2.28
  • Covers: Expert debug log context, Expert update banner, Device Agent NodeJS options, apiMaxLength UI, ingress migration to Traefik, and self-hosted deployment improvements
  • Adds tier badge and changelog linking system driven by featureCatalog.yaml

Tier badges & changelog links (new)

  • Frontmatter-driven: blog post authors declare features in frontmatter, mapping feature IDs to headings. The build auto-injects tier badges and changelog links at the right positions — no shortcodes needed in the markdown body.
  • featureCatalog as single source of truth: tier availability and changelog URLs are defined in featureCatalog.yaml. Blog posts reference feature IDs, changelog and pricing pages all read from the same data.
  • Changelog entries tagged with release version: changelog entries in featureCatalog now support url + release fields, enabling per-release filtering.
  • Inline tier overrides: for sections not tied to a specific feature (e.g. "More Flexibility for Self-Hosted Deployments"), frontmatter supports inline tiers specification.
  • Two-part badge design: label (Cloud/Self-Hosted) on darker background, value (All tiers/Enterprise/etc) on lighter. Grey variant for "Not available".
  • Applied to: changelog list view, individual changelog pages, and 2.28 blog post.

Files changed

File Change
.eleventy.js releaseFeatures HTML transform, tier/changelog helper functions, filters for changelog views
src/_data/featureCatalog.yaml Added release-tagged changelog URLs to ff-expert, ff-expert-support, edge-devices
src/_includes/components/tier-badges.njk New reusable partial for changelog views
src/_includes/changelog/changelog-posts.njk Tier badges on changelog list items
src/_includes/layouts/post-changelog.njk Tier badges on individual changelog pages
src/blog/2026/03/flowfuse-release-2-28.md Added features frontmatter, renamed "Manage Remote Instances Without SSH" per Nick's feedback
src/css/style.css Two-part badge styles with available/unavailable variants

TODOs

Closes #4668

@netlify
Copy link

netlify bot commented Mar 12, 2026

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit 39e6c3e
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/69b30bd9972c830008c320aa
😎 Deploy Preview https://deploy-preview-4686--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 89 (🟢 up 5 from production)
Accessibility: 81 (no change from production)
Best Practices: 100 (no change from production)
SEO: 91 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

This was referenced Mar 12, 2026
…og views

Connect featureCatalog.yaml to blog posts and changelog entries via a
frontmatter-driven HTML transform. Blog post authors declare which features
map to which headings, and the build system auto-injects tier badges and
changelog links at the right positions.

- Add releaseFeatures transform that parses frontmatter and injects HTML
- Support both feature ID lookups and inline tier specifications
- Add release field to featureCatalog changelog entries for version filtering
- Heading-level scoping: H2 changelogs before next H2, H3 before next H3
- Two-part badge design (label + value) with available/unavailable variants
- Render tier badges on changelog list view and individual changelog pages
- Apply to 2.28 release: ff-expert, ff-expert-support, edge-devices sections
@dimitrieh dimitrieh force-pushed the feature/blog-release-2-28 branch from 1dec53d to 27cd964 Compare March 12, 2026 15:23
@dimitrieh dimitrieh marked this pull request as ready for review March 12, 2026 15:26
@dimitrieh
Copy link
Contributor Author

@Yndira-E @lbeau @knolleary up for review! Added badges and changelog inclusions to header sections through front-matter.

Thanks for fixing the build @Yndira-E

@dimitrieh
Copy link
Contributor Author

Images still need to be added

@dimitrieh dimitrieh self-assigned this Mar 12, 2026
@Yndira-E
Copy link
Contributor

Looks good overall 👍 (although it still needs the images)

One small observation: this reads a bit more feature-focused than the previous release post.
In 2.27 the “In practice” sections helped highlight the outcomes/value (e.g. https://flowfuse.com/blog/2026/02/flowfuse-release-2-27/#in-practice-2). It might be nice to add that here as well.

Also noticed the tier availability labels you added (Cloud / Self-Hosted / tiers). I like the idea, but the spacing/layout feels a bit inconsistent and the design might need some refinement.

For the sake of iterations we could keep it for now, or alternatively keep the scope of this PR focused on the article content and incorporate the labels in a follow-up PR. They don’t necessarily need to land with this release; a link to the pricing page might also work if it’s up to date.

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 59.2%, saving 179.0 KB.

Filename Before After Improvement Visual comparison
src/blog/2026/03/images/flowfuse-release-2-28.png 302.6 KB 123.6 KB 59.2% View diff

@knolleary
Copy link
Member

Images added and url for tile fixed

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 71.6%, saving 166.5 KB.

Filename Before After Improvement Visual comparison
src/blog/2026/03/images/debug-expert.png 146.6 KB 39.6 KB 73.0% View diff
src/blog/2026/03/images/expert-update-banner.png 85.8 KB 26.4 KB 69.3% View diff

1 image did not require optimisation.

Copy link
Member

@knolleary knolleary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the badges could do with some tweaking, and given some more time they could be before this went live. Ideally, that could have been introduced separately without the time pressure to get the release finished. Happy for this to go live.

@knolleary
Copy link
Member

knolleary commented Mar 12, 2026

@dimitrieh all of the changes unrelated to the blog post content are breaking. Can we strip out everything that isn't blog post related and do it separately?

Found some broken links, reading source files
website/_site/handbook/engineering/product/features/index.html
  error: bad link /handbook/engineering/product/[object Object]

Error: bad links:
  handbook/engineering/product/[object Object]

The featureCatalog changelog field changed from a string URL to an
array of {url, release} objects. The features.njk template was still
interpolating it directly, producing [object Object] hrefs. Now
handles both formats.
Adds a light gray border (2px solid #E5E7EB) to the inline images
in the 2.28 release blog post for better visual separation.
h2 has a larger prose margin-bottom (29.6px) than h3 (14.4px),
causing inconsistent gaps before tier badges. Add negative margin-top
on h2 + .ff-tier-badges to match the h3 gap. Normal headings without
badges are unaffected.
Inject ff-tier-badges--h2/h3 classes at the insertion point where
heading level is known, replacing the fragile h2+ sibling selector.
Compensates for prose h2 larger bottom margin to equalize badge gaps.
@dimitrieh dimitrieh merged commit 701f7bb into main Mar 12, 2026
7 checks passed
@dimitrieh dimitrieh deleted the feature/blog-release-2-28 branch March 12, 2026 18:58
@dimitrieh
Copy link
Contributor Author

Agreed with the scope problem. Resolved the problems for now as it was the fastest. Small refinement to badges done as well.

@Yndira-E
Copy link
Contributor

I like the idea of the badges. My only concern is that the darker indigo makes them stand out more than the titles or general content. Maybe it could be a bit more subtle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release BlogPost 2.28

3 participants