docs: prioritize Data Engineering in nav, fix faint section headers#29
Merged
anandgupta42 merged 1 commit intomainfrom Mar 3, 2026
Merged
docs: prioritize Data Engineering in nav, fix faint section headers#29anandgupta42 merged 1 commit intomainfrom
anandgupta42 merged 1 commit intomainfrom
Conversation
As a data engineering tool, the Data Engineering section (agent modes, tools, guides) should be the first thing users see after Getting Started — not buried below Configure. New nav order: Getting Started → Data Engineering → Usage → Configure → Develop → Reference. This matches the user journey: install, use the data tools, learn the interfaces, then customize. Also adds custom CSS to make nav section headers (DATA ENGINEERING, USAGE, CONFIGURE, etc.) bold uppercase with full contrast instead of the default faint light-gray styling from the white primary theme. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
anandgupta42
added a commit
that referenced
this pull request
Mar 17, 2026
…29) As a data engineering tool, the Data Engineering section (agent modes, tools, guides) should be the first thing users see after Getting Started — not buried below Configure. New nav order: Getting Started → Data Engineering → Usage → Configure → Develop → Reference. This matches the user journey: install, use the data tools, learn the interfaces, then customize. Also adds custom CSS to make nav section headers (DATA ENGINEERING, USAGE, CONFIGURE, etc.) bold uppercase with full contrast instead of the default faint light-gray styling from the white primary theme. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two changes to improve the docs sidebar from a data engineer's perspective:
1. Reorder nav to prioritize Data Engineering
Before: Getting Started → Usage → Configure → Data Engineering → ...
After: Getting Started → Data Engineering → Usage → Configure → ...
As a data engineering tool, agent modes, SQL/dbt/FinOps tools, and guides should be the first thing users see — not buried below 20+ configuration items. The new order matches the user journey:
2. Fix faint section headers
Section headers (DATA ENGINEERING, USAGE, CONFIGURE, etc.) were nearly invisible with the
primary: whitetheme. Added custom CSS (assets/css/extra.css) to make them:Test plan
mkdocs build— zero errors🤖 Generated with Claude Code