← Development guidelines

Release history

Technical changelog

What's new for users

Guideline content by Lucas Vitti, licensed under CC BY 4.0. See scope and attribution.

3.2.0 — 2026-10-25

Availability: Prepared on 2026-10-25; public availability is confirmed by the edition displayed at the live guidelines URL.

Adds an explicit CC BY 4.0 license for Lucas Vitti's licensable rights in the guideline prose, documentation templates, original explanatory examples and snippets, session instruction, and changelog narratives. Requests credit to Lucas Vitti linked to https://lucas.mat.br, alongside the source and license references and disclosure of modifications, in a reasonable format under the license. The scope excludes site implementation code, private workspace records, other applications, and separately owned material. Following these guidelines does not license an application. The official CC legal code remains unmodified.

Adds a license page and downloadable notice, linked attribution across all current document pages and standalone text, and content-specific license metadata in each manifest. The generator emits 18 files per edition. Verification checks the notice, linked author, official license URL, scoped metadata, and document consistency. Four templates, 87 rules, and 522 examples are retained. This edition includes the two-changelog workflow introduced in the locally prepared 3.1.0 edition. Earlier frozen editions and narratives retain their original files and dated state.

Lucas explicitly selected this license and authorized local preparation, validation, and publication through the existing restricted SFTP account only. No administrative SSH, remote shell, service changes, main-site deployment, or application edits are authorized. Publication evidence is recorded separately after it succeeds; this preparation entry does not claim an upload has already occurred. Version 3.2.0 adds reuse permission within the requested 3.x series without adding mandatory licensing rules for projects.

3.1.0 — 2026-10-25

Availability: Local preview only; not published as of 2026-10-25.

Revises DOC-08 to require two distinct, indexed changelogs for every version. The technical journal retains the full change narrative, source/artifact identity, approved plan, architecture and configuration effects, verification, compatibility, deployment, and recovery details. The user changelog explains practical capabilities, changed workflows, moved or renamed controls, removed pages, fixes, relevant limits or permissions, and required user actions. Both histories must agree on version, dates, facts, and actual availability. Internal-only releases retain a user entry stating that there are no user-visible changes; published history is preserved with explicit dated corrections.

Adds the user changelog template and this edition's separate user history. Updates the design, planning, and technical journal templates, documentation layout, completion criteria, and reusable AI-session instruction. The existing changelog destination stays available as Technical changelog; What's new for users opens a separate page. Both pages link back to the guide and to each other, work without JavaScript, and offer Markdown downloads. No nested tabs or new application screens are introduced.

The static generator now produces four templates and both histories: 16 files per edition including the manifest. It requires a single current version/date entry at the top of each history and matching recorded availability. Verification covers source/current/pinned history consistency, page navigation, template discovery, and complete manifest membership. All 87 rules retain three DOs and three DON'Ts, totaling 522 examples. DOC-08's six examples cover practical translations, pending availability, internal-only releases, moved/removed controls, and preserved history. No application runtime parameter, dependency, schema, or service changes are part of this edition.

Version 3.1.0 follows Lucas's explicit instruction to stay in the 3.x series. The new second-changelog requirement strengthens adoption obligations despite this owner-directed minor release. Existing projects agree on a starting version and record historical gaps; adoption does not authorize unrelated changes or invented backfills. Earlier frozen editions remain unchanged. The approved scope is local implementation and validation only; actual checks and artifact identity are recorded in the project's private technical journal. No publication or server access is authorized for this work.

3.0.0 — 2026-10-18

Adds DOC-09, a mandatory internal-parameter register during planning and documentation. Owners must be able to understand the limits, defaults, thresholds, durations, quotas, allowed values, and other hardcoded policies that determine behavior, including unnamed literals. Records explain purpose, exact values and units, scope, source and enforcement, configuration/override behavior, rationale and ownership, approval state, user effects, change consequences, and verification. Plans distinguish source defaults, effective environment values, and proposed changes; completion reconciles the register and journals actual parameter changes.

Extends the architecture/UX change-plan, project-design, version-journal, completion guidance, and AI-session instruction. Includes a fictional upload-limit record distinguishing bytes, MB, and MiB and checking interacting frontend, server, proxy, and storage constraints. This documentation requirement does not authorize increasing a limit or require making every constant configurable. Existing projects disclose reviewed scope and legacy gaps; audit-only work remains read-only.

The edition contains 87 rules, each with three DOs and three DON'Ts, totaling 522 examples. All earlier editions are preserved. Version 3.0.0 follows the existing major-version policy because the parameter inventory is a new mandatory adoption requirement; projects choose when to adopt it. No application parameter or Balde source is changed by this guideline release. Publication status is recorded separately in the project's release journal.

2.3.0 — 2026-10-18

Adds architecture rules ARCH-11 through ARCH-13: establish a baseline through one representative working feature, isolate external details behind justified narrow contracts, and version reusable starters. Strengthens ARCH-08 and ARCH-10 with public boundary contracts, data ownership, allowed and prohibited dependencies, executable dependency checks, runtime-coupling review, and evidence that implementation details can change without editing unrelated features. Short files and acyclic imports alone are not proof of sound architecture.

Adds DOC-07 and DOC-08 for a document-first workflow and a narrative journal for every project version. An architecture and UX plan must be saved, presented, and explicitly approved before implementation; material changes require renewed approval. Deployment requires authorization covering the release and target, which may be included in the same explicit approval. Existing approval for unchanged scope remains valid. Version journals explain actual additions, corrections, improvements, compatibility, verification, and deployment state, preserving prior narratives and explicit later corrections.

Strengthens DOC-01 and DOC-05 to keep design guides, plans, decisions, and journals in a dedicated, indexed documentation folder inside each project workspace. Extends the project design template and adds readable/downloadable change-plan and version-journal templates. Updates the session instruction and completion criteria. The edition contains 86 numbered rules and 516 examples, with three DOs and three DON'Ts for every rule. Existing examples are revised where the associated rule changed.

Released as the owner's explicitly requested minor version 2.3.0. Planning, approval, documentation, and boundary verification requirements are stronger, so projects must review and record adoption; this release does not imply existing applications comply or authorize their modification. Earlier frozen editions remain unchanged. The release manifest identifies the artifact; publication evidence is recorded separately and only verified publication may be called deployed.

2.2.0 — 2026-10-15

Adds a dedicated Modularization and code splitting section, with mandatory rules ARCH-07 through ARCH-10. Requires cohesive maintained source, a module-boundary plan, resolution of oversized touched files/functions, and explicit modularity evidence before completion. The house review thresholds are 300 nonblank, non-comment-only lines per file and 50 per function; extraction or a scoped documented exception is required. A smaller file with mixed responsibilities still fails review. Generated output is distinguished from maintained source, and staged adoption preserves the scope of narrow fixes and read-only audits.

Adds six examples to each new rule, a feature-layout example, and an illustrative ESLint review gate. The edition contains 81 numbered rules and 486 DO/DON'T examples. Extends the project design template and reusable AI-session instruction with module boundaries, size-review dispositions, dependency review, and verification evidence. Fixes navigation-number wrapping for long section titles.

Continues the owner's requested minor-version treatment. These mandatory checks strengthen the original modularization requirements, so adopters should review the enforcement changes before upgrading. Earlier editions remain unchanged.

2.1.0 — 2026-10-15

Adds UX-19 through UX-21 to prevent competing nested interaction layers across navigation, tabs, dialogs, scrolling, disclosure, and embedded workspaces. Distinguishes structural containment from duplicated control roles and requires clear separation of destinations, filters, view controls, and selection. Extends the project template with interaction hierarchy, task/scroll ownership, and depth-review fields.

Adds six concrete examples to every numbered rule: three DOs and three DON'Ts, totaling 462 examples across 77 rules. Examples appear in native expandable sections on the page and in full in the Markdown edition. They illustrate the existing scope and requirement levels rather than authorizing additional features.

Released as a minor version at the owner's explicit request. UX-19 and UX-20 add mandatory house rules, so adopters should review them before upgrading; existing work is not silently reclassified. Editions 1.0.0, 1.1.0, and 2.0.0 are preserved. This entry identifies the edition; publication status is verified separately.

2.0.0 — 2026-10-08

Adds mandatory rules UX-16 and UX-17 for one declared main intent per page/form and on-request presentation of separate secondary tasks. Adds UX-18 guidance for choosing pages, dialogs, side panels, and collapsed sections. Supporting controls such as search and filters remain part of the primary task.

Adds DOC-01 through DOC-06 for maintained project documentation covering code, architecture, page/form intent, UX patterns, significant decisions, and evidence. Includes a downloadable project design guide template with page/form and decision records plus illustrative client-list and registration examples. References Diátaxis, C4, and architecture decision records without requiring heavyweight documentation.

This is a major version because it introduces mandatory adoption requirements beyond 1.x. Existing projects adopt in stages within authorized work; audit-only reviews remain read-only. Existing rule IDs retain their meanings. Editions 1.0.0 and 1.1.0 are preserved. The new package is prepared locally, not deployed.

1.1.0 — 2026-10-08

Adds compatible visual-design recommendations VIS-01 through VIS-07: whole-screen coherence, figure and ground, similarity, proximity, continuity, closure, and common fate. Each includes concrete application, an example, and review criteria. Clarifies that closure does not justify hiding essential information and common fate does not require adding animation.

Adds an AI workflow and example brief for translating visual principles into verifiable interface decisions. Updates the session instruction to pin version 1.1.0 and makes the page navigation count follow its content. No existing mandatory requirements are changed. The frozen 1.0.0 edition is preserved. This package remains local and has not been deployed.

1.0.0 — 2026-09-29

Initial public-ready edition. Unifies human-manageable structure, readability, comments, contracts, ten application-security tenets, local development and IDE readiness, shared-VPS deployment, UX patterns, interaction scenarios, verification, audit findings, and exception handling.

Adds stable rule IDs, requirement levels, an AI-session instruction, immutable edition paths, and semantic-version adoption rules. Contains general guidance only; project audit findings and private infrastructure details are excluded.

This changelog records preparation of the release package. It does not assert that deployment has occurred.

Download technical changelog