Continued development on the tool behind the BiPRO standards

The documentation tool is not a side product, it is the workbench of the standardisation work: standards are drafted, versioned, reviewed and published to members there. So it had to keep growing without stalling the committee work already in flight. A greenfield rebuild was off the table; the job was work inside the existing system and its existing release rhythm.

We worked our way into the existing code and developed it further where that paid off, rather than rewriting it. New features arrived incrementally and in step with the committees, alongside tidied-up interfaces, tests at the critical points and automated builds so a release stops being an event. Built in TypeScript and React on a Node.js and PostgreSQL base, shipped containerised.

The tool kept pace with the standards work instead of slowing it down. Changes are traceable, the state of things is documented, and it can be handed back to the internal team at any time without knowledge staying with us.