docs
Ink Documentation
The Ink docs site: Next.js, Nextra, and careful tooling
An advanced documentation platform built with Nextra on Next.js for InkChain, still on the Pages Router, with a shelf of quality tools and automated checks wired into every pull request.
Pages Router, on purpose
The documentation app runs on Nextra, a framework for docs sites built on Next.js, and it uses the Pages Router for navigation and routing. The App Router upgrade has not happened, and the README is candid about why: compatibility limitations. For a docs site, staying a step behind the newest router is usually the boring, correct call. The repo's primary language is MDX.
The tool shelf
CSpell handles real time spell checking. Remark processes and renders the Markdown content, with plugins. ESLint catches code issues, Prettier keeps formatting consistent, and Tailwind CSS handles the responsive UI. None of it is exotic; the value is that all of it is present and configured, which is more than most documentation repositories can claim.
Checks on every pull request
The CI and CD pipeline uses GitHub Actions to run automated checks on every pull request. For a documentation project, that means spelling, linting, and formatting problems get caught before they land, rather than accumulating quietly across hundreds of merged edits. Anyone who has tried to fix a docs site where every page follows a slightly different convention will recognize how much friction this removes.
What ships at the end
The built site is the Ink documentation, describing itself as an advanced, streamlined platform built specifically for InkChain, and it serves from docs.inkonchain.com. Around 36,500 stars on a docs repository says the underlying project has an audience that actually reads.
Editorial conclusion
As documentation infrastructure goes, this is a tidy template: one framework, a handful of enforced conventions, and a gate on every change.
Community notes