Skip to content

docs: Restructure docs to a 8-Section Navigation with Guides #6335

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.

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

Open
wants to merge 25 commits into
base: main
Choose a base branch
from

Conversation

bdougie
Copy link
Collaborator

@bdougie bdougie commented Jun 28, 2025

Description

[ What changed? Feel free to be brief. ]

fixes #6265

Restructured Continue's documentation from 10+ sections (with deep and confusing nesting) to 6 main sections for improved discoverability

https://screen.studio/share/cYqpX02F

Key Changes

  • New 6-section structure: Getting Started, Features, Customization, Hub, Advanced, Guides
  • Fixed 50+ broken links and image references after restructuring
  • Added comprehensive redirects for SEO preservation (netlify.toml)
  • Standardized title casing titles ("Quick start" → "Quick Start")

Docs Structure Changes Only

No content was modified - only file locations, navigation structure, and internal linking. All copy remains unchanged.

How to Review

Navigate through the new 6-section structure and assess:

  • Discoverability: Can you find features without prior knowledge?
  • Logical grouping: Do sections make intuitive sense?
  • Navigation flow: Is the user journey smooth?
  • Please avoid reviewing the content, as it is unchanged, just moved to different pages.
  • All links have been verified to be 301 or 200 via CI

Checklist

  • I've read the contributing guide
  • The relevant docs, if any, have been updated or created
  • The relevant tests, if any, have been updated or created

Screenshots

[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]

Screenshot 2025-07-02 at 10 37 19 AM Screenshot 2025-06-27 at 11 15 27 PM

Tests

[ What tests were added or updated to ensure the changes work as expected? ]


Summary by cubic

Restructured the documentation into 6 main sections for easier navigation and better discoverability, replacing deep nesting and fixing over 50 broken links and images.

  • Migration
    • Added redirects to preserve old URLs and SEO.
    • Standardized title casing across docs.
    • No content changes; only file locations, navigation, and internal links were updated.

@bdougie bdougie requested a review from a team as a code owner June 28, 2025 06:17
@bdougie bdougie requested review from RomneyDa and removed request for a team June 28, 2025 06:17
@dosubot dosubot bot added the size:XL This PR changes 500-999 lines, ignoring generated files. label Jun 28, 2025
Copy link

netlify bot commented Jun 28, 2025

Deploy Preview for continuedev ready!

Name Link
🔨 Latest commit 742c3df
🔍 Latest deploy log https://app.netlify.com/projects/continuedev/deploys/68658678d1ccf80008b583a8
😎 Deploy Preview https://deploy-preview-6335--continuedev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Comment on lines +62 to +64
gtag: {
trackingID: "G-M3JWW8N2XQ",
anonymizeIP: true,
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this got added due to an error I was seeing in dev. Let me my find out if the anonymizeIP is needed.

docs/CLA.md Outdated
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Moved to the root since I did not see it rendered in the production. Not sure if it is in meant to be on the page or just a reference for contributors.

@bdougie bdougie changed the title docs: Documentation Restructure to a 6-Section Navigation with Guides docs: Restructure docs to a 6-Section Navigation with Guides Jun 28, 2025
@bdougie bdougie requested review from a team June 30, 2025 17:34
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think all redirects should use redirects in the docusaurus config, any reason for extra ones here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

moved

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we shouldn't put context providers under "Custom providers", since we have a separate idea of a "custom context provder" in the code for config.ts. These are more like "Built In" context providers

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I am not sure I am following the suggestion, but the thought here is Context Provider are an advanced feature (for now) and we need to focus a story on core features while focus navigate the docs.

If you provide more specifics, I'd be happy to move them to wherever for now, but for context. Our docs are simply not being leveraged by users and Context providers is the 17/20th most visited page at 3k uniques in the last 10days. That is not popular by a far margin.

FWIW - Context in general has a bit of docs tech debt.

i.e. #6360 & #6081

Copy link
Collaborator

Choose a reason for hiding this comment

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

Flagging lorem ipsum stuff

Copy link
Collaborator

Choose a reason for hiding this comment

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

Flagging lorem ipsum

@@ -1,6 +1,6 @@
---
title: Creating an Organization
description: Creating an Organization
title: Creating An Organization
Copy link
Collaborator

Choose a reason for hiding this comment

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

lower case is correct here for "an" in title

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

over zealous model here. I will need to fix a few of these.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think you can do this in the header of the md file

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I tried this, and there are extra things the _category.json gives. It give every section a generated index overviews. These are needed to not have an undefined LLMs.txt

{
  "label": "Guides",
  "position": 6,
  "link": {
    "type": "generated-index",
    "title": "Guides",
    "description": "Learn how to use Continue with comprehensive guides and tutorials"
  }
}

It also Title cases all the files without frontmatter.

With _category.json:

Screenshot 2025-07-01 at 4 57 53 PM

Without

Screenshot 2025-07-01 at 5 47 58 PM

Copy link
Collaborator Author

@bdougie bdougie Jul 2, 2025

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

This is awesome

@github-project-automation github-project-automation bot moved this from Todo to In Progress in Issues and PRs Jun 30, 2025
Comment on lines +7 to +9
# Core Features

Continue provides four powerful AI-assisted development features that work seamlessly within your IDE.
Copy link
Collaborator

Choose a reason for hiding this comment

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

This feels quite similar to /getting-started/overview. Wondering if we should combine. If we did that, we could also then move /getting-started/install out of a dropdown and into a top-level section in the sidebar which might be nice.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This gets into the weeds in updating the actual content. I am going to track this in the "Quick Start" issue instead.


## Session Management

- Use `Cmd/Ctrl + L` (VS Code) or `Cmd/Ctrl + J` (JetBrains) to start a new session
Copy link
Collaborator

Choose a reason for hiding this comment

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

We use <kbd /> elements on other pages, e.g. <kbd>cmd</kbd> + <kbd>shift</kbd> + <kbd>P</kbd> on https://docs.continue.dev/troubleshooting#vs-code

It renders a fancier looking keyboard key. I don't necessarily love them, but if we decide not to use them we should probably replace all instances of <kbd /> with regualr codeblock formatting like we use here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I have a linear issue to follow up on this. This was copied from an existing doc, and it will be easier to audit all of these instances in a single PR, but can update this instance since its a net new.

https://linear.app/continue/issue/CON-2176/keyboard-commands-in-docs-need-consistency-macos-windows

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That's right. It is not the same command/ctrl change to windows for VS Code specifically, which is why I started the linear issue. There is some nuance, which I will need to rethink how this command is shared, probably a TAB, but out of scope for this PR. I will track via Linear.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I lean towards keeping this as a top level sidebar item, but that might be a maintainer specific viewpoint so don't feel strongly

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Valid take. From the data (Posthog), it is not a top 20 clicked page. My guess is either folks don't make it to TroubleShooting, or search is enough. The hope is the LLMs.txt will be the solution eventually thanks to GEO.

Here's the list of the top 20 most visited docs pages on your site:

Homepage - 28,642 visits
Getting Started: Install - 10,069 visits
Customize: Deep Dives Autocomplete - 9,006 visits
Autocomplete: Model Setup - 8,745 visits
Chat: Model Setup - 8,139 visits
Getting Started: Overview - 8,095 visits
Agent: How to Use It - 7,206 visits
Reference - 7,146 visits
Chat: How to Use It - 5,398 visits
Customize: Model Providers - 5,061 visits
Agent: Model Setup - 4,256 visits
Autocomplete: How to Use It - 4,171 visits
Customize: Deep Dives MCP - 3,961 visits
Customize: Model Roles Reranking - 3,405 visits
Customize: Model Roles Chat - 3,289 visits
Customize: Overview - 3,211 visits
Customize: Context Providers - 3,129 visits
Customize: Model Providers Ollama - 2,972 visits
Chat: Context Selection - 2,924 visits
Customize: Deep Dives Codebase - 2,813 visits

Copy link
Collaborator

Choose a reason for hiding this comment

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

I had to add the following to run this locally:

  future: {
    experimental_faster: true,
+    v4: true,
  },

Probably just a local thing for me but curious if you had any issues with the experimental_faster.

Copy link
Collaborator

@Patrick-Erichsen Patrick-Erichsen left a comment

Choose a reason for hiding this comment

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

Huge improvement! Really nice to be back down to a single sidebar.

Only high level comment I have is that I'm wondering if we should just fully remove the Chinese docs at this point. It doesn't seem feasible to keep them up to date with our work.

Also merged main to resolve a conflict from a PR I recently merged

Copy link
Collaborator Author

@bdougie bdougie left a comment

Choose a reason for hiding this comment

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

I will address more of your comments and reviews later tonight @RomneyDa and @Patrick-Erichsen - thanks for taking a look

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

moved

@@ -1,6 +1,6 @@
---
title: Creating an Organization
description: Creating an Organization
title: Creating An Organization
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

over zealous model here. I will need to fix a few of these.


## Session Management

- Use `Cmd/Ctrl + L` (VS Code) or `Cmd/Ctrl + J` (JetBrains) to start a new session
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That's right. It is not the same command/ctrl change to windows for VS Code specifically, which is why I started the linear issue. There is some nuance, which I will need to rethink how this command is shared, probably a TAB, but out of scope for this PR. I will track via Linear.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Valid take. From the data (Posthog), it is not a top 20 clicked page. My guess is either folks don't make it to TroubleShooting, or search is enough. The hope is the LLMs.txt will be the solution eventually thanks to GEO.

Here's the list of the top 20 most visited docs pages on your site:

Homepage - 28,642 visits
Getting Started: Install - 10,069 visits
Customize: Deep Dives Autocomplete - 9,006 visits
Autocomplete: Model Setup - 8,745 visits
Chat: Model Setup - 8,139 visits
Getting Started: Overview - 8,095 visits
Agent: How to Use It - 7,206 visits
Reference - 7,146 visits
Chat: How to Use It - 5,398 visits
Customize: Model Providers - 5,061 visits
Agent: Model Setup - 4,256 visits
Autocomplete: How to Use It - 4,171 visits
Customize: Deep Dives MCP - 3,961 visits
Customize: Model Roles Reranking - 3,405 visits
Customize: Model Roles Chat - 3,289 visits
Customize: Overview - 3,211 visits
Customize: Context Providers - 3,129 visits
Customize: Model Providers Ollama - 2,972 visits
Chat: Context Selection - 2,924 visits
Customize: Deep Dives Codebase - 2,813 visits

@bdougie bdougie requested a review from RomneyDa July 2, 2025 01:26
@bdougie bdougie changed the title docs: Restructure docs to a 6-Section Navigation with Guides docs: Restructure docs to a 8-Section Navigation with Guides Jul 2, 2025
@bdougie
Copy link
Collaborator Author

bdougie commented Jul 2, 2025

updated the side nav to have Troubleshooting and Reference making it 8 items. Based on this interaction in Discord. https://discord.com/channels/1108621136150929458/1389889311457022004/1390021752117006336

Screenshot 2025-07-02 at 10 37 19 AM

@bdougie bdougie force-pushed the bdougie/docs-structure branch from 2259f64 to 083ef5a Compare July 2, 2025 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:XL This PR changes 500-999 lines, ignoring generated files.
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

Docs: Add Features Section to docs
3 participants