Performance within the agreed implementation
We review generated pages, assets, and interactive components, then validate the performance targets your project requires. A framework choice alone does not establish those results.
Documentation engineering - Astro Starlight services
Setup, custom theming, and migrations for Astro Starlight, the fast, modern documentation framework. We build branded, searchable, AI-ready Starlight sites, and validate the agreed URL mappings and redirects when moving teams onto Starlight.
When Starlight fits the workflow
Starlight can fit a team that wants Astro-based documentation with Markdown/MDX content and scoped custom components. We assess publishing, versioning, integration, and maintenance requirements before selecting it.
Built-in Pagefind search
Fully static, privacy-friendly search ships in the box, no Algolia account, no external service, no per-query cost. We tune it for your content and structure.
First-class i18n
Multi-language documentation is a core Starlight feature, not a bolted-on plugin. We set up locale routing, translated navigation, and fallbacks properly.
Our Starlight services
Set up Starlight and brand it via Astro component overrides and design tokens, a custom look that stays on the upgrade path.
Move from Docusaurus, GitBook, or MkDocs, content, components, search, and a full redirect map so existing links keep working.
Build interactive Astro islands and custom components, API explorers, callouts, embeds, without bloating the page.
Automated builds, preview deploys, OpenAPI-driven reference generation, and quality checks for your Starlight docs.
Agree capacity for dependency reviews, compatibility checks, issue investigation, and selected improvements.
Architecture guidance and team training for Astro/Starlight documentation workflows and Docs-as-Code.
Modern docs sites we’ve engineered
Explore custom themes, search, and publishing workflows built on Docusaurus and Sphinx.
Coiled
A developer-first documentation site with custom components and automated deployment for a cloud-computing platform.
- Custom components
- Automated deployment
- Developer-first
Voxel51
A custom Sphinx theme with Algolia search and a feedback widget. The published case reports that users found information 3x faster.
- Custom theme
- Advanced search
- Algolia DocSearch
Starlight, done by docs engineers
We combine Astro/front-end development with a decade of documentation engineering, so your Starlight site isn’t just set up, it’s architected to scale, stay fast, and stay maintainable.
Astro component theming
We use component overrides and design tokens, document the customizations, and check compatibility with the agreed framework version.
URL mapping and launch validation
We scope content and component conversion, inventory the agreed source URLs, and validate destination links and redirects before launch.
Performance & AI-readiness
Review rendering and indexable content for your selected consumers. Markdown exports, agent access, and query evaluation can be scoped where the use case requires them.
Commonly asked questions about our Starlight services
Starlight is Astro’s documentation framework, with Markdown/MDX authoring, Pagefind search, internationalization, and dark mode. We assess it against your content, custom components, contribution workflow, and publishing requirements. Performance depends on the implementation, assets, integrations, and hosting, and is validated against the agreed scope.
We assess the source content and components, then scope conversion, navigation, search, and redirect mapping. Existing React components may be adapted through Astro integrations or replaced with reviewed equivalents. Redirect implementation depends on access to the old domains and hosting configuration.
Starlight supports named component overrides, custom CSS, and Astro components. We scope branded navigation and reading components using those extension points, document dependencies, and test compatibility for the target version. Future upgrades still need review.
i18n is built in and first-class. Versioned documentation is handled via community plugins or a build-time strategy we set up per your needs, we’ll advise on whether true versioning is worth the maintenance cost for your project or whether a simpler approach fits better.
Yes, we integrate OpenAPI-driven reference (via Starlight OpenAPI plugins or a generated pipeline) so your API docs stay in sync with the spec, alongside your guides. This is the same "define once, generate everything else" approach we bring to every reference project.
Static HTML can support crawlability, but AI retrieval and answer quality also depend on content coverage, indexing, access, and the consuming tool. We can scope representative query evaluation and implement selected structure, export, or access improvements.
From our blog
Practical guidance on faster builds and reliable publishing.
How to make your docs discoverable to AI
Almost half of docs traffic is now AI crawlers. The 90% that matters: crawlable-without-JS, allowed in robots.txt, and ranking for real questions.
Take back control of your documentation
Your docs are a business asset, own them like one. Docs-as-code in Git ends vendor lock-in and export limits.
Slow builds were killing our docs
A 30-minute Sphinx build cut to under 5 minutes by splitting the PDF and parallelizing, and why build speed decides whether writers iterate.
Building, or moving to, Starlight?
Share your current platform and the Starlight setup or migration you have in mind. We will help you compare the options and identify what to tackle first.