Join the beta to get early access

We're bringing the power of structured authoring to docs-as-code

Reuse content, enforce rules and structure, federate documentation from multiple repositories, all while using a familiar docs-as-code workflow

Markdown page Topic template
Use topic template Author in Markdown Model content semantically
---
title: Deploy Command
---

<Topics.CliCommand title="Deploy Command">
  <Description>
    Deploys the current project to a remote server.

    ```bash title="Deploy to production"
    deployatron deploy -e production
    ```
  </Description>

  <Flag name="--environment" required>
    The environment to deploy to.
  </Flag>

  <Flag name="--dry-run">
    Prints the deployment plan without executing it.
  </Flag>

  <Flag name="--timeout">
    The timeout in **seconds** for the deployment.
  </Flag>
</Topics.CliCommand>
          
Define topic shape Add validation Map topic to Markdown
---
attributes:
  - name: title
slots:
  - name: Description
    validate:
      min_length: 1 sentence
  - name: Flag
    repeatable: true
    attributes:
      - name: name
      - name: required
---

# { @title }

<Slot name="Description" />

## Flags

<Fragment foreach="F in Flag">
  ### { @F.name } { @F.required ? '(required)' : '' }

  <Slot name="F" />
</Fragment>

Structured Markdown

The power of DITA in Markdown and docs-as-code

Docs-as-code doesn't have to be a content wild west

Add structure and rules to your content as you grow, so your content stays consistent and easy to maintain

Content reuse & single sourcing

Organize your content into discrete, self-contained topics to reuse across your project

getting-started.md
# Getting Started

<ProductDescription />

## Creating an account

<AccountCreationInstructions />
                

Enforce consistency

Configure rules to validate your content and ensure it adheres to your standards

_topics/tutorial.md
---
slots:
  - name: TutorialSteps
    required: true
    validate:
      component: Step+

                

Layer on structure incrementally

Start with simple Markdown, and add structure as your docs grow. Doctave scales with your team's needs.

_topics/feature.md
---
attributes:
  - name: title
    required: true
  - name: enterprise_only
    required: true
                

Additional resources

Learn about how we're bringing structured authoring to docs-as-code

We're creating new ways to author Markdown documentation, while allowing for single sourcing, content reuse, and semantic structure

Blog post

The path to structured content with Markdown

The path to structured content with Markdown

Video

Markdown and Structured Authoring

Ready to bring structure to your Markdown docs?

Join our beta and help us shape the future of structured authoring

Join the beta ›

Frequently asked questions

Can’t find the answer you’re looking for? Reach out to us.

How do join the beta?
Click the "Join the beta" button above and schedule a call with us. We will discuss your needs, and get you set up with the beta.
How does the beta work?
You'll get early access to new structured authoring features, and we'll be working closely with you to help you get the most out of Doctave.

We'll also be sharing our roadmap and future plans with you, so you can see where we're headed.
Do I need to be a customer to get early access?
You will need a valid Doctave subscription to get early access to the beta. But as a thank you for participating in our beta, we will be giving discounts to early access customers.
How long is the beta?
Never rush greatness, but we expect the beta to finish by the end of 2024.