-
Notifications
You must be signed in to change notification settings - Fork 4
docs: document custom icon functionality for docs.yml and navigation #1703
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 documentation for custom icons using file: prefix for local files - Document inline SVG icon support using < > wrapper - Update navbar-links section with icon format examples - Update sidebar icons section with comprehensive examples for all three formats - Update products section with detailed icon format documentation - Add examples showing Font Awesome, custom image files, and inline SVG usage Co-Authored-By: Catherine Deskur <[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:
|
| ``` | ||
| </CodeBlock> | ||
|
|
||
| #### Inline SVG icons |
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] 'Inline SVG icons' should use sentence-style capitalization.
| - **Custom image files**: Use `file:` prefix followed by the file ID (e.g., `file:my-icon`). The file must be uploaded to your docs assets. | ||
| - **Inline SVG**: Provide an SVG string wrapped in `< >` (e.g., `<svg>...</svg>`). | ||
|
|
||
| ### Font Awesome icons |
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] 'Font Awesome icons' should use sentence-style capitalization.
| ``` | ||
| {/* <!-- vale on --> */} | ||
|
|
||
| ### Inline SVG icons |
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] 'Inline SVG icons' should use sentence-style capitalization.
- Change from file: prefix to relative paths (./assets/icons/...) - Update navbar-links icon examples to use ./assets/icons/ - Update sidebar icons examples to use relative paths - Update product icons examples to use relative paths - Add note that paths are relative to the YAML file where declared - Wrap inline SVG examples in quotes for proper YAML parsing Co-Authored-By: Catherine Deskur <[email protected]>
Document custom icon functionality for docs.yml and navigation
Summary
This PR documents the new custom icon functionality that allows users to specify icons using three formats across docs.yml and navigation configurations:
fa-solid fa-rocket./assets/icons/icon.svg"<svg>...</svg>"Updated three documentation files:
what-is-docs-yml.mdx- navbar linksiconandrightIconparametersnavigation/overview.mdx- sidebar icons (sections, pages) and tabsnavigation/products.mdx- product iconsEach section includes comprehensive examples showing all three icon formats with syntax details.
Note: Initial commit incorrectly used
file:prefix syntax. Second commit corrected to relative paths (e.g.,./assets/icons/) based on Catherine's feedback and existing docs.yml examples.Review & Testing Checklist for Human
Test custom image icon examples end-to-end - Create a test docs site with custom icon files and verify the documented relative path syntax works correctly (e.g.,
icon: ./assets/icons/my-icon.svg). This is critical since all examples are synthetic and untested.Verify path resolution for nested YAML files - Test that icons declared in
products/*.ymlorversions/*/*.ymlfiles resolve paths correctly relative to those files (as documented: "Paths are relative to the YAML file where the icon is declared"). The implementation details weren't fully verified.Consider adding file upload workflow documentation - The docs explain icon SYNTAX but not WHERE/HOW users place icon files or what "docs assets folder" means. This could confuse users about the complete workflow.
Decide on Vale style warnings - Vale flagged heading capitalization: "Font Awesome icons" and "Inline SVG icons" should use sentence case. CI passed (warnings only), but you may want to fix for consistency with style guide.
Notes
88c8c2850(branchorigin/cd/custom-icons)