You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DESIGN.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ Controls and nested panels use gently rounded 6–10px corners. Breadcrumb state
163
163
164
164
### Navigation
165
165
166
-
- **Top tabs:** Natural-width labels with a 3px active underline. Each tab links to its language-aware section directory (for example, `/social/` or `/en/social/`), where the generated section landing page replaces the aliased fallback document rather than selecting the first document. Cross-origin links and entries that own a submenu leave the primary tab group and appear in the right utility cluster before language, repository, and theme controls. Their triggers share the language control's compact styling; desktop submenus always open downward. In the mobile drawer, direct auxiliary links rejoin the two-column primary navigation grid. Languages and the repository control remain in the compact utility row below it, followed by every submenu expanded as its own full-width row. Submenu links keep readable intrinsic widths in one line and become independently horizontally scrollable when they exceed the drawer, without widening the page. The drawer owns vertical overflow, so additional links and menus remain reachable without compressed labels or clipped popovers. Additional language and auxiliary entries flow from their Markdown or dictionary sources without layout rewrites. Language changes preserve the current section or page when its Markdown exists, otherwise they resolve to the configured home page for the target language instead of opening a 404.
166
+
- **Top tabs:** Natural-width labels with a 3px active underline. Each tab links to its language-aware section directory (for example, `/social/` or `/en/social/`), where the generated section landing page replaces the aliased fallback document rather than selecting the first document. Cross-origin links and entries that own a submenu leave the primary tab group and appear in the right utility cluster before language, repository, and theme controls. A submenu whose parent has a URL keeps that parent as a normal utility link with a compact adjacent disclosure button; a parent without a URL uses the full label button as the disclosure control. Desktop submenus always open downward. In the mobile drawer, the primary links, centered direct auxiliary links, language/repository row, and expanded submenus share one intrinsic-height navigation shell so no flex spacer can separate them. Linked submenu parents join their children as equal horizontal items instead of becoming a detached heading; unlinked submenu parents remain the desktop disclosure label but are omitted from the mobile link row. Item dividers match the language row, and each row scrolls horizontally when needed without widening the drawer. The drawer owns vertical overflow, so additional links and menus remain reachable without compressed labels or clipped popovers. Additional language and auxiliary entries flow from their Markdown or dictionary sources without layout rewrites. Language changes preserve the current section or page when its Markdown exists, otherwise they resolve to the configured home page for the target language instead of opening a 404; after selecting a language, the target hash is applied and the page refreshes once so Docsify, generated headings, breadcrumbs, and navigation all rebuild from the same dictionary.
167
167
- **Document tree:** Parent Markdown pages may also own collapsible child pages. Sibling groups behave as an accordion: opening one closes the other open group at the same depth with a measured 220ms height, spacing, and opacity transition. Selecting a sibling parent page completes that same transition before the route changes; initial load and browser history restoration remain immediate. Every link uses a shared 2.75rem Flex row so text and arrow controls remain vertically centered. Links use regular-weight text and rounded neutral-gray hover panels rather than underlines. The panel is an opacity layer with a perceptible 180ms fade and the text color transitions independently; neither position, scale, nor weight changes. Reduced-motion mode retains a 120ms opacity/color fade. Selected links retain the gray panel and use the blue accent for text. A parent link and its arrow button share one hover state. Docsify section queries such as `?id=...` do not alter the selected Markdown page; selection and `aria-current` are synchronized from the query-free document route after every render.
168
168
-**Page outline:** H2/H3 links never remain inside the document tree; they occupy the right rail or isolated sidebar footer.
169
169
-**Breadcrumb:** Hidden on the Wiki home page and on a single-document tab's root document. Every page beneath a tab that owns a generated overview starts with a home icon linked to the language-aware Wiki home, followed by the tab overview and the complete sidebar ancestry (for example, Home > Game Docs > Custom Post-processing > V2). Nested routes inside a single-document tab retain Home plus their document ancestry. The Custom Post-processing parent document alone uses a short render gate before Docsify replaces its article; the completed-render task releases it after inserting the breadcrumb above H1, preventing that page's heading-only first frame without delaying other documents. Intermediate links use regular-weight body color and the same neutral pill hover as Home; only the current page keeps the blue active pill.
0 commit comments