Skip to content

Clearer main nav and a footer with its own job - #6029

Merged
JoycePlaysFootball merged 37 commits into
mainfrom
nav-header-footer-rework
Nov 16, 2026
Merged

JoycePlaysFootball merged 37 commits into
mainfrom
nav-header-footer-rework

Conversation

@sumitshinde-84

Copy link
Copy Markdown
Contributor

The header and footer were built from one shared list, so the footer repeated 98% of the header's pages, and the header itself listed Pricing, Industrial AI and Security twice and split use cases across two menus. This PR gives each its own job. Solutions now comes before Platform in the header, since our new GTM leads with the problems FlowFuse solves rather than the product, and a buyer's first question is whether we solve theirs. The header also shows each page once (53 links down to 48), groups every use case under Solutions, describes Edge, Hub and Fleet by who they're for, and can be used from the keyboard, which it couldn't before. The footer is its own shorter list (51 links down to 35), organised by Solutions, Product, Evaluate, Resources, Company and Trust & Support, with the new tagline. Merge with or after #6021, which introduces the Foundation Partnership name and tagline used here.

Header: each page appears once. Pricing, Industrial AI and the security,
support and status duplicates are out of the dropdowns. Use-case pages
move from Platform > Capabilities into Solutions > By Use Case, so
Platform is products and components and Solutions is team, industry and
use case. Adds Aviation & Aerospace, Free templates and Build with us,
clearer labels, and one-line descriptions under Edge, Hub and Fleet.

Footer: its own list instead of a copy of the mega nav. Adds comparison
pages, Node-RED and protocol pages, free templates, and a trust and
support column; newsletter link and Talk to Us in a top strip.

Tests: the header lists each page once, and the footer stays below
two-thirds overlap with the header.
Five columns (Product, Evaluate, Resources, Company, Trust & support) and
a brand block, 29 links. Drops the Node-RED topic, individual template,
industry and Tulip links and the top strip; the header is sticky, so a
footer Talk to Us repeated it. The overlap test now checks the footer does
not carry most of the header.
Matches the offer's name on the redesigned homepage and /build-with-us/
page. In the footer it moves from Company to Evaluate, since it is now how
a buyer starts with FlowFuse. The Solutions highlight card promotes it
with the homepage's own line.
The site now leads with outcomes and the Foundation Partnership rather
than the product, so the first menu answers the buyer's first question:
do you solve my problem, for my industry and team.
Matches the redesigned homepage's H1. Used under the footer logo and in
the llms.txt description.
- Utility bar carries existing-user tasks only (Docs, Support, Install on
  edge, Sign In); About and Blog are already in the main menus.
- Highlight cards no longer repeat links: Platform points to the platform
  overview, Company promotes Partners.
- Column headings describe their contents: Products, Features (now with
  Security & Compliance), and Evaluate (now with Why FlowFuse).
- Every header link has its own icon, and a test keeps it that way.
- Industrial AI sits beside Platform; header.order sets the top-level
  order, and a test checks it lists every item once.
- One Title Case style across header and footer labels.
- See All links are indigo instead of grey; Integrations, a regular item
  now, is no longer caught by the old See-all grey rule.
Keyboard users could not reach Solutions, Platform, Resources or Company:
the triggers were plain spans and the panels used visibility: hidden, so
Tab skipped about 45 links (WCAG 2.1.1). Triggers are now focusable with
button semantics and aria-expanded, following the W3C disclosure pattern:
Tab moves between top-level items, Enter/Space opens a panel, Escape
closes it and returns focus. Mouse hover and click are unchanged.

The top-level item a page belongs to now keeps the brand colour and its
underline, resolved by the longest matching nav href.
The footer had no solutions links on a solutions-led site. Solutions now
leads the footer, matching the header order, and lists the six core use
cases plus All Use Cases: one kind of item, the problems FlowFuse solves.
Foundation Partnership moves to the top of Evaluate.

The brand block gets its own row so six columns fit without wrapping,
and the old rule that greyed footer links to /use-cases/, /industries/
and /integrations/ is removed. The overlap guard allows up to two thirds,
since the footer now deliberately shares the use-case pages.
…ustries

Labels match the header's Solutions > By Team. There is no teams index
page, so the column ends with the two real index pages rather than an
All Teams link to a page that does not exist.
@netlify

netlify Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for flowfuse-website ready!

Name Link
🔨 Latest commit fef5ea9
🔍 Latest deploy log https://app.netlify.com/projects/flowfuse-website/deploys/6afb3b9872421e6cfd3312df
😎 Deploy Preview https://deploy-preview-6029--flowfuse-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: 80 (🟢 up 26 from production)
Accessibility: 98 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (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.

sumitshinde-84 and others added 16 commits November 14, 2026 00:03
With it now in the Evaluate column, the copy under Company > Work with us made the header tests flag a duplicate link and icon.
The newsletter was only a link under Resources. The footer now carries the
signup itself: the blog's HubSpot form (same list, same cta-blog-subscribe
event, tagged footer), restyled into one email row with the form's consent
text as small print and the reCAPTCHA notice in place of its badge. It has to
be the embed, not an API post: the form has captcha on, and HubSpot refuses
API submissions for those.

HubSpotForm takes an optional stylesheet and reports when the form is ready,
and gives each instance its own container id so the blog page can render the
blog form and the footer form together.
The brand row now goes side by side from md instead of lg, and the form has a
fixed width instead of filling the row. HubSpot's consent block is hidden and
replaced by one short privacy and reCAPTCHA line under the form.
Updated FAQ answers and page content to clarify the Foundation Partnership and solution deployment process.
Removed unused CSS prop and form ready callback. Simplified container ID generation and added viewport detection for script loading.
Pauses a drawing while it’s off screen for efficiency.
Added IntersectionObserver to manage visibility state.
Marked the Results, Customers, Security and FAQ sections so the browser skips rendering them until they’re near the screen.
KristopherLeads and others added 9 commits November 17, 2026 01:53
Updated SEO metadata and text content for clarity and impact.
Three requests were competing with what the homepage needs to paint, and
Lighthouse counts every request started before first paint against FCP/LCP:

- Google Fonts CSS now loads without blocking render (media="print" +
  onload, with a <noscript> fallback). It is only @font-face rules with
  font-display: swap, and keeps its position, so the final look is unchanged.
- KaTeX CSS is no longer global. useKatexStyles() adds it on the pages that
  render markdown, so math pages still get it in their prerendered <head>.
- Nuxt's <link rel="prefetch"> for every lazy chunk (~290 KB on the homepage)
  is turned off. Chunks still load on demand.

Local production build, mobile Lighthouse: performance 63 -> 68, LCP 7.3s -> 5.3s.
The HubSpotForm refactor dropped the css prop, the ready event and the
per-instance container id. Without css HubSpot falls back to its default
iframe embed, so the footer showed the full consent block and the reCAPTCHA
badge again, and without the unique id the footer form and the blog's form
render into the same container on blog posts. Brings those back and keeps
the near-viewport lazy loading from the refactor.
@JoycePlaysFootball
JoycePlaysFootball merged commit 8ecaba7 into main Nov 16, 2026
8 checks passed
@JoycePlaysFootball
JoycePlaysFootball deleted the nav-header-footer-rework branch November 16, 2026 18:18
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