Projects Overview

The portal currently brings together eight Devalltect projects, including its own maintenance documentation. Each project keeps its own domain and documentation structure while sharing navigation, design components, build validation, and deployment guidance.

Project Directory

Project	Started	Documented version	Primary purpose	Documentation
Devalltect Homepage	Sep 2026	v1.0.0	Guide visitors to the Devalltect portfolio, documentation, projects, and engineering profiles.	Explore the homepage
Devalltect Portfolio	Sep 2026	v2.1.0	Present projects, experience, and technical growth through a bilingual interactive portfolio.	Explore the portfolio
Foksiku	Sep 2026	v0.2.0	Record and report private Telegram expenses through a bilingual, role-aware interface.	Explore Foksiku
Devalltect Docs	Aug 2026	v1.2.0	Maintain the bilingual documentation portal, shared discovery UI, release freshness, and deployment workflows.	Explore Devalltect Docs
Path Header Scanner	May 2026	v1.0.1	Preview, validate, and apply consistent path headers across supported languages.	Explore Path Header Scanner
Reflow	Apr 2026	v1.0.2	Convert tags, recover tag-driven releases, and publish tagged container images.	Explore Reflow
Doc Gen	Mar 2026	v1.1.0	Generate, print, and analyze project structure documentation.	Explore Doc Gen
Custy	Jul 2025	v2.1.2	Coordinate Git workflows, validation, versioning, changelogs, commits, tags, pushes, backups, cleanup, and release pipelines.	Explore Custy

Devalltect Homepage

The v1.0.0 documentation describes the bilingual Astro gateway, configurable public destinations, metadata workflow, static architecture, and root GitHub Pages deployment boundary.

Foksiku

The v0.2.0 documentation covers deterministic expense entry, reusable products, confirmations, append-only corrections, reports, access roles, invitations, deployment, spreadsheet structure, logging, retention, and troubleshooting. The bot provides English and Indonesian responses, per-user language preferences, localized action buttons, a compact menu, and Indonesian aliases. Optional local-model NLU remains a later milestone.

Devalltect Portfolio

The v2.0.0 release introduced the public portfolio experience, bilingual navigation, project discovery, accessible galleries, theme and motion preferences, static Vercel deployment, and optional Docker development workflow. Internal maintenance details remain in the source repository.

Devalltect Docs

The v1.2.0 portal documentation explains local and container development, shared metadata, bilingual maintenance, version freshness, validation, and GitHub or GitLab Pages deployment.

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.1.0 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.