RepoDNA v1.3.2: A Dedicated Documentation Website and Reliability Improvements

#opensource #rust #devtools #documentation

RepoDNA v1.3.2: A Dedicated Documentation Website and Reliability Improvements

Tags: opensource, rust, devtools, webdev

RepoDNA v1.3.2 is now available!

This release introduces a dedicated documentation website and improves several parts of the project's error handling, GitHub Actions downloads, and documentation workflow.

RepoDNA is an open-source, local-first repository intelligence and code archaeology tool. It helps developers explore code structure, architecture, dependencies, Git history, quality signals, and project evolution.

The goal is to make a repository easier to understand—not just easier to browse.

A documentation website of its own

The documentation now has a dedicated home:

https://sanskarin.github.io/RepoDNA/docs/

The site brings together the project's guides, changelog, roadmap, policies, examples, benchmarks, and fixtures.

It includes:

Search across documentation sections.
A sidebar that follows the documentation index.
Previous and next page navigation.
Copy buttons for code examples.
Light and dark themes.
Responsive layouts for phones.
Print-friendly pages.
Links between related guides and repository files.

The documentation is published alongside the web version, making the guides easier to discover and navigate.

Better error handling

The repodna-wasm component now reports missing files and folders more clearly.

Previously, some invalid inputs could surface low-level Node.js errors or be treated as the wrong kind of input. The improved behavior explains what is missing and clarifies when commands such as report or card require an analysis file.

More reliable GitHub Actions downloads

Temporary failures from GitHub's servers could cause downloads to fail after only a short period.

The GitHub Action now retries download attempts for up to two minutes and provides a more accurate error when a download actually fails.

The guide for the action has also been updated to include the security-only profile in its supported profile options.

Documentation checks

The development and documentation workflows now check for broken links and anchors. This helps catch navigation problems before changes are released.

The project also updates documentation destinations and support links across the relevant application and repository pages.

Why this release matters

Documentation is part of the developer experience. It should be easy to search, navigate, read on a small screen, and use while working through real development problems.

Likewise, errors should explain what went wrong, and automation should distinguish temporary infrastructure failures from genuinely missing files.

Those improvements make the project easier to explore and maintain.