FlowFuse 2.31 blog: featureCatalog + changelog interlinking (stacked on #5114)#5137
Draft
dimitrieh wants to merge 25 commits into
Draft
FlowFuse 2.31 blog: featureCatalog + changelog interlinking (stacked on #5114)#5137dimitrieh wants to merge 25 commits into
dimitrieh wants to merge 25 commits into
Conversation
…Remote Instances expansion
…off-site to one photo slot, styled hr
Co-authored-by: Jamie Strusz <5758031+allthedoll@users.noreply.github.com>
…d cta block, link LLM docs, drop Try FlowFuse; defer featureCatalog wiring
1 task
Contributor
|
…pen-beta tiers + 2.31 changelog refs)
Contributor
Author
|
Dark mode won't merge yet this release |
c1bb575 to
a7a4c50
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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"The
features:block alone does NOT link upVerified against the
releaseFeaturestransform in.eleventy.js: badges come from each feature'scloud/selfHostedtiers infeatureCatalog.yaml; changelog links come from that feature's changelog entries filtered torelease: "2.31". So this PR must also editfeatureCatalog.yaml, otherwise the blog shows no changelog links and stale/wrong badges.ff-expert-application-buildingrelease: "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).selfHosted.enterprise.value: trueso the Self-Hosted Enterprise badge shows (currently allnull→ no SH badge). Cloud already resolves to "All tiers".certified-nodesrelease: "2.31"changelog entry (URL must match the authored certified-nodes changelog page; currentlychangelog: null).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 SHnulluntil SH support lands, or (c) use an inline cloud-onlytiers:entry in the blog instead of the id (loses the changelog link).Changelog entries + docs that must exist for the links to resolve
/node-red/flowfuse/ai/llm-nodes/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?