Contributing

Set up framework development, understand the architecture, and find backend contracts and design records.

• Developing Day and an app together

  Build an app against a local day checkout with day patch, and the workflow for changing a framework crate and the app that demonstrates it in the same sitting.

• The extension model

  How new widgets and capabilities plug into Day as ordinary crates: composite pieces, native pieces, parts, and the registration machinery.

• Architecture

  The crate graph, one-binary-per-target compilation, and how the CLI and platform build systems cooperate.

• How rendering works

  Following a widget through the system: mounting, the realized tree, patches, events, the turn, and the mock toolkit.

• Contributing to Day

  Day is a young project. Its architecture is still moving, and the most useful contribution right now is a conversation, not a patch.

• Backend contracts

  Implementation contracts, generated coverage tables, and framework testing records.

• Design records

  Proposals, resolved decisions, and historical implementation plans. These records are not stable API reference.

• History

  Retained migration and implementation history.

• Contributor tutorials

  Learn to create composite pieces, native pieces, and parts.

• Documentation authoring

  The canonical style guide, terminology, authoring workflow, and validation commands.

The repository’s DESIGN.md remains the architectural authority. It includes proposals and historical sections; consult their status before treating them as implemented contracts.