Skip to content

FlowFuse 2.31 blog: featureCatalog + changelog interlinking (stacked on #5114)#5137

Draft
dimitrieh wants to merge 25 commits into
mainfrom
blog-2-31-interlinking
Draft

FlowFuse 2.31 blog: featureCatalog + changelog interlinking (stacked on #5114)#5137
dimitrieh wants to merge 25 commits into
mainfrom
blog-2-31-interlinking

Conversation

@dimitrieh
Copy link
Copy Markdown
Contributor

@dimitrieh dimitrieh commented Jun 4, 2026

Summary

Stacked follow-up to #5114 (the FlowFuse 2.31 release blog post). It holds the featureCatalog + changelog interlinking, which can only be correct once the 2.31 changelog entries exist (they land with the release). Keep as draft; merge after #5114 and the changelog entries are in.

This PR wires the blog's features: block to featureCatalog ids:

  • ff-expert-application-building → "Agentic Development Now in Open Beta"
  • certified-nodes → "Certified nodes for industrial connectivity and AI"
  • "What else is new?" tiers row

The features: block alone does NOT link up

Verified against the releaseFeatures transform in .eleventy.js: badges come from each feature's cloud/selfHosted tiers in featureCatalog.yaml; changelog links come from that feature's changelog entries filtered to release: "2.31". So this PR must also edit featureCatalog.yaml, otherwise the blog shows no changelog links and stale/wrong badges.

ff-expert-application-building

  • Add a release: "2.31" changelog entry (URL must match the authored agentic open-beta changelog page). Without it, no changelog link renders (the existing 2.30 entry is filtered out for 2.31).
  • Set selfHosted.enterprise.value: true so the Self-Hosted Enterprise badge shows (currently all null → no SH badge). Cloud already resolves to "All tiers".

certified-nodes

  • Add a release: "2.31" changelog entry (URL must match the authored certified-nodes changelog page; currently changelog: null).
  • Badge decision: the catalog has selfHosted.enterprise: true, so the blog would render a Self-Hosted Enterprise badge, but certified nodes is Cloud-only for 2.31 (SH deferred). Pick one: (a) accept it, (b) set SH null until SH support lands, or (c) use an inline cloud-only tiers: entry in the blog instead of the id (loses the changelog link).

Changelog entries + docs that must exist for the links to resolve

Related in-flight PRs (2.31)

@sumitshinde-84 does this cover everything on the changelog and docs side for 2.31, and any preference on the certified-nodes Self-Hosted badge question above?

dimitrieh and others added 24 commits June 3, 2026 18:25
Co-authored-by: Jamie Strusz <5758031+allthedoll@users.noreply.github.com>
…d cta block, link LLM docs, drop Try FlowFuse; defer featureCatalog wiring
@sumitshinde-84
Copy link
Copy Markdown
Contributor

does this cover everything on the changelog and docs side for 2.31, or is anything missing?
I think yes !

@dimitrieh
Copy link
Copy Markdown
Contributor Author

Dark mode won't merge yet this release

@Yndira-E Yndira-E force-pushed the blog-release-2-31 branch from c1bb575 to a7a4c50 Compare June 4, 2026 14:09
Base automatically changed from blog-release-2-31 to main June 4, 2026 15:57
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.

2 participants