update-paths

Automating documentation inventory for MDX files involves scanning pillar directories to track new, moved, or deleted files and compile them into a manifest. This process targets .mdx files under specific repository paths while excluding template locations.

Keeping a documentation file index updated requires scanning directories for .mdx files, sorting them alphabetically within subsections, and recording counts and timestamps. This generates a current listing in a manifest file with full repository-root paths.

Generating a manifest of MDX files with per-section counts requires scanning pillar directories, organizing files by subsection, and sorting them alphabetically. The output records per-pillar counts, a grand total, and the last updated timestamp in a markdown file.

Previewing documentation inventory changes before applying them is possible using a dry-run command. This allows you to verify the updated listing of .mdx files without modifying the actual manifest file.

The documentation inventory process does exclude template files. It specifically targets .mdx files in pillar directories while ignoring any files located within template directories to maintain an accurate documentation manifest.