Start with a concrete case
A useful contribution begins with an artifact or workflow the current model cannot describe clearly. Show a minimal document, the intended meaning and the ambiguity or failure you observed. Distinguish a specification issue from a validator or site defect.
The repository is github.com/gfrancodev/visualspec. Visual Spec is created and maintained by Gustavo Franco. Its current governance is maintainer-led and its 1.0 implementation is a release candidate.
Choose the right path
- Fix spelling, links and explanatory examples with a focused pull request.
- Report defects with a minimal reproduction and the relevant version.
- Propose normative changes, new profiles or compatibility changes through an RFC.
- Contribute adapter evidence with an explicit capability list and reproducible tests.
Do not include private source documents, credentials or assets you cannot redistribute. Small synthetic examples are often better reproductions than complete production designs.
Work locally
npm install
npm test
npm run build
For schema or validator changes, add a positive example and a negative case that fails for the intended reason. For site changes, check navigation, keyboard operation and narrow-screen layout. Update generated artifacts when their authoritative inputs change.
What a review needs
Explain the problem, final behavior, compatibility impact and verification. Link the issue or RFC when applicable. A proposed behavior remains proposed until accepted and implemented; do not describe an unimplemented adapter as supported.
Read the repository's CONTRIBUTING.md and GOVERNANCE.md for the complete process.