WordPress & YOOtheme Pro
WooCommerce Development
Website Planning
Website Ownership & Access
Website Support & Growth
Website Launch ChecklistOps-Box: Product Website and Platform UI for a DevOps Platform
A product website and the user interface of the platform itself for Ops-Box, a unified DevOps management platform. Built from scratch, from the domain to two release environments, with content, code, and deployments kept entirely in GitHub.
Ops-Box Project at a Glance
Client
The author of Ops-Box, a DevOps platform for infrastructure, pipelines, and access.
Scope
Domain, product website, platform UI, staging and production environments, release automation.
Stack
Astro, GitHub, automated deployments to staging and production.
Scale
84 pages: 8 platform pages, a 68-page technical handbook, team, academy, and legal pages.
What the Ops-Box Project Required
Ops-Box is a large product: one platform for infrastructure as code, CI/CD pipelines, Kubernetes access and environments, scheduled jobs, and cluster health. The website had to explain each module clearly to engineers and their managers, and grow into a full technical handbook.
The client wanted everything in GitHub: the code, the content, and the history of every change. That requirement decided the technology. Instead of WordPress, the site is built with Astro, so every page lives in the repository and every update goes through a review before it reaches visitors.
What I Built for Ops-Box
The product website
Home page, a platform overview, and a page for each module: IDP, infrastructure as code, CI/CD, Kubernetes RBAC, Kubernetes environments, CronJobs, and cluster health.
The handbook
A technical handbook of 68 pages, organized in chapters, that answers the questions engineers ask before adopting a platform.
The platform UI
The interface of the Ops-Box panel itself, not only the marketing site around it.
The infrastructure
Domain, hosting, and two environments: staging for review and production for visitors.
How Ops-Box Releases Reach Production
1. Merge to main
An approved change merged into the main branch is deployed to staging automatically.
2. Review on staging
The change is checked on staging exactly as visitors will see it.
3. Tag a version
Creating a version tag deploys that exact release to production.
Nothing reaches the live site without passing through staging, and every release can be traced to a tagged version in GitHub.
Ops-Box Website Performance, Measured
| Lighthouse category | Desktop | Mobile |
|---|---|---|
| Performance | 100 | 74 |
| Accessibility | 96 | 96 |
| Best practices | 100 | 100 |
| SEO | 100 | 100 |
Ops-Box Website Screens
Home page
The platform explained in one screen, with an interactive before-and-after view.
Module page
Each module starts with the problem it solves, here CI/CD pipelines.
Handbook article
A chapter of the technical handbook, written by the platform’s founder.