All notable changes to this project are documented in this file.
This changelog is automatically generated by Custy from structured commit messages.
🔗 Compare: https://github.com/devalltect00/devalltect-docs/compare/v1.0.0...HEAD
Release Unreleased
Summary
Expand the bilingual documentation portal from four developer tools to five Devalltect projects by adding a public portfolio guide and release baseline.
- resolve provider CLI paths on Windows
- add English and Indonesian portfolio overview, getting-started, and
- register the portfolio in shared project metadata, homepage discovery, and
- connect the portal navbar and footer to the central Devalltect homepage with
- document the v2.0.0 visitor experience, static Vercel delivery, optional
- keep internal maintenance, credentials, private project data, and security
- update portal metadata, README tables, badges, maintainer guidance, and
Tags
feature • bugfix • portfolio-docs
Release Stable
Summary
Publish the first stable release of the Devalltect documentation portal after completing the multilingual content, reusable component integration, project version tracking, production delivery, and consistency work that remained open during the abandoned alpha plan. The release consolidates four untagged development checkpoints: the complete multilingual documentation foundation, project previews and portal-maintainer documentation, clearer homepage navigation and reader paths, then optional reproducible container workflows. It also includes the final repository-metadata, release automation, and delivery hardening completed after the fourth checkpoint.
- Add aligned English and Indonesian Docker and Compose guides.
- Update the README, badge catalog, developer hub, portal overview, and
- Add CI and Docker-validation badges without implying that public container
- Regenerate the concise project-structure reference and establish a clean
- Update the cumulative v1.0.0 commit and tag messages to include this fourth
- Complete documentation hubs for Custy, Path Header Scanner, Doc Gen, and Reflow.
- Provide English as the default locale and aligned Indonesian documentation for all four projects.
- Organize each project around appropriate getting-started, command, configuration, concept, workflow, architecture, user, developer, reference, and troubleshooting material.
- Preserve literal command names, flags, paths, configuration keys, output, and code identifiers when translation would weaken technical accuracy.
- Replace duplicated guidance with focused canonical pages and clear cross-references.
- Apply consistent heading, sidebar, category, navigation, troubleshooting, and related-page patterns throughout the portal.
- Document source, editable, private GitLab package-registry, and container installation paths with credential-safe examples.
- Explain exact prerelease images and the stable Docker alias lifecycle for
v<major>.<minor>.<patch>,v<major>.<minor>,v<major>, andlatest. - Add aligned English and Indonesian developer-hub pages.
- Add documented release versions to both project-overview tables.
- Synchronize the portal guide with Custy v2.1.1, Path Header Scanner v1.0.0,
- Preserve literal project names, commands, paths, and technical terms where
- Explain preview, dry-run, confirmation, and mutation boundaries where they
- Centralize project versions, release URLs, source-review dates, status routes,
- Support automatic SemVer and PEP 440 tag discovery with prerelease filtering,
- Keep notices hidden for current documentation and show actionable states for
- Cover the freshness resolver with focused automated tests.
- Doc Gen: v1.0.0.
- Reflow: v1.0.0.
- Added shared portal introductions, project discovery, navigation, badges, and
- Completed the most comprehensive documentation implementation for Custy,
- Added a complete Indonesian Custy documentation set while retaining English
- Documented experimental or incomplete behavior with visible status and
- Added project-level documentation baseline metadata, release links, review
- Added manual and automatic freshness modes for maintainers.
- Added build-time remote tag discovery with SemVer and PEP 440 parsing,
- Added a version-status notice that remains hidden for current documentation
- Added focused tests for remote tag parsing, version comparison, and freshness
- Integrate reusable React components across every project documentation set as needed.
- Provide common command heroes, metadata, syntax, option, output, example, requirement, feature, workflow, terminal, screenshot, table, architecture, Mermaid, status, and navigation components.
- Maintain shared type definitions, responsive styling, theme variables, dark-mode behavior, copy interactions, and accessible visual hierarchy.
- Handle unavailable or planned screenshot assets gracefully so missing images do not break documentation pages.
- Present one responsive 16:9 application preview on every project landing page and homepage card.
- Provide overview and compact card screenshot variants with accessible fallback content and uncropped terminal output.
- Detect cached image failures after hydration so missing preview assets never degrade into broken-image UI.
- Keep component usage proportional to the information being presented instead of forcing identical layouts onto unrelated content.
- Configure English and Bahasa Indonesia as fully supported documentation locales.
- Add stable sidebar and category translation keys to prevent locale extraction conflicts.
- Translate shared UI strings while retaining technical terminology where appropriate.
- Align developer setup, contribution, pre-commit, testing, and safety guidance across both locales for every documented project.
- Provide consistent project discovery, homepage cards, navigation, footer links, breadcrumbs, page hierarchy, and related-content pathways.
- Provide a dedicated bilingual developer hub that connects contributors to each project's developer guide, architecture, and the portal maintainer workflow.
- Register the developer hub in the curated root sidebar so it opens with consistent navigation and pagination context.
- Add English and Indonesian documentation for maintaining the Devalltect Docs portal itself.
- Complete Indonesian counterparts for the portal introduction and project overview.
- Redirect the documentation root to the portal homepage instead of exposing a not-found route.
- Apply a coherent color system, typography, spacing, status language, terminal presentation, and mobile-responsive behavior.
- Centralize documented project versions, release URLs, review dates, status routes, and repository metadata.
- Support automatic remote tag discovery through
git ls-remote --tags --refs. - Parse and sort supported SemVer and PEP 440 tags with optional prerelease filtering.
- Support manual freshness status for inaccessible repositories or unsupported tag formats.
- Distinguish current, outdated, preview, and unknown documentation states.
- Keep the notice hidden for current documentation and display actionable status only when reader attention is required.
- Add timeouts, diagnostics, safe fallbacks, and automated freshness resolver tests.
- Document consistent PNG names and recommend crisp, credential-safe 1600 × 900
- Keep command names, paths, and configuration identifiers literal across
- Validate documentation freshness, TypeScript, pre-commit, multilingual builds,
- Document Path Header Scanner v1.0.1 with SemVer freshness detection.
- Document Custy v2.1.2 with SemVer freshness detection and cross-project workflow guidance.
- Record source-review dates and release-specific status pages for maintainers and readers.
- Replace the starter homepage with a project-oriented Devalltect documentation landing page.
- Generate homepage project cards from centralized project metadata.
- Centralize project-preview paths, alternative text, fallback descriptions, and project-specific technology badges.
- Consolidate overlapping documentation-model sections into one goal-oriented discovery guide.
- Replace ambiguous audience labels and destinations with accurate tool-use and developer-contribution paths.
- Add direct navigation to each tool and a dedicated bilingual developer hub.
- Keep technology badges concise, project-specific, and representative rather than listing every maintenance dependency.
- Add a maintainer workflow covering content review, localization, screenshots, validation, freshness, and release preparation.
- Resolve homepage image assets through the configured base path for reliable subpath deployment.
- Use explicit light- and dark-background Devalltect logo assets in the navbar and homepage through native Docusaurus theme switching.
- Document component and freshness configuration for future maintainers.
- Keep project-specific content independent while sharing stable UI and documentation conventions.
- Add concise repository structure, contribution, badge, security, and maintenance guidance.
- Mark the portal package as the stable private v1.0.0 workspace.
- Add a clear package description, searchable keywords, repository, homepage, issue tracker, license, author, and maintainer metadata.
- Keep independently maintained GitHub and GitLab topic sets under the
- Add a dependency-free Node.js helper that validates provider-specific Git
- Provide provider selection, a non-mutating metadata dry-run, target and
- Move public support metadata to a dedicated project contact while keeping
- Keep Yarn 4.18.0 as the package manager and
yarn.lockas the dependency source of truth. - Retain Node.js 20+ compatibility, TypeScript validation, Docusaurus development commands, multilingual builds, and freshness tests.
- Add optional multi-stage Docker and Compose workflows for live development,
- Replace the npm-oriented Makefile with categorized Node.js, Yarn, Docker,
- Keep Make help portable across Windows and Linux containers, and regenerate
- Establish a clean repository-wide Prettier baseline for deterministic local
- Repair the pre-commit Prettier file matcher and formatter configuration so repository hooks parse and run reliably.
- Keep the Devalltect GitHub Pages URL and repository path as the default while
- Deploy through GitHub Pages with the Node.js 24-compatible configuration
- Wait for production-preview containers to report healthy before smoke tests,
- Publish GitLab Pages directly from
build/throughpages.publish, restrict - Resolve GitLab project paths and unique-domain roots from
CI_PAGES_URL, with - Build and smoke-test development and production container targets in GitHub
- Keep Docker optional and preserve direct static-file delivery through both
- Validate locale-aware routes, links, anchors, MDX rendering, static generation, and TypeScript integration.
- Preserve build-time fallback behavior when a remote documentation freshness check is unavailable.
- Standardize the Doc Gen project-structure output on the lowercase tracked
- Add regression coverage for generated-artifact casing, configuration, links,
- Make generated-artifact regression checks context-aware so Docker validation
- Validate annotated Semantic Version tags, preserve their complete messages as
- Generate clear alpha, beta, release-candidate, prerelease, and stable Release
- Allow repeatable GitHub Release creation for pushed or manually selected tags
- Configured Docusaurus for the Devalltect GitHub Pages project URL and base
- Added GitHub Actions deployment for static GitHub Pages publishing.
- Added GitLab CI and Pages definitions for validation and mirrored deployment.
- Repaired route and link issues required for production builds across the
- Added project structure, contribution, security, and repository-level
- Promote directly to the first stable release without publishing the abandoned alpha templates.
- Retain the alpha commit and tag message files only as historical planning references.
- Preserve four untagged v1.0.0 development checkpoints, followed by focused
- Confirm that all four final project-preview PNG files are present and
- Confirm that Custy, Path Header Scanner, Doc Gen, and Reflow documentation follow the shared quality baseline.
- Confirm that both supported locales are available and behaviorally aligned.
- Keep documentation freshness and component APIs documented for continued maintenance.
- Confirm GitHub Pages, GitLab Pages, and container smoke tests against their
- Review repository-metadata dry-run targets before applying provider updates.
- Confirm that the final annotated tag message and generated Release Information
- Add dependency, development, validation, builder, and production Docker
- Run formatting checks, documentation-freshness tests, TypeScript validation,
- Serve the immutable production build through Nginx at the configured
- Redirect the container root to the portal base path and provide a dedicated
- Keep generated output, host dependencies, caches, logs, Git metadata, and
- Add shared, development, and production Compose definitions.
- Provide live reload on port 3000 with host source mounted separately from a
- Provide an immutable Nginx production preview on port 8080 without mounting
- Expose focused services for freshness tests, formatting checks, type checking,
- Replace the npm-oriented monolithic Makefile with focused Node.js and
- Use the checked-in Yarn release consistently for dependency installation,
- Add categorized and counted help for local, Docker, Compose, cleanup, and CI
- Keep the modular help output portable across Windows hosts and Linux
- Exclude Python packaging, registry publishing, remote runtime, and Git release
- Add GitHub and GitLab container validation that builds the validation and
- Keep all container validation non-publishing: no registry authentication,
- Expand source CI with formatting and documentation-freshness tests before
- Preserve direct GitHub Pages and GitLab Pages publication of static build
- Validate immutable dependency installation and the pinned Yarn runtime.
- Run formatting, freshness, TypeScript, and bilingual production checks.
- Validate categorized Make help and representative non-mutating dry-runs.
- Validate Docker and Compose configuration, development and production image
- Validate TypeScript and documentation-freshness behavior.
- Build English and Indonesian production documentation.
- Check MDX routes, internal links, homepage rendering, responsive cards, and
- Consolidate the overlapping documentation-category and documentation-tree
- Present getting started, commands and configuration, concepts and
- Explain that projects share navigation conventions without claiming that
- Remove hover behavior from informational cards so they no longer imply an
- Remove the superseded DocumentationModel component and stylesheet instead of
- Replace ambiguous Users and Developers labels with the task-oriented
- Keep the tool path connected to the project directory.
- Add an English and Indonesian developer hub with direct project developer
- Register the developer hub in the curated root sidebar immediately after the
- Point the developer homepage action to that dedicated hub instead of the
- Expand homepage technology badges with representative runtime technologies
- Add Rich and Docker where they describe the delivered CLI experience.
- Identify Reflow's GitHub CLI integration and Custy's Jinja2 and Commitizen
- Keep the project cards readable by treating their badges as curated summaries
- Replace transformation-oriented logo filenames with explicit
on-lightand - Configure the navbar to select the correct logo through Docusaurus
srcDark - Render the homepage logo through Docusaurus's native themed-image component
- Keep the light-background variant as the temporary social preview image until
- Reuse the shared screenshot component for Custy, Path Header Scanner,
- Add overview and compact card presentation variants with consistent 16:9
- Reserve stable asset paths under
static/img/project-previews/so final PNG - Keep missing preview assets non-breaking during preparation while requiring
- Detect image failures that occur before client hydration so cached missing
- Display project previews directly in the existing homepage cards instead of
- Add typed preview metadata with asset paths, alternative text, and fallback
- Replace identical technology badges with concise project-specific runtime and
- Preserve responsive card behavior, readable terminal images, lazy loading,
- Resolve the homepage hero logo through the configured Docusaurus base path so
- Add a dedicated Devalltect Docs documentation hub in English and Indonesian.
- Explain supported projects, portal organization, localization, source review,
- Add the portal guide to the sidebar and homepage maintainer navigation.
- Correct outdated root-page language coverage and add the missing Indonesian
- Apply the reusable React documentation component system across project pages.
- Keep command, terminal, workflow, screenshot, table, architecture, status,
- Align page hierarchy, colors, typography, dark mode, spacing, terminology,
- Preserve literal command names, flags, paths, configuration keys, output, and
- Maintain the portal with Docusaurus, React, TypeScript, Yarn, and Node.js 20+.
- Validate multilingual routes, links, anchors, MDX rendering, static output,
- Support GitHub Pages delivery and mirrored GitLab CI/Pages validation.
- Align contributor setup, pre-commit, testing, and release guidance across
- Added reusable common layout, badge, card, grid, heading, section, tag, and
- Added command-focused heroes, syntax, options, outputs, examples, metadata,
- Added requirement, feature, workflow, terminal, screenshot, comparison,
- Added shared styling, theme variables, responsive layouts, dark-mode support,
- Added graceful screenshot handling so planned assets do not break pages when
- Integrated the component system throughout the Custy documentation while
- Configured English as the default locale and Indonesian as the secondary
- Added translated Custy pages, sidebar metadata, navigation, footer content,
- Preserved command names, flags, paths, configuration keys, and technical
- Added stable category and sidebar translation keys to prevent localization
- Added a route for the documentation root so /docs redirects to the portal
- Added a custom homepage with project discovery, audience guidance,
- Added centralized project data used by the homepage and documentation
- Added consistent documentation presentation, color themes, typography,
- Added internal component guidance and configuration comments for future
- Migrated package management and project commands to Yarn with an immutable
- Fixed TypeScript compatibility issues across reusable components and shared
- Added type-checking, locale-aware development, and production-build scripts.
- Verified the English and Indonesian development servers during implementation.
- Verified TypeScript checks and multilingual production builds after migration
- Added automated tests for the documentation freshness plugin.
- Retained clear fallback behavior when remote version checks cannot complete.
- This is the first public prerelease of the documentation portal.
- Custy has the strongest component integration and English/Indonesian coverage.
- Path Header Scanner, Doc Gen, and Reflow documentation remain available but
- Navigation, component APIs, page organization, and freshness configuration may
- Documentation should be reviewed against each source project before treating
Tags
release • docs • ci • build • stable • portal
Release Alpha
- Added documentation roots for Custy, Path Header Scanner, Doc Gen, and Reflow.
- Added shared portal introductions, project discovery, navigation, badges, and
- Organized project material into command, configuration, architecture,
- Completed the most comprehensive documentation implementation for Custy,
- Added a complete Indonesian Custy documentation set while retaining English
- Documented experimental or incomplete behavior with visible status and
- Added project-level documentation baseline metadata, release links, review
- Added manual and automatic freshness modes for maintainers.
- Added build-time remote tag discovery with SemVer and PEP 440 parsing,
- Added a version-status notice that remains hidden for current documentation
- Added focused tests for remote tag parsing, version comparison, and freshness
- Added reusable common layout, badge, card, grid, heading, section, tag, and
- Added command-focused heroes, syntax, options, outputs, examples, metadata,
- Added requirement, feature, workflow, terminal, screenshot, comparison,
- Added shared styling, theme variables, responsive layouts, dark-mode support,
- Added graceful screenshot handling so planned assets do not break pages when
- Integrated the component system throughout the Custy documentation while
- Configured English as the default locale and Indonesian as the secondary
- Added translated Custy pages, sidebar metadata, navigation, footer content,
- Preserved command names, flags, paths, configuration keys, and technical
- Added stable category and sidebar translation keys to prevent localization
- Added a route for the documentation root so /docs redirects to the portal
- Added a custom homepage with project discovery, audience guidance,
- Added centralized project data used by the homepage and documentation
- Added consistent documentation presentation, color themes, typography,
- Added internal component guidance and configuration comments for future
- Migrated package management and project commands to Yarn with an immutable
- Fixed TypeScript compatibility issues across reusable components and shared
- Added type-checking, locale-aware development, and production-build scripts.
- Configured Docusaurus for the Devalltect GitHub Pages project URL and base
- Added GitHub Actions deployment for static GitHub Pages publishing.
- Added GitLab CI and Pages definitions for validation and mirrored deployment.
- Repaired route and link issues required for production builds across the
- Added project structure, contribution, security, and repository-level
- Verified the English and Indonesian development servers during implementation.
- Verified TypeScript checks and multilingual production builds after migration
- Added automated tests for the documentation freshness plugin.
- Retained clear fallback behavior when remote version checks cannot complete.
- This is the first public prerelease of the documentation portal.
- Custy has the strongest component integration and English/Indonesian coverage.
- Path Header Scanner, Doc Gen, and Reflow documentation remain available but
- Navigation, component APIs, page organization, and freshness configuration may
- Documentation should be reviewed against each source project before treating
Tags
release • docs • build • alpha