Docs navigation upgrades

[abhijna]

Preview: https://deploy-preview-2353--semgrep-docs-prod.netlify.app/docs/writing-rules/overview

Changes:

• Nav at the top of the docs with the same sections as side nav for better visibility
• Combined KBs and Support page under "Help" tab
• The Explore tab contains About Semgrep and other sections

https://linear.app/semgrep/issue/TEC-436/docs-navigation-changes

TO DO:

• Fix pre-commit

[netlify]

✅ Don't forget to add /docs at the end of the deploy preview site URL!

Name	Link
🔨 Latest commit	eef3ad7
🔍 Latest deploy log	https://app.netlify.com/projects/semgrep-docs-prod/deploys/6924d1bc9d4c5c0008e7489e
😎 Deploy Preview	https://deploy-preview-2353--semgrep-docs-prod.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[khorne3]

I don't think we should add a nav bar, because then we'd have three nav bars stacked on top of each other. Maybe something like this:

[khorne3]

Nav bar:

• "What's semgrep" --> "What's Semgrep?" or even "What is Semgrep" or maybe "Semgrep 101" (not particular tied to any option)

WDYT about the following for the top-level nav bar based on the heatmap below of what's most often used -- maybe we should have these easily accessible?:

• Scan with Semgrep (I think putting just Scan isn't super clear)
• Write Semgrep rules
• API
• Help
• Explore

[abhijna]

@khorne3, thanks for sharing the heatmap. I changed the label to “Scan with Semgrep.” “Write Rules” should be clear from context, and the shorter text reduces clutter. Based on your suggestion, I also moved For Developers out of the top-level nav, but kept Learning Guides there since it’s a newer section.

[khorne3]

It looks like the font for Help and Explore don't match the others (also, maybe API should be to the left of these two for visual consistency?)

[khorne3]

Do we need to go back and update the metadata for every doc?

[abhijna]

TLDR: No, we shouldn't update the metadata for each doc.

---

Any page can include displayed_sidebar, but you don’t need it on most pages.

Docusaurus picks the sidebar based on:

• The page’s folder path.
• How the page is referenced in sidebars.js.

When to set displayed_sidebar:

• Override the default sidebar selection.
• Choose a sidebar when a page appears in multiple sidebars.
• Resolve ambiguity about which sidebar should render.