Second Front Systems · Documentation Platform Owner / Lead Technical Writer

From fragmented documentation to an AI-native documentation platform

Overview

When I joined Second Front, documentation was spread across outdated websites, duplicated content, and disconnected repositories maintained by different teams. Customers struggled to find reliable onboarding guidance, implementation teams lacked a consistent source of truth, and Product needed better visibility into the gaps between platform capabilities and customer expectations.

I took ownership of bringing these pieces together. What started as a documentation overhaul evolved into designing and independently building an entirely new documentation platform from scratch.

The platform brought together the flexibility of a self-hosted solution with capabilities typically found in commercial documentation products. It supported private documentation, API references, versioning, offline deliverables, and AI-native documentation workflows, while meeting the deployment requirements of restricted government environments.

This wasn't just a documentation migration. It was an opportunity to rethink how documentation was created, delivered, maintained, and consumed by both people and AI systems.

Project at a glance

AreaDetails
RoleDocumentation Platform Owner / Lead Technical Writer
PlatformDesigned and built from scratch
TechnologyNext.js, React, TypeScript
Legacy content2 repositories, approximately 150 Markdown files
ContributorsApproximately 5 occasional contributors
Audience100+ customers
Deployment contextsDoW IL2/IL4/IL5/IL6, DIU, FedRAMP Class B/C/D, GovRAMP, and other restricted environments
AuthenticationNextAuth.js, Keycloak OIDC
DeploymentDocker, Helm, Harbor Registry
ScopeStrategy, content, product requirements, architecture, development, deployment, and ongoing operations

01. The challenge: Documentation without ownership

I inherited two documentation repositories: one for the Game Warden platform and another for the Game Warden web application. Together, they contained approximately 150 Markdown files.

Around five people had contributed information over time, but there was no consistent process for reviewing, validating, or maintaining it. Content had accumulated without clear ownership, resulting in duplicated, outdated, and sometimes confusing documentation.

The problems extended beyond the content itself.

Fragmented customer information

  • Multiple customer-facing documentation sites contained outdated and duplicated information.
  • Content had been assembled by different contributors without consistent editorial standards or information architecture.
  • Customers had difficulty finding reliable information to onboard and operate the platform.

Outdated documentation infrastructure

  • The existing MkDocs setup was built on an outdated technology stack.
  • The infrastructure had no clear owner or roadmap.
  • Extending the existing setup would mean continuing to work around limitations rather than building the capabilities we needed.

Cross-functional misalignment

  • Implementation teams struggled to guide customers through onboarding and mission-critical accreditation requirements.
  • Product teams needed better visibility into platform limitations and the gap between product capabilities and customer expectations.
  • Teams needed a more consistent understanding of what the platform could actually deliver.

Complex deployment requirements

Documentation needed to support hundreds of customers across commercial and government environments.

The challenge was to establish a reliable source of truth while building infrastructure capable of supporting the security, operational, and customer experience requirements of the business.

What this project demonstrates

This project reflects how I approach documentation as a product and take ownership beyond the boundaries of traditional technical writing.

  • Product thinking: Identifying infrastructure gaps, translating operational needs into product requirements, and prioritizing capabilities.
  • Independent product development: Designing and building a complete documentation platform from scratch.
  • Technical depth: Working across application architecture, authentication, deployment, containerization, and vulnerability management.
  • Customer experience: Making complex product and compliance information easier to discover, understand, and access.
  • AI readiness: Building documentation workflows and platform capabilities for both human and machine consumption.
  • Long-term ownership: Continuing to develop, maintain, and improve the platform as product and customer needs evolve.