Vitte

Suggestions Vitte

Short tracks for choosing what to read, what to test, what to fix, and what to publish first.

Welcome Documentation Download Source Community News Diagnostics Suggestions

Read

Test

Debug

Contribute

Release

Example

# Start with a single action
make quickstart-check

# Then narrow to a failing diagnostic or a documentation update

Use this pattern to keep changes small and reviewable: one main action before branching to a deeper follow-up.

Simple rule: only one main action per block, then we refine only if the context requires it.

How to choose

When the project feels busy, pick the smallest block that moves the work forward. If you need to understand a feature, start with Documentation. If you need to prove the behavior, go to Diagnostics. If you need the current implementation, open Source. If you need the latest project context, read News. The suggestion page exists to keep the next action obvious.

The general order is stable:

  1. Read the page that describes the rule.
  2. Check the implementation or the error path that enforces it.
  3. Run the smallest test that can confirm the behavior.
  4. Only then broaden the change to docs, examples, or release notes.

Suggestion list

  • Read : Open Documentation for the current feature or rule.
  • Inspect : Open Source and follow the implementation path.
  • Verify : Open Diagnostics and match the error message before fixing.
  • Test : Use a focused command like make quickstart-check or a targeted test file.
  • Document : Add an example or explanation to the HTML page when the behavior is not obvious.
  • Release : Update News or migration notes only after the change is confirmed.

This keeps the work easy to review and easy to explain. It also keeps the repository honest: every suggestion should point toward a concrete artifact, not just a vague intention.