Add relevant documentation links in featureCatalog#4713
Add relevant documentation links in featureCatalog#4713sumitshinde-84 wants to merge 8 commits intomainfrom
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
src/_data/featureCatalog.yaml
Outdated
| label: Git Integration | ||
| description: "Back up your flows to a remote Git repository through a DevOps Pipeline." | ||
| docsLink: null | ||
| docsLink: /blog/2026/01/how-to-integrate-node-red-with-git/ |
There was a problem hiding this comment.
@sumitshinde-84 this brings forth the question if we want docsLink to only be for docs/ or also for informative blogposts. Do you think we should feature them differently? I think of the blogposts there could be multiple? 🤔
PS: Aside from that, more of product work related question: Where would you like to see these links featured more? What other cross linking would you like to see across the website? (give me your broad thinking here, not just docslinks.. what inter connectivity might help expose helpful content across the site?)
Currently, these docs links are featured at the pricing page in the details modals:
And on the feature catalogue handbook page
There was a problem hiding this comment.
While some features do not yet have formal documentation—or some topics are better explained in blog posts—they are currently well-covered in the existing blogs. Until the official documentation is created or improved, we should link to the relevant blog posts. I agree that a feature may be covered in multiple blogs, but once the documentation is ready, we will replace the blog links with the official docs. I will create an issue to add documentation for the currently missing features.
Regarding the questions you asked, the docs link can also be referenced in blogs when mentioning a feature. For prerequisites, we can use the feature availability flags included in the release post.
There was a problem hiding this comment.
@dimitrieh, I have created an epic with sub-issues here: #4714
2 participants
Description
This PR adds relevant feature documentation links. Some features, such as Workflow Executions, Performance Monitoring, live chat support, and HIPAA BAA, are missing documentation as it is not yet available.
Related Issue(s)
Checklist