Coro is a modular cybersecurity platform for small and mid-sized businesses. I was Director of Product & Corporate Marketing, and technical writing was one of the two functions I'd been hired to build. I've put the whole documentation site in one entry, because we built its parts as one system.
The artifact
docs.coro.net holds featured guides, the full product documentation, release notes for every version, FAQs, the compliance section, and the public API. Each section has a different reader. All of them use the same structure and the same words for the same things.
The compliance section mattered most commercially. It covers more than 20 global regulations, including GDPR, HIPAA, SOC 2, PCI DSS, ISO 27001, NIS2, SOX, FERPA, GLBA, CCPA and the state privacy laws, and maps each one to what the platform does. The entry page answers the three questions a buyer arrives with, which are what the regulation covers, who it applies to, and who enforces it. Each regulation then gets its own page, alongside a list of the sensitive data types Coro recognizes.
We built the developer portal from scratch, including the structure and the writing, ahead of the company's move to selling through partners and MSPs. It covers the endpoints, guides, changelog and full reference across the US, Canadian and German regions. It also explains the workspace model MSPs work in, where a channel workspace holds the partner's own data and creates a child workspace for each of their clients.
The featured guides are a separate task-based layer, split into getting started, how-tos and agent deployment. Product documentation is organized by product. Someone who needs to connect an account or deploy an agent today needs a different route through the same material.
Release notes run from version 1.3 to the current release, with separate lines for the console and for MDM. Coro is still publishing them in the structure I set, most recently in August 2026.
Why
In security, the documentation is where trust is won or lost. Buyers read it long before they talk to sales. I wrote the compliance section for someone who hasn't contacted us yet.
