Skip to content

Fixes blog not appearing under Company nav dropdown #18714

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
andyvan-ph wants to merge 6 commits into from
+6 −6
Closed

Fixes blog not appearing under Company nav dropdown #18714

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
329a519
feat(nav): reorder Company dropdown to About, Blog, Handbook, Customers
andyvan-ph Jul 21, 2026
d8a5618
Merge branch 'master' into posthog-code/company-menu-reorder
andyvan-ph Jul 21, 2026
57fc0fa
Apply suggestions from code review
andyvan-ph Jul 21, 2026
f5aa290
Merge branch 'master' into posthog-code/company-menu-reorder
andyvan-ph Jul 21, 2026
4516725
Update menuData.tsx
andyvan-ph Jul 21, 2026
abe2b8a
Merge branch 'master' into posthog-code/company-menu-reorder
andyvan-ph Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions src/components/TaskBarMenu/menuData.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -393,8 +393,8 @@ export function useMenuData(): MenuType[] {
},
{
type: 'item',
label: 'Customers',
link: '/customers',
label: 'Blog',
link: '/blog',
},
{
type: 'item',
Expand All @@ -403,13 +403,13 @@ export function useMenuData(): MenuType[] {
},
{
type: 'item',
label: 'Roadmap',
link: '/roadmap',
label: 'Customers',
link: '/customers',
},
{
type: 'item',
label: 'WIP',
link: '/wip',
label: 'Roadmap',
link: '/roadmap',
Comment on lines -411 to +412

@joethreepwood joethreepwood Jul 21, 2026

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.

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 charlescook-ph Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 joethreepwood Jul 21, 2026 •
edited
Loading

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 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 andyvan-ph Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

},
{
type: 'item',
Expand Down
Loading