Configure once. Publish everywhere. An OSS experiment to automate your documentation from the repository to multiple platforms (Confluence, Notion, SharePoint).

We know technical documentation is often a headache:

• ❌ Breaks developer workflow.
• ❌ Quickly becomes outdated.
• ❌ Locked into platforms that create vendor dependency.

We are exploring a solution where the repository is the single source of truth. Each code change synchronizes documentation across your chosen destinations.

flowchart LR
    A[Git Repository] --> B[CI/CD Pipeline]
    B --> C[Conversion]
    C --> D[Confluence]
    C --> E[Notion]
    C --> F[SharePoint]

This is still under construction 🚧, but we want to validate if it solves a real problem for developers and enterprises.

# docs_publish.yml
docs:
  source: /docs
  targets:
    - confluence
    - notion
  formats:
    - markdown
    - html
publish: true

The idea is simple: a single YAML file keeps your documentation synchronized.

• 🔄 Document without leaving the repository.
• 🚀 Keep documentation always updated with every PR.

• 📦 Avoid lock-in with a single provider.
• 💸 Reduce costs of documentation migration.
• 🔐 Greater control and compliance by centralizing information.

👉 We want to validate if these benefits are relevant for your team.

QuipuFlow is OSS under Apache 2.0. Our intention is to build this project with the community from day one.

• The core will always be free.
• We are exploring an open-core model with premium connectors.

👉 See the LICENSE file for more details.

1. Join the waitlist for early access.
2. Open an issue with your feedback or use case (even short notes are valuable).
3. Share the project if you think your team would benefit.

This project is distributed under the Apache 2.0 license. See the LICENSE file for more information.