Skip to content

Add use-case and outcome lens pages and cross-link includes#5376

Open
dimitrieh wants to merge 3 commits into
split/navfrom
split/usecase
Open

Add use-case and outcome lens pages and cross-link includes#5376
dimitrieh wants to merge 3 commits into
split/navfrom
split/usecase

Conversation

@dimitrieh

@dimitrieh dimitrieh commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Description

Outcome: visitors can navigate the platform by use case and by outcome. Adds use-case chips and links, a derived use-case grid for industry pages, the use-case layout, refreshed use-case pages, and systematic cross-links between related content. The industry-use-cases heading falls back to the page eyebrow so industry pages read cleanly rather than showing the raw SEO title.

Builds on: the navigation PR's shared stylesheet and components.

Provides for later PRs: the reusable includes (use-case-links, use-case-chips, industry-use-cases) that the industry pages and the AI page consume downstream.

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 P76 here;
Loading

@netlify

netlify Bot commented Jul 24, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit 8f047a3
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a634985056b1800086d86da
😎 Deploy Preview https://deploy-preview-5376--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: 65 (🔴 down 3 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.

See all
{% include "components/icons/arrow-long-right.svg" %}
<a href="/blog/{{ collectionName or '' }}" class="group hover:no-underline w-full text-right flex flex-row items-center justify-end self-end justify-self-end gap-1">
<span class="ff-animated-link">See all</span>

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.

Introducing it here creates an inconsistency with the rest of links across the website. I would reserve this for the main nav exclusively.

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.

I can see you've been adding that class to other elements as well, lets reserve this class for the main nav only.

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.

For instance, here, the hover effect on the card is enough, no need for that effect there
Screenshot 2026-07-24 at 17 20 09

@Yndira-E

Copy link
Copy Markdown
Contributor

What do you think about adding a CTA that links to /ai, so they can get started with the expert?

Screenshot 2026-07-24 at 17 09 52

@Yndira-E

Copy link
Copy Markdown
Contributor

This button shouldn't be full width at that screen size
Screenshot 2026-07-24 at 17 18 45

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.

2 participants