Skip to content

Services

Available when the template is the starting point, not the finish line. Each service solves a specific problem.

Headless CMS Integration

Headless CMS Integration

Decap, Sveltia, Tina, or custom Git dashboard for your JAMstack project.

Modern Documentation Website

Modern Documentation Website

Full documentation site with Starlight, Docusaurus, or custom stack.

Custom Web App

Custom Web App

POS, online store, inventory, dashboards — JAMstack architecture.

AI Solutions

AI Solutions

Private AI for finance automation and autoblog SEO engines.

Building a documentation site is not just about the template. It is about the setup, the integration, the customization, and sometimes the parts that go beyond the template itself. Astro Docus is designed to be complete — but there are situations where additional help makes the difference between a project that launches smoothly and one that drags on for weeks.

This section covers the services available for Astro Docus users. Each is described honestly — what it does, who it is for, and why it might be worth it for your specific situation.


Astro Docus is a full template. You can install it, configure it, and deploy it yourself. Many users do exactly that — and the documentation you are reading right now is designed to support that path.

But some projects need more than a template. Some need:

  • A CMS integrated into the template so non-technical editors can update content
  • A fully custom documentation site that goes beyond what any template provides
  • A custom web application built with the same modern stack
  • AI integration — search, chat, summarization, or content generation

These services exist for those cases. They are not required to use Astro Docus. They are available when the template is the starting point, not the finish line.


What it is: Integrating a headless CMS (Decap, Sveltia, Tina, CloudCannon, or another) into your Astro Docus project so that content can be edited through a visual admin interface instead of directly editing Markdown files.

Who it is for:

  • Teams with non-technical content editors
  • Organizations where multiple people update documentation
  • Projects where a WordPress-like dashboard is expected
  • Companies that want visual editing on top of their JAMstack site

Why it might be worth it: A CMS integration is rarely a single afternoon of work. Authentication, content schema, media handling, deployment configuration, and Git-based workflows each have their own moving parts. Getting them all right the first time avoids weeks of trial and error.

If your team will eventually need a CMS anyway, setting it up correctly from the start is cheaper than retrofitting it later.


Service 2 — Modern Documentation Website

Section titled “Service 2 — Modern Documentation Website”

What it is: A complete documentation website built with Astro Starlight (or Docusaurus) — from design to deployment. This is not a template customization. It is a full project built for your specific content, structure, and brand.

Who it is for:

  • Companies launching a documentation site for a product or API
  • Teams migrating from an outdated docs platform
  • Organizations that need a design that matches their brand precisely
  • Projects where the template structure is close but not exactly right

Why it might be worth it: A documentation site is often the first thing a developer sees when evaluating a product. It shapes perception. Getting the structure, navigation, search, and design right is not trivial — but it is one of the highest-leverage investments a technical product can make.

If your team does not have a dedicated frontend developer, or if the site needs to launch on a deadline, a custom build is often faster than learning the template deeply enough to customize it well.


What it is: A custom web application built with a modern stack — Astro, Next.js, Svelte, or another framework, depending on the requirements.

Who it is for:

  • Teams that need more than a static site
  • Projects that require authentication, dashboards, or user accounts
  • Businesses building internal tools or client-facing applications
  • Anyone whose requirements go beyond what a static template can provide

Why it might be worth it: Astro Docus is a static site. It does not handle logins, form persistence, or dynamic data. When a project outgrows the static model, a custom application is the next step.

Building a web app from scratch is a significant undertaking — architecture, database, authentication, deployment, and maintenance are all part of the package. Having someone who has built these systems before reduces risk and shortens the timeline.


What it is: AI-powered features integrated into your documentation or web project — semantic search, conversational Q&A, content summarization, automatic tagging, or content generation assistants.

Who it is for:

  • Documentation sites where users struggle to find answers
  • Teams that want a “chat with the docs” experience
  • Projects that generate large volumes of content and need automation
  • Products that want to differentiate with intelligent features

Why it might be worth it: AI is no longer a novelty — it is becoming an expectation. Users increasingly prefer asking a question and getting an answer over scanning search results. For documentation sites, this can dramatically improve the experience.

But AI integration is not just an API call. Choosing the right model, indexing your content properly, handling context windows, and designing a useful interaction pattern — these are all decisions that affect whether the feature actually helps users or just gets in the way.


None of these services are required to use Astro Docus. The template works on its own. The documentation you are reading is complete enough to set up, configure, and deploy without any outside help.

But if any of the following apply, one of these services might save significant time or improve the outcome:

  • You need a CMS but do not want to spend weeks on configuration
  • You need a documentation site that is more than a template tweak
  • You need a web application, not just a static site
  • You want to add AI features but are unsure where to start

Each service is a solution to a specific problem. If you do not have that problem, you do not need the service. That is the honest answer.


Each service will be documented in its own page under docs/services/, covering:

  1. Headless CMS Integration — what it includes, how it works, who it is for
  2. Modern Documentation Website — project scope, process, deliverables
  3. Custom Web App — capabilities, stack options, timeline
  4. AI Solutions — use cases, integration approach, limitations

Each page will focus on clarity — what you get, what you do not get, and whether it is the right fit for your situation.


Astro Docus Services:
├── Headless CMS Integration → visual editing on top of Git
├── Modern Documentation Website → full custom docs build
├── Custom Web App → dynamic applications beyond static
└── AI Solutions → search, chat, summarization, generation
Not required to use the template.
Available when the template is the starting point, not the finish line.

The template is the foundation. The services are for when you want to build higher.

👉 Contact for service inquiries: https://www.fiverr.com/creativitas