Contributing and project information

A useful contribution can begin with a mathematical question, an unclear explanation, or a small example whose answer seems wrong. The contribution guide explains how to report a problem, set up a checkout and propose a change. Use it for the shared procedure, then consult the guidance for the work you are doing.

Write and organize documentation

The writing guide explains article purposes, approachable exposition and the relationship between the learning routes and topic map. The site build guide covers publication and rendered review. Maintain article identities and subject links through the article inventory; use the API inventory guide for public-binding coverage and reference review.

Check a change

The testing guide helps select mathematical, package and integration checks and explains the evidence each provides. Live inspector changes also use the browser guide, which keeps native checks and actual frontend acceptance distinct.

For performance work, begin with the benchmarking manual and comparison-suite guide. They define equivalent requests, timing conditions, correctness checks and a bounded study. The benchmark style guide governs presentation of the resulting evidence; completed reports show its use.

Release and credit the work

The release guide covers candidate verification, registration and tagging. The changelog records package changes.

The citation record credits Erik Novak as the software author and explains how to identify the version or commit used in research. The repository contributor history records contributions to tracked files. Mathematical and software sources are credited where their ideas are used, including the implementation bibliography.