Skip to content

Add release blogs page#4836

Open
allthedoll wants to merge 8 commits intomainfrom
allthedoll/release-blogs
Open

Add release blogs page#4836
allthedoll wants to merge 8 commits intomainfrom
allthedoll/release-blogs

Conversation

@allthedoll
Copy link
Copy Markdown
Contributor

@allthedoll allthedoll commented Apr 8, 2026

Description

This PR adds a release blogs page that mirror's @sumitshinde-84's changelog page to help us all make better release blogs!

Related Issue(s)

N/A

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

@allthedoll allthedoll self-assigned this Apr 8, 2026
@allthedoll allthedoll requested a review from ZJvandeWeg as a code owner April 8, 2026 16:58
@netlify
Copy link
Copy Markdown

netlify bot commented Apr 8, 2026

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit 7159206
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/69dd0a60a265560008f1230a
😎 Deploy Preview https://deploy-preview-4836--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: 87 (🔴 down 2 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.

Comment thread src/handbook/engineering/releases/release-blogs.md Outdated
Comment thread src/handbook/engineering/releases/release-blogs.md Outdated
@sumitshinde-84
Copy link
Copy Markdown
Contributor

@allthedoll I have added two suggestions. This is a really well-written guide on writing release posts, thank you for it. One thing that needs to be addressed is that the guide should include a section or note to ensure the featureCatalog.yml file is updated.

allthedoll and others added 2 commits April 13, 2026 13:30
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Comment thread src/handbook/engineering/releases/release-blogs.md Outdated
allthedoll and others added 2 commits April 13, 2026 13:47
Added a note about confirming feature catalog updates before populating features in release blogs.
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
@allthedoll
Copy link
Copy Markdown
Contributor Author

@sumitshinde-84 I added a section under the features table in line 43 about checking to ensure things have been added to the feature catalog. I think I did the link wrong. 🙃 Can you review it for the content to address your point about that and also help me with the link?

Comment thread src/handbook/engineering/releases/release-blogs.md Outdated
@sumitshinde-84 sumitshinde-84 self-requested a review April 13, 2026 15:22
allthedoll and others added 2 commits April 13, 2026 16:22
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
@allthedoll
Copy link
Copy Markdown
Contributor Author

@ZJvandeWeg can you 👀 this? @sumitshinde-84 and I are happy with it and ready to 🚀

> Managing flows across environments means tracking what changed, when, and by whom. When tooling gaps introduce friction here — or leave your version control workflow fragmented — they slow teams down at exactly the wrong moment.

**2. Feature content**
Use H3 headings when multiple features are grouped under one H2. Each feature gets 1–2 factual paragraphs. No preamble. No "we're excited to announce."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@allthedoll for the H3 it would be expected to include the feature name, I think it would be worth mentioning it here.


Give an AI tool your feature list — not a written draft. If you hand it a draft, it will polish rather than restructure. A bullet list of what shipped forces the grouping and framing work to happen from scratch.

Paste the following prompt along with your feature list:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@allthedoll we now have the skill you created, is this full prompt still necessary?

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.

3 participants