-
Notifications
You must be signed in to change notification settings - Fork 3
Document folder-based navigation configuration #1765
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
Conversation
Add comprehensive documentation for the new folder configuration feature that allows automatic navigation generation from a folder of markdown files. The documentation covers: - Basic usage and how it works - Filename to title/slug conversion rules - Nested folder support - All configuration options (title, slug, icon, collapsed, hidden, etc.) - Combining folder and manual navigation - Controlling page order with frontmatter - Use cases and real-world examples Includes example from Slack's documentation showing the feature in action. Co-Authored-By: Deep Singhvi <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
fern/products/docs/pages/navigation/folder-based-navigation.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| **Large documentation sets**: When you have dozens or hundreds of pages, manually maintaining the navigation structure in `docs.yml` becomes tedious. Folder-based navigation lets you organize pages in the filesystem and have the navigation generated automatically. | ||
|
|
||
| **Frequently updated content**: If you regularly add new pages to a section, folder-based navigation eliminates the need to update `docs.yml` every time you add a page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[FernStyles.Adverbs] Remove 'regularly' if it's not important to the meaning of the statement.
|
|
||
| **Team collaboration**: When multiple team members are adding documentation, folder-based navigation reduces merge conflicts in the `docs.yml` file since new pages don't require configuration changes. | ||
|
|
||
| ## Example from Slack |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[FernStyles.Headings] 'Example from Slack' should use sentence-style capitalization.
- Remove standalone folder-based-navigation.mdx page - Add concise 'Add pages from a folder' section to navigation overview - Create reusable snippet at /fern/snippets/folder-nav-basic.mdx - Add redirect from old URL to navigation overview - Add changelog entry for 2025-11-05 - Keep documentation dry and concise as requested Co-Authored-By: Deep Singhvi <[email protected]>
Refactor folder-based navigation documentation to be concise and integrated
Summary
Per user feedback, the standalone folder-based navigation page was too verbose. This PR refactors the documentation to be dry and concise by:
folder-based-navigation.mdx, 259 lines) and integrating it as a short subsection in the navigation overview page (~7 lines)/fern/snippets/folder-nav-basic.mdxfor the basic example to avoid duplication/learn/docs/configuration/folder-based-navigation) to the navigation overview pageThe new documentation is minimal: introduces the
folderconfiguration with one example, mentions that subfolders become nested sections, and lists the supported options (title,slug,icon,collapsed,hidden,skip-slug,availability).Review & Testing Checklist for Human
/learn/docs/configuration/navigationcorrectly<Markdown src="/snippets/folder-nav-basic.mdx" />reference works in both the navigation overview page and the changelog entry#add-pages-from-a-folder) on the navigation overview pagefern docs devand navigate to the navigation overview page to ensure it renders correctly with proper formatting and the snippet resolvesNotes
what-is-docs-yml.mdxto avoid unnecessary duplication