Split febcode reference out of the Features tab into its own top-level tab

Per Steve Maas's request in the FEBio discussion thread, the febcode
input-file-format reference was easy to miss buried at the bottom of the
Features tab's nav. build.py now writes it as a fourth top-level nav key
(a sibling of Theory/Studio/Features) instead of tools/features2md.py
nesting it inside the Features manual's own nav tree.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CKmmAMYDcwi64diTqw5MPb

Author: Wesley-Jakob-Gilbert

CLAUDE.md

@@ -5,9 +5,9 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 ## What this repo is
 
 A MkDocs site that generates all of FEBio's manuals into one site (Material for MkDocs theme, indigo
-palette, `pymdownx.arithmatex` + MathJax for equations, footnote-based citations). The site has three
-`navigation.tabs`, each a separately generated manual, orchestrated by `build.py`'s `MANUALS` list. Each
-entry has a `"kind"` selecting its converter:
+palette, `pymdownx.arithmatex` + MathJax for equations, footnote-based citations). The site has four
+`navigation.tabs`. Three are separately generated manuals, orchestrated by `build.py`'s `MANUALS` list —
+each entry has a `"kind"` selecting its converter:
 
 - **Theory** (`kind: "lyx"`, `source/FEBio_Theory_Manual.lyx` → `docs/theory/`) — all 9 chapters (1–8
   plus Appendix A) are converted.
@@ -16,7 +16,14 @@ entry has a `"kind"` selecting its converter:
 - **Features** (`kind: "features"`, `source/feature-manual/` → `docs/features/`) — the FEBio Feature
   Manual, absorbed from the standalone `febio-feature-manual` repo. Generated by `tools/features2md.py`
   (not `lyx2md.py`) from `febio_features.json` plus per-feature description fragments in `meta/`.
-  660 feature pages, 7 module pages, plot/log variable tables, and the hand-authored febcode page.
+  660 feature pages, 7 module pages, and plot/log variable tables.
+
+The fourth tab, **Febcode** (`docs/features/febcode.md`, hand-authored), is *not* in `MANUALS` — it's a
+single page that lives under the Features manual's `docs_root` but that `build.py` promotes to its own
+top-level nav key right after the `MANUALS` loop, rather than letting it stay nested inside the Features
+tab's own nav tree as it used to (see the comments at both call sites in `build.py` /
+`tools/features2md.py` if this changes again — split out per
+[Steve Maas's request](https://github.com/febiosoftware/FEBio/discussions/130#discussioncomment-18179757)).
 
 `source/` is vendored/checked-in for all three manuals, so the repo builds standalone from a bare clone.
 

README.md

@@ -1,8 +1,8 @@
 # FEBio-Documentation
 
 A MkDocs site collecting FEBio's manuals into one searchable site (Material for MkDocs theme, indigo
-palette, `pymdownx.arithmatex` + MathJax for equations, footnote-based citations). The site has three
-tabs, each a separately generated manual:
+palette, `pymdownx.arithmatex` + MathJax for equations, footnote-based citations). The site has four
+tabs:
 
 - **Theory** — the FEBio Theory Manual. Started as a single-chapter pilot (Chapter 2, Continuum
   Mechanics); now covers the complete manual — Chapters 1 through 8 plus Appendix A (Tensor Calculus).
@@ -13,6 +13,11 @@ tabs, each a separately generated manual:
 - **Features** — the FEBio Feature Manual, absorbed from the standalone
   [`febio-feature-manual`](https://github.com/febiosoftware/febio-feature-manual) repository. 660 feature
   pages across 32 categories, 7 module pages, and the plot/log output-variable tables.
+- **Febcode** — the FEBio input-file-format (`.feb`) reference, a single hand-authored page that used to
+  be buried at the bottom of the Feature Manual's own nav. Split out into its own top-level tab per
+  [Steve Maas's request](https://github.com/febiosoftware/FEBio/discussions/130#discussioncomment-18179757),
+  since it's a distinct kind of reference (input file syntax, not feature-by-feature parameter docs) that
+  deserved to be easy to find from the site's tab bar.
 
 The two LyX manuals share one generic, stdlib-only converter (`tools/lyx2md.py`). The Feature Manual has
 no LyX source — it is generated from FEBio's exported feature database by `tools/features2md.py`. Both
@@ -45,7 +50,7 @@ tools/features2md.py            the Feature Manual generator (port of febio-feat
 build.py                        runs the right converter per manual (see its MANUALS list), generates mkdocs.yml
 docs/                            generated Markdown SOURCE for mkdocs -- this is mkdocs's input, not the
                                  deployed site; see "Deployment" below
-  index.md                      site root landing page (not manual-specific; links to all three tabs)
+  index.md                      site root landing page (not manual-specific; links to all four tabs)
   theory/index.md                Theory Manual Preface (hand-authored)
   theory/chapter<N>/*.md         Theory Manual generated pages
   studio/index.md                Studio Manual Preface (hand-authored)
@@ -105,13 +110,17 @@ the entry's `"kind"`:
   per converted chapter, expanding to that chapter's sections.
 - `"features"` (Features) → `tools/features2md.py`. Its sidecar records a freely nested nav tree, which
   `build.py`'s `write_nav()` emits recursively; the nav becomes a Preface entry followed by Modules,
-  Features (subdivided by category), Output, and Febcode.
+  Features (subdivided by category), and Output.
 
 `"kind"` also gates the figure-fetching step: only `"lyx"` manuals fetch missing figures from upstream,
 since the Feature Manual's figures are vendored in `docs/features/features/figs/`.
 
 Navigation uses `navigation.tabs`, so each manual is exactly one top-level nav key rendered as a tab
-("Theory", "Studio", "Features").
+("Theory", "Studio", "Features"). Febcode (`docs/features/febcode.md`) is the one exception: it's a page
+that lives under the Features manual's `docs_root`, but `build.py` writes it as its own top-level nav key
+— a fourth tab — right after the `MANUALS` loop, rather than letting `tools/features2md.py` nest it inside
+the Features tab as it used to. `tools/features2md.py`'s nav tree deliberately omits it for this reason;
+see the comments at both call sites if this needs to change again.
 
 ## Deployment
 

build.py

@@ -228,6 +228,14 @@ def write_nav(f, items, indent):
                 for title, path in chap["nav"]:
                     f.write(f"      - {title}: {path}\n")
 
+    # Febcode (the FEBio input-file-format reference) is a page of the
+    # Features manual's own docs_root, but per Steve Maas's request
+    # (github.com/febiosoftware/FEBio/discussions/130#discussioncomment-18179757)
+    # it gets its own top-level tab here rather than being nested inside the
+    # Features tab, since it's a distinct kind of reference (input file
+    # syntax) from the feature-by-feature parameter docs around it.
+    f.write("  - Febcode: features/febcode.md\n")
+
 for manual in MANUALS:
     if manual["kind"] == "features":
         t = manual_stats[manual["key"]]["totals"]

docs/index.md

@@ -10,5 +10,6 @@ versioned static site with [MkDocs](https://www.mkdocs.org/) and the
   GUI.
 - **[Features](features/index.md)** — the FEBio Feature Manual: a reference for every feature
   available in FEBio, with its type string, parameters, and description.
+- **[Febcode](features/febcode.md)** — the FEBio input file (`.feb`) format reference.
 
 Use the tabs above to browse any of the manuals.

mkdocs.yml

@@ -957,4 +957,4 @@ nav:
     - "Output":
       - "Plot variables": features/plotvars.md
       - "Log variables": features/logvars.md
-    - "Febcode": features/febcode.md
+  - Febcode: features/febcode.md

tools/_stats_features.json

@@ -2850,10 +2850,6 @@
           "features/logvars.md"
         ]
       ]
-    ],
-    [
-      "Febcode",
-      "features/febcode.md"
     ]
   ],
   "totals": {

tools/features2md.py

@@ -244,14 +244,18 @@ def main():
         "The following log variables are available in FEBio:",
         log_variables, missing_vars)
 
+    # Febcode (the FEBio input-file-format reference) is intentionally left
+    # out of this nav tree -- build.py promotes it to its own top-level tab,
+    # a sibling of Theory/Studio/Features, rather than nesting it inside the
+    # Features tab. See build.py's MANUALS loop / the Febcode tab it writes
+    # right after it.
     nav = [
         ["Modules", module_nav],
         ["Features", feature_nav],
         ["Output", [
             ["Plot variables", f"{args.nav_root}/plotvars.md"],
             ["Log variables", f"{args.nav_root}/logvars.md"],
         ]],
-        ["Febcode", f"{args.nav_root}/febcode.md"],
     ]
 
     stats = {