Add Blog CTA Template

[sumitshinde-84]

Description

This PR introduces reusable CTA templates for blog posts, including Sign Up, Book Demo, Contact, and View Pricing. Each template comes with a default CTA title, button text, and description, which can be customized by passing variables through the front matter. The templates also emit events that can be tracked via PostHog.

By default, the Sign Up CTA is automatically added to all blog posts using the article post template.
Additionally, this PR adds documentation in the handbook, providing instructions on how to use CTAs in blog posts along with related guidance.

Related Issue(s)

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)

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	2acb31c
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/69b991f8597d320008e14f09
😎 Deploy Preview	https://deploy-preview-4708--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 92 (🟢 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.

[Yndira-E]

Hi @sumitshinde-84, thanks for putting this together.

A few notes:

• There should be more than one partial: sign-up, contact-us, book-a-demo (I’d use this one the least, since cookies need to be accepted to load the calendar), and something like “check our plans” for the pricing page. All of them should include fallback text, and the button text and URL should remain fixed (i.e. not configurable).
• The partials should be included in the template, and variables should be handled in the front matter rather than inline. Check out how it's handled in this template and then in the front matter of contact us, book a demo and support
• The default for all articles should be the sign-up one
• The CTA section needs a title, like in this example, but with the highlighted button style (red instead of indigo). You can see the code in this PR.

Right now, it looks like this:

[Yndira-E]

Hey Sumit, looks good. I’ll check locally to see how the other partials behave.

One detail — I’m seeing too much white space. You probably picked up a min-height or something similar from the code I shared. Please review it; I’m sure it can be tightened up.

[Yndira-E]

@PabloFilomeno83 please review and feel free to merge if everything looks good.

@sumitshinde-84 once this is merged, please open two separate PRs:

1. Add custom CTAs at least to this month’s articles and the ones that have performed best on social media this year
2. Remove the old CTAs you previously added, along with the partial you created (this file https://github.com/FlowFuse/website/blob/main/src/_includes/cta.njk and all its implementations across articles)