Fixes blog not appearing under Company nav dropdown

[andyvan-ph]

Summary

Reorders the Company dropdown in the top navigation bar so the list now starts:

1. About
2. Blog (/blog)
3. Handbook
4. Customers

Also removes WIP

---

Created with PostHog Code

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Jul 21, 2026 11:02AM

[github-actions]

Bundle report

Total JS (gzip)

6.72 MiB (+0.2 KiB / +0.0%)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint	Eager size	Budget	Modules
✅ app	16.06 MiB (+2.8 KiB / +0.0%)	report-only	1968

Largest modules in the app closure

Module	Size
./src/data/mcp-tools.json	861.3 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css	740.2 KiB
./src/components/Stickers/Stickers.tsx	696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js	481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules	395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js	364.8 KiB
./src/hooks/useCustomers.tsx + 54 modules	355.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js	354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules	351.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js	281.9 KiB
./src/components/ProductComparisonTable/index.tsx + 120 modules	278.6 KiB
./src/components/SearchUI/index.tsx + 87 modules	271.9 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules	247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules	239.9 KiB
./gatsby-browser.tsx + 44 modules	227.0 KiB

---

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

[charlescook-ph]

Not a 'fix' per se as the Blog is already under Community? (Always has been as far as I can see)

[andyvan-ph]

It was (and should) be under both. Very common for "blog" to fall under "Company" on most business websites, so it's just a simpler to have it in both so people can find it where they might expect it to be.

[joethreepwood]

I don't think we should add it to Company unless we're willing to also remove it from Community.

I'd discussed this previously with Cory and his challenge then was always that Company > Blog ends up feeling a bit businessy and makes it feel like this is a corporate blog -- which is what most other company blogs are and why you may expect their blogs to be Company > Blog. The idea was that putting it under Community fit more with the vision we have.

This also extended to the Merch store too. It could go in both, but we want our merch to feel cool, so we put it in Community, because who wants to wear Company merch?

I can take or leave that argument, but I don't think Blog should be appearing in both Company and Community.

[joethreepwood]

Why do you want to remove this? I think it's worth keeping and there isn't an argument for it in the PR.

[charlescook-ph]

I explained it in another PR but Andy edited this one - that information is already surfaced under small teams, it's confusing what WIP vs. Roadmap means, and the list of items here is getting long

[joethreepwood]

I think we should leave this for now.

My incoming Roadmap PR is going to shake up how the Roadmap works, and I personally really like the WIP page because it's the only place you can see what the company is actually focused on this quarter. The only alternative is having to go one-by-one through every individual team, or using the Slack bot to query this.

If there's a strong feeling against it then I'd be happy to remove it in a subsequent PR that combines it into the imminent /roadmap page - I agree a single Roadmap page with this info would be ideal - but right now we created the /wip to solve a problem, and getting rid of it just re-introduces that problem.

[andyvan-ph]

@charlescook-ph's suggestion. I don't care either way.

[andyvan-ph]

@joethreepwood you're massively overthinking this. this just makes it easier for people to find it if they expect that to be there. i don't think it communicates anything other than "we have a blog". the content can speak for itself.

[joethreepwood]

I'm not overthinking, I'm just reiterating why we have not done this in the past when it's been proposed. As I said: I can take or leave it being in /company -- but I think having it in both is needless and just bloats the nav. It should be one or the other, like the Merch Store.

[andyvan-ph]

closing as don't feel strongly

[joethreepwood]

PR on the /WIP point : #18817