VidArch Docs
Developers

Contribute

Prepare a clear branch and pull request.

  1. Create a fork or a working branch;
  2. Install the dependencies;
  3. Develop in strict TypeScript and respect the existing style;
  4. Add or adapt the tests;
  5. Run the validation;
  6. Open a targeted pull request.

Use explicit commits, for example feat:, fix:, docs: or test:. The pull request description must explain the problem, the solution, the risks, and the verifications actually performed.

Never add node_modules, data/, downloads/, cookies, a real database, or personal media. Prefer minimal and free fixtures for tests and demonstration.

Keep interface changes specific to VidArch clean: a familiar convention is welcome, but the identity, archiving states, and components must remain consistent with the product.