Hyland’s product documentation lived as static PDFs you opened in the browser. I redesigned it into the interactive, maintained documentation site Hyland uses today.
The team wanted ideas that would boost impact. My answer was simple: start with the problem they had right then — the docs.
From a scattered stack to an organized, maintained system
The problem they had now
In 2025, the docs were static PDFs viewed in the browser. Not interactive, scattered, and often out of date — hell on wheels for internal teams and customers alike.
Nobody trusted them, so people worked around them — which made them drift further out of date. The fastest way to boost impact wasn’t a new feature. It was fixing the thing everyone already relied on and nobody could stand.
Where it came from
The approach grew out of experimenting with FlutterFlow, and a lot of time spent living in the docs myself. I’d been deep enough in them to feel exactly where they failed.
The result is the interactive documentation site Hyland uses today — the same one that hosts product docs like the OnBase Integration for Esri.
Start with the problem they have now.