Apply site-wide animated-link and button interaction polish

[dimitrieh]

Description

Outcome: a cohesive, finished interaction feel across the site. Applies the animated-underline link treatment and the outlined/tertiary button conventions to the remaining templates (comparison pages, FAQ, post/story/ABM layouts, why-flowfuse, PLC landing).

Also fixes an invalid align-center class to items-center in the post and story back-links, and adds a social image to the customer stories index.

Builds on: the whole stack, this is the finishing layer applied last.

Related Issue(s)

Split from #5371.

Checklist

• I have read the contribution guidelines
• I have considered the performance impact of these changes

---

Stack (left to right is merge order; #5373 punctuation is independent, off main):

flowchart LR
    main([main])
    main --> P73["#5373 punctuation"]
    main --> P74["#5374 shop-floor"] --> P75["#5375 nav"] --> P76["#5376 use-cases"] --> P77["#5377 hero-media"] --> P78["#5378 industry"] --> P79["#5379 AI"] --> P80["#5380 homepage"] --> P81["#5381 polish"]
    classDef here stroke-width:4px;
    class P81 here;

Loading

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	cb1e82e
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/6a634a0262396b00088f9a65
😎 Deploy Preview	https://deploy-preview-5381--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 74 (🟢 up 6 from production) Accessibility: 96 (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]

I still have the same concern I raised in the previous PRs about the animated underline treatment.

My impression is that it’s being applied quite selectively rather than consistently, so it doesn’t yet feel like a cohesive interaction pattern. Some links use it, others don’t, and in places like the FAQ it adds motion to interactions that I don’t think benefit from it.

I’d still recommend keeping this effect reserved for the main navigation. Used more sparingly it feels like a deliberate interaction pattern, whereas applying it across many different templates starts to dilute its impact and adds more motion throughout the site than I think is necessary.