Hi TULIP Team,
I’d like to suggest adding an advanced documentation capability directly inside Tulip — similar to what Confluence offers alongside Jira — with the ability to auto-generate and maintain documentation using AI as apps are built.
Problem
For large app ecosystems (interconnected apps, Node-RED flows, connectors, tables), the current trigger-level “Documentation” area is too limited. Our technical documentation lives outside Tulip (in Confluence JIRA), where it drifts out of sync with the apps, is hard to discover, and can’t be linked easily to the specific app, step, version, or connector it describes.
On top of that, writing it manually is time-consuming and rarely kept up to date.
Proposed solution
A first-class documentation module, accessible from a dedicated tab at the app level (next to Steps, Analytics, Versions… — see attached mockup), offering at minimum:
- AI-generated documentation: leveraging the app’s own structure (steps, triggers, connectors, tables) to automatically draft a first version of the documentation, and to keep it updated as the app evolves. The developer reviews and refines rather than starting from a blank page.
- A rich text / Markdown editor (headings, tables, code blocks, images, diagrams).
- Hierarchical pages and sub-pages to build a structured knowledge base.
- Versioning tied to app versions.
- Cross-linking to platform objects (steps, connectors, tables, other apps).
- Search across all documentation, plus optional PDF / Markdown export.
Why it matters
Because Tulip already knows the full structure of each app, it is uniquely positioned to generate accurate documentation. This keeps documentation synchronized with the apps it describes, removes most of the manual effort, improves onboarding and maintenance, and preserves the rationale behind each design decision — turning Tulip into a single source of truth for both executing and understanding applications.
Suggested first step
Even a minimal version — an AI-assisted draft generated from the app’s structure, editable in a Confluence-style editor with versioning and search — would deliver immediate value, and could later be extended with cross-object linking and continuous auto-updates.
Thanks !
Paul