PureXxx

TODO: Add badges

TODO: Short description of PureXxx

Why PureXxx ?

TODO: Explain the motivation for PureXxx

PureXxx in the PureFramework

TODO: Mermaid diagram showing the location and dependencies of this library in the PureFramework ecosystem.

Quick Start

TODO: Installation and ultra-simple example following best practices.

Advanced documentation

API TODO: Add the complete documentation of the library API. Best practices TODO: Complete best practices to be followed by human users and AI agents. Examples TODO: Add examples illustrating best practices.

Contributing

Contributions are welcome.

Mandatory branch naming

Branch prefixes are required and define the semantic impact of the change:

• upgrade/ → breaking changes (major version)
• us/ → new features (minor version)
• fix/ → bug fixes (patch version)

Why not Conventional Commits?

Versioning information belongs to the branch, not individual commits.

Branches express intent and scope. Commits should stay frequent, descriptive, and free of artificial prefixes that often degrade into wip: or chore: without semantic value.

License

This project is licensed under the Mozilla Public License 2.0 (MPL-2.0).

Author

Gilles Coudert

• Email: pure.framework@gmail.com
• GitHub: https://github.com/GillesCoudert

Links