revamp: update fonts and improved home page navigation#238
revamp: update fonts and improved home page navigation#238
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis pull request updates the documentation infrastructure, redesigns the homepage with a card-based layout, introduces a new tab navigation component integrated into the VitePress theme, adds a VSCode launch configuration, and overhauls the stylesheet with typography and layout changes from Satoshi to Inter fonts. Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~50 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/.vitepress/theme/style.css (1)
96-146:⚠️ Potential issue | 🔴 CriticalResolve unresolved merge conflict markers.
The file contains unresolved Git merge conflict markers (
<<<<<<< Updated upstream,=======,>>>>>>> Stashed changes) that break CSS parsing. This is causing the Prettier CI check to fail.The conflict appears to be between the old Satoshi font and the new Inter font. Based on the PR objectives, the Inter font should be kept.
🔧 Proposed fix - Remove conflict markers and keep Inter font
/* ================================================ -<<<<<<< Updated upstream - SATOSHI FONT - ================================================ */ - -@font-face { - font-family: "Satoshi"; - src: - url("/fonts/Satoshi/Satoshi-Light.woff2") format("woff2"), - url("/fonts/Satoshi/Satoshi-Light.woff") format("woff"); - font-weight: 300; - font-style: normal; - font-display: swap; -} - -@font-face { - font-family: "Satoshi"; - src: - url("/fonts/Satoshi/Satoshi-Regular.woff2") format("woff2"), - url("/fonts/Satoshi/Satoshi-Regular.woff") format("woff"); - font-weight: 400; - font-style: normal; - font-display: swap; -} - -@font-face { - font-family: "Satoshi"; - src: - url("/fonts/Satoshi/Satoshi-Medium.woff2") format("woff2"), - url("/fonts/Satoshi/Satoshi-Medium.woff") format("woff"); - font-weight: 500; - font-style: normal; - font-display: swap; -} - -@font-face { - font-family: "Satoshi"; - src: - url("/fonts/Satoshi/Satoshi-Bold.woff2") format("woff2"), - url("/fonts/Satoshi/Satoshi-Bold.woff") format("woff"); - font-weight: 700; -======= INTER VARIABLE FONT ================================================ */ `@font-face` { font-family: "Inter"; src: url("/fonts/Inter/Inter-roman.var.woff2") format("woff2-variations"); font-weight: 100 900; ->>>>>>> Stashed changes font-style: normal; font-display: swap; }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/.vitepress/theme/style.css` around lines 96 - 146, Remove the Git conflict markers and the old Satoshi `@font-face` blocks, keeping the Inter `@font-face` definition; specifically delete the lines containing <<<<<<< Updated upstream, =======, and >>>>>>> Stashed changes and remove the three `@font-face` blocks that declare font-family "Satoshi", leaving only the `@font-face` for font-family "Inter" (ensure it includes font-weight, font-style, and font-display properties). This will resolve the merge conflict and restore valid CSS.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/.vitepress/config.mts`:
- Around line 96-106: The preload entry for the Inter variable font (the link
object in docs/.vitepress/config.mts referencing
"/fonts/Inter/Inter-roman.var.woff2") points to a missing asset; either add the
Inter variable font file into docs/public/fonts/Inter/ with the exact filename
or update the preload entry and the corresponding `@font-face` src in style.css to
use an existing font (e.g., IBMPlexMono or Satoshi) with matching paths and
filenames so the preload and `@font-face` references are consistent and do not 404
at runtime.
In `@docs/.vitepress/theme/style.css`:
- Around line 670-693: The CSS block for the navbar search is malformed due to a
merged selector and property mix (remove the stray ".VPNavBarSearch.search {
.VPNavBarSearch.search `#docsearch` {" fragment and the misplaced
"justify-content: center;" inside it), so fix the .VPNavBarSearch.search rule to
be a single valid block and ensure the nested selectors target `#docsearch` and
`#local-search` correctly; update the rules for .VPNavBarSearch.search,
.VPNavBarSearch.search `#docsearch`, .VPNavBarSearch.search `#local-search`, and
.VPNavBarSearch.search .DocSearch.DocSearch-Button so there are no nested
selector tokens inside property lists and widths/spacing (max-width, min-width,
flex, margin, padding) are applied in proper CSS blocks.
- Around line 200-278: Remove the leftover merge-conflict markers and
consolidate the font-family and typography blocks so only the "Inter" font and
the added typography rules remain; specifically, delete the conflict markers
(<<<<<<<, =======, >>>>>>>) and ensure --vp-font-family and
--vp-font-family-heading both use "Inter" alongside the existing system fonts,
and keep the added body font-feature-settings and heading/body selectors
(.vp-doc h1..h6, .VPHero .name/.tagline, .vp-doc p, .vp-doc li, .VPNavBar
.title) with their weights, letter-spacing, line-height, and other typographic
rules intact.
---
Outside diff comments:
In `@docs/.vitepress/theme/style.css`:
- Around line 96-146: Remove the Git conflict markers and the old Satoshi
`@font-face` blocks, keeping the Inter `@font-face` definition; specifically delete
the lines containing <<<<<<< Updated upstream, =======, and >>>>>>> Stashed
changes and remove the three `@font-face` blocks that declare font-family
"Satoshi", leaving only the `@font-face` for font-family "Inter" (ensure it
includes font-weight, font-style, and font-display properties). This will
resolve the merge conflict and restore valid CSS.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: cd5984d6-d125-41aa-bc0b-0cc4161635d3
⛔ Files ignored due to path filters (6)
docs/public/fonts/Satoshi/Satoshi-Bold.woffis excluded by!**/*.woffdocs/public/fonts/Satoshi/Satoshi-Bold.woff2is excluded by!**/*.woff2docs/public/fonts/Satoshi/Satoshi-Medium.woffis excluded by!**/*.woffdocs/public/fonts/Satoshi/Satoshi-Medium.woff2is excluded by!**/*.woff2docs/public/fonts/Satoshi/Satoshi-Regular.woffis excluded by!**/*.woffdocs/public/fonts/Satoshi/Satoshi-Regular.woff2is excluded by!**/*.woff2
📒 Files selected for processing (7)
.claude/launch.jsondocs/.vitepress/config.mtsdocs/.vitepress/theme/components/Card.vuedocs/.vitepress/theme/components/TabNav.vuedocs/.vitepress/theme/index.tsdocs/.vitepress/theme/style.cssdocs/index.md
| // Font preload for critical rendering | ||
| [ | ||
| "link", | ||
| { | ||
| rel: "preload", | ||
| href: "/fonts/Inter/Inter-roman.var.woff2", | ||
| as: "font", | ||
| type: "font/woff2", | ||
| crossorigin: "", | ||
| }, | ||
| ], |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify Inter font file exists
fd -t f "Inter-roman.var.woff2" docs/.vitepress/public/fonts/
# If not found in public/fonts, search broader
if [ $? -ne 0 ]; then
echo "Searching entire docs directory..."
fd -t f "Inter-roman.var.woff2" docs/
fiRepository: makeplane/developer-docs
Length of output: 236
🏁 Script executed:
# Find style.css files
fd -t f "style.css" docs/
# List the public directory structure
find docs/.vitepress/public -type d -o -type f 2>/dev/null | head -20
# Search for any reference to Inter font in config files
rg "Inter" docs/.vitepress/ -t mts -t ts -t cssRepository: makeplane/developer-docs
Length of output: 95
🏁 Script executed:
# Check git history for font-related changes in this PR
git log -1 --name-status
git diff HEAD~1 HEAD --name-status | grep -i fontRepository: makeplane/developer-docs
Length of output: 25930
🏁 Script executed:
cat -n docs/.vitepress/theme/style.cssRepository: makeplane/developer-docs
Length of output: 28902
🏁 Script executed:
# Also check the config.mts around the preload section for any other font references
sed -n '80,120p' docs/.vitepress/config.mtsRepository: makeplane/developer-docs
Length of output: 1335
Font file missing: preload references non-existent asset.
The Inter font file (/fonts/Inter/Inter-roman.var.woff2) does not exist in the repository. While the preload declaration in config.mts correctly matches the @font-face src path in style.css, the actual font file is absent from docs/public/fonts/. This will cause the preload to fail at runtime with a 404 error, negating any performance benefit and potentially breaking the application's typography.
Add the Inter variable font file to docs/public/fonts/Inter/ or update both the preload link and @font-face declaration in style.css to reference the available fonts (IBMPlexMono or Satoshi).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/.vitepress/config.mts` around lines 96 - 106, The preload entry for the
Inter variable font (the link object in docs/.vitepress/config.mts referencing
"/fonts/Inter/Inter-roman.var.woff2") points to a missing asset; either add the
Inter variable font file into docs/public/fonts/Inter/ with the exact filename
or update the preload entry and the corresponding `@font-face` src in style.css to
use an existing font (e.g., IBMPlexMono or Satoshi) with matching paths and
filenames so the preload and `@font-face` references are consistent and do not 404
at runtime.
docs/.vitepress/theme/style.css
Outdated
| <<<<<<< Updated upstream | ||
| "Satoshi", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, sans-serif; | ||
| ======= | ||
| "Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, sans-serif; | ||
| --vp-font-family-heading: | ||
| "Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, sans-serif; | ||
| >>>>>>> Stashed changes | ||
| --vp-font-family-mono: | ||
| "IBM Plex Mono", ui-monospace, SFMono-Regular, "SF Mono", Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", | ||
| monospace; | ||
| } | ||
|
|
||
| <<<<<<< Updated upstream | ||
| ======= | ||
| /* ================================================ | ||
| TYPOGRAPHY OPTIMIZATION | ||
| ================================================ */ | ||
|
|
||
| /* Enable Inter's OpenType features for better readability */ | ||
| body { | ||
| font-feature-settings: "cv01", "cv02", "cv03", "cv04", "ss01", "ss03"; | ||
| } | ||
|
|
||
| /* Headings use Inter with weight hierarchy and tight tracking */ | ||
| .vp-doc h1, | ||
| .vp-doc h2, | ||
| .vp-doc h3, | ||
| .vp-doc h4, | ||
| .vp-doc h5, | ||
| .vp-doc h6, | ||
| .VPNavBar .title, | ||
| .VPHero .name, | ||
| .VPHero .tagline { | ||
| font-family: var(--vp-font-family-heading); | ||
| } | ||
|
|
||
| .vp-doc h1, | ||
| .VPHero .name { | ||
| font-weight: 700; | ||
| letter-spacing: -0.025em; | ||
| line-height: 1.2; | ||
| } | ||
|
|
||
| .vp-doc h2, | ||
| .VPHero .tagline { | ||
| font-weight: 650; | ||
| letter-spacing: -0.02em; | ||
| line-height: 1.3; | ||
| } | ||
|
|
||
| .vp-doc h3 { | ||
| font-weight: 600; | ||
| letter-spacing: -0.015em; | ||
| line-height: 1.35; | ||
| } | ||
|
|
||
| .vp-doc h4, | ||
| .vp-doc h5, | ||
| .vp-doc h6 { | ||
| font-weight: 600; | ||
| letter-spacing: -0.01em; | ||
| line-height: 1.4; | ||
| } | ||
|
|
||
| /* Body text: optimized spacing for readability at 16px */ | ||
| .vp-doc p, | ||
| .vp-doc li { | ||
| line-height: 1.75; | ||
| letter-spacing: -0.011em; | ||
| word-spacing: 0.01em; | ||
| } | ||
|
|
||
| /* Navbar title: match heading style */ | ||
| .VPNavBar .title { | ||
| font-weight: 600; | ||
| letter-spacing: -0.015em; | ||
| } | ||
|
|
||
| >>>>>>> Stashed changes |
There was a problem hiding this comment.
Resolve second merge conflict block.
Another unresolved merge conflict exists in the font-family and typography optimization sections.
🔧 Proposed fix - Remove conflict markers, keep Inter font and typography rules
/* Fonts */
--vp-font-family-base:
-<<<<<<< Updated upstream
- "Satoshi", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;
-=======
"Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;
--vp-font-family-heading:
"Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;
->>>>>>> Stashed changes
--vp-font-family-mono:
"IBM Plex Mono", ui-monospace, SFMono-Regular, "SF Mono", Menlo, Monaco, Consolas, "Liberation Mono", "Courier New",
monospace;
}
-<<<<<<< Updated upstream
-=======
/* ================================================
TYPOGRAPHY OPTIMIZATION
================================================ */
/* Enable Inter's OpenType features for better readability */
body {
font-feature-settings: "cv01", "cv02", "cv03", "cv04", "ss01", "ss03";
}
/* ... rest of typography rules ... */
->>>>>>> Stashed changes
/* Dark mode */🧰 Tools
🪛 Biome (2.4.6)
[error] 200-200: Unexpected value or character.
(parse)
[error] 201-201: Expected a compound selector but instead found '"Satoshi"'.
(parse)
[error] 201-201: Expected a relative selector but instead found '"Segoe UI"'.
(parse)
[error] 201-201: expected , but instead found ;
(parse)
[error] 203-203: Expected a relative selector but instead found '"Segoe UI"'.
(parse)
[error] 203-203: expected , but instead found ;
(parse)
[error] 204-204: expected , but instead found --vp-font-family-heading
(parse)
[error] 205-205: Unexpected value or character.
(parse)
[error] 205-205: Expected a relative selector but instead found '"Segoe UI"'.
(parse)
[error] 205-205: expected , but instead found ;
(parse)
[error] 206-206: expected , but instead found >
(parse)
[error] 206-206: Expected a relative selector but instead found '>'.
(parse)
[error] 206-206: Expected a relative selector but instead found '>'.
(parse)
[error] 206-206: Expected a relative selector but instead found '>'.
(parse)
[error] 206-206: Expected a relative selector but instead found '>'.
(parse)
[error] 206-206: Expected a relative selector but instead found '>'.
(parse)
[error] 206-206: Expected a relative selector but instead found '>'.
(parse)
[error] 208-208: Unexpected value or character.
(parse)
[error] 208-208: Expected a relative selector but instead found '"SF Mono"'.
(parse)
[error] 208-208: Expected a relative selector but instead found '"Liberation Mono"'.
(parse)
[error] 208-208: Expected a relative selector but instead found '"Courier New"'.
(parse)
[error] 209-209: expected , but instead found ;
(parse)
[error] 212-212: expected , but instead found Updated
(parse)
[error] 213-213: Expected a compound selector but instead found '='.
(parse)
[error] 219-219: expected , but instead found body
(parse)
[error] 278-278: Expected a relative selector but instead found '>'.
(parse)
[error] 278-278: Expected a relative selector but instead found '>'.
(parse)
[error] 278-278: Expected a relative selector but instead found '>'.
(parse)
[error] 278-278: Expected a relative selector but instead found '>'.
(parse)
[error] 278-278: Expected a relative selector but instead found '>'.
(parse)
[error] 278-278: Expected a relative selector but instead found '>'.
(parse)
[error] 200-200: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 200-200: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 201-201: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 201-201: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 201-201: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 201-201: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 201-201: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 203-203: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 203-203: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 203-203: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 203-203: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 203-203: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 205-205: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 205-205: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 205-205: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 205-205: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 205-205: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 206-206: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 206-206: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 208-208: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 208-208: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 208-208: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 208-208: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 209-209: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 212-212: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 212-212: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 278-278: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
[error] 278-278: Unknown type selector is not allowed.
(lint/correctness/noUnknownTypeSelector)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/.vitepress/theme/style.css` around lines 200 - 278, Remove the leftover
merge-conflict markers and consolidate the font-family and typography blocks so
only the "Inter" font and the added typography rules remain; specifically,
delete the conflict markers (<<<<<<<, =======, >>>>>>>) and ensure
--vp-font-family and --vp-font-family-heading both use "Inter" alongside the
existing system fonts, and keep the added body font-feature-settings and
heading/body selectors (.vp-doc h1..h6, .VPHero .name/.tagline, .vp-doc p,
.vp-doc li, .VPNavBar .title) with their weights, letter-spacing, line-height,
and other typographic rules intact.
| /* Center search area in desktop navbar and make the input wider. */ | ||
| @media (min-width: 960px) { | ||
| .VPNavBarSearch.search { | ||
| .VPNavBarSearch.search #docsearch { | ||
| width: 100%; | ||
| max-width: 320px; | ||
| } justify-content: center; | ||
| flex: 1 1 520px; | ||
| min-width: 300px; | ||
| max-width: 520px; | ||
| margin-left: auto; | ||
| margin-right: auto; | ||
| padding-left: 0 !important; | ||
| } | ||
|
|
||
| .VPNavBarSearch.search #local-search, | ||
| .VPNavBarSearch.search #docsearch { | ||
| width: 100%; | ||
| max-width: 320px; | ||
| } | ||
|
|
||
| .VPNavBarSearch.search .DocSearch.DocSearch-Button { | ||
| width: 100% !important; | ||
| } |
There was a problem hiding this comment.
Fix malformed CSS in navbar search section.
This block contains duplicate/overlapping selectors that appear to be a merge artifact. Lines 673-676 have malformed CSS with selectors inside property values.
🔧 Proposed fix
/* Center search area in desktop navbar and make the input wider. */
`@media` (min-width: 960px) {
.VPNavBarSearch.search {
- .VPNavBarSearch.search `#docsearch` {
- width: 100%;
- max-width: 320px;
- } justify-content: center;
+ justify-content: center;
flex: 1 1 520px;
min-width: 300px;
max-width: 520px;
margin-left: auto;
margin-right: auto;
padding-left: 0 !important;
}
.VPNavBarSearch.search `#local-search`,
.VPNavBarSearch.search `#docsearch` {
width: 100%;
max-width: 320px;
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| /* Center search area in desktop navbar and make the input wider. */ | |
| @media (min-width: 960px) { | |
| .VPNavBarSearch.search { | |
| .VPNavBarSearch.search #docsearch { | |
| width: 100%; | |
| max-width: 320px; | |
| } justify-content: center; | |
| flex: 1 1 520px; | |
| min-width: 300px; | |
| max-width: 520px; | |
| margin-left: auto; | |
| margin-right: auto; | |
| padding-left: 0 !important; | |
| } | |
| .VPNavBarSearch.search #local-search, | |
| .VPNavBarSearch.search #docsearch { | |
| width: 100%; | |
| max-width: 320px; | |
| } | |
| .VPNavBarSearch.search .DocSearch.DocSearch-Button { | |
| width: 100% !important; | |
| } | |
| /* Center search area in desktop navbar and make the input wider. */ | |
| `@media` (min-width: 960px) { | |
| .VPNavBarSearch.search { | |
| justify-content: center; | |
| flex: 1 1 520px; | |
| min-width: 300px; | |
| max-width: 520px; | |
| margin-left: auto; | |
| margin-right: auto; | |
| padding-left: 0 !important; | |
| } | |
| .VPNavBarSearch.search `#local-search`, | |
| .VPNavBarSearch.search `#docsearch` { | |
| width: 100%; | |
| max-width: 320px; | |
| } | |
| .VPNavBarSearch.search .DocSearch.DocSearch-Button { | |
| width: 100% !important; | |
| } |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/.vitepress/theme/style.css` around lines 670 - 693, The CSS block for
the navbar search is malformed due to a merged selector and property mix (remove
the stray ".VPNavBarSearch.search { .VPNavBarSearch.search `#docsearch` {"
fragment and the misplaced "justify-content: center;" inside it), so fix the
.VPNavBarSearch.search rule to be a single valid block and ensure the nested
selectors target `#docsearch` and `#local-search` correctly; update the rules for
.VPNavBarSearch.search, .VPNavBarSearch.search `#docsearch`,
.VPNavBarSearch.search `#local-search`, and .VPNavBarSearch.search
.DocSearch.DocSearch-Button so there are no nested selector tokens inside
property lists and widths/spacing (max-width, min-width, flex, margin, padding)
are applied in proper CSS blocks.
1 participant
Description
single variable font, with preload for faster rendering
and components, organized into "Explore the docs", "Popular guides", and "Developer resources" sections
Type of Change
Summary by CodeRabbit
Release Notes
New Features
Style