member badge
Uppili Srinivasan
The existing integration is not suitable for teams that already maintain documentation in a structured Git repository with advanced configurations (snippets, variables, YAML, asset organization, etc.). This limits adoption for users expecting a scalable, repo-first documentation workflow.
  1. Articles synced from GitHub are appended to the bottom of categories during incremental syncs.
* No ability to define or maintain article hierarchy from the repository.
* Limits usability for teams managing structured documentation trees.
  1. No Structured Asset Management
* Media files are stored in a single, non-segregated folder.
* No support for organizing assets into logical directories within the repo. We would like to maintain the drive folder structure similar to what we have in Document360.
  1. No Support for Advanced Docs-as-Code Features
* No support for reusable snippets, variables, or YAML-based configurations.
* Does not align with modern documentation practices used in Git-based workflows.