Projects Overview

The portal currently brings together four developer-tool projects. Each project keeps its own domain and documentation structure while sharing navigation, design components, build validation, and deployment.

Project Directory

Project	Documented version	Primary purpose	Documentation
Path Header Scanner	v1.0.1	Preview, validate, and apply consistent path headers across supported languages.	Explore Path Header Scanner
Doc Gen	v1.0.2	Generate, print, and analyze project structure documentation.	Explore Doc Gen
Reflow	v1.0.2	Convert tags, recover tag-driven releases, and publish tagged container images.	Explore Reflow
Custy	v2.1.2	Coordinate Git workflows, validation, versioning, changelogs, commits, tags, pushes, backups, cleanup, and release pipelines.	Explore Custy

Path Header Scanner

The v1.0.1 documentation covers preview-first scanning, explicit apply and dry-run behavior, language strategies, configuration, examples, architecture, development, and troubleshooting in English and Indonesian.

Doc Gen

The v1.0.2 documentation covers initialization, generation, printing, analysis, profiles, smart mode, dry-run, configuration, architecture, development, and troubleshooting in English and Indonesian.

Reflow

The v1.0.2 documentation covers repository targeting, local and remote conversion, release recovery, Docker publishing, safety, configuration, architecture, development, and troubleshooting in English and Indonesian. reflow tags replay is documented only as a deprecated alias for reflow releases recover.

Custy

Custy v2.1.2 includes getting started, command documentation, concepts, full configuration reference, pipeline profiles and ordering, user and developer guides, architecture, concise references, and troubleshooting. English is the default and a complete Indonesian version is available.

:::warning Experimental Custy workflow

The custy workflow branch feature is still experimental. Its documentation identifies current implementation limits and should not be read as a stable public workflow contract.

:::

Documentation Coverage

Documentation depth varies because the projects evolve independently. A page being available does not automatically mean every described feature is stable; use status labels, warnings, and source-aligned references where provided.

Adding Another Project

1. Create a top-level docs/<project-name>/ directory.
2. Add a clear overview and _category_.json navigation metadata.
3. Organize user, command, reference, developer, and architecture material according to the project's actual needs.
4. Add cross-project navigation from this page.
5. Run yarn typecheck and yarn build so MDX, routes, links, and both locales are validated.