Coheris by ChapsVision
Documentation Manager — Docs-as-code and Multi-contributor Management
Key Elements
| Category | Data |
|---|---|
| Organization | Coheris by ChapsVision |
| Period | September 2022 to April 2025 |
| Domains | CRM, merchandising, inventory, and field sales |
| Role | Senior Technical Writer & Consultant, then Documentation Manager |
| Scope | Documentation audit, architecture, migration, writing, governance, and release management |
| Audiences | Administrators, business users, integrators, developers, Support, and Customer Success teams |
| Languages | French and English |
| Environment | Docusaurus, Markdown, GitLab, CI/CD, REST APIs, ReDoc, Confluence |
Project Overview
Coheris by ChapsVision develops software solutions for Customer Relationship Management and merchandising.
My collaboration began with a four-month consulting assignment to audit and redesign the documentation of the Coheris CRM suite. Following this initial phase, I joined the organization as Documentation Manager and extended the approach to the Merch-Nomad product line.
Across the full assignment, I transformed legacy documentation into secure, bilingual documentation portals and established a sustainable docs-as-code and multi-contributor model involving Product, R&D, Support, and Customer Success teams.
Context
The existing CRM documentation was distributed across obsolete PDF-based deliverables produced with several authoring tools. This made updates slow, limited collaboration with R&D, and made it difficult to align documentation with frequent software releases.
The documentation also covered a broad technical and functional scope: installation, upgrades, configuration, administration, advanced business features, integrations, REST APIs, and external data flows.
The objective was to replace this fragmented model with secure, maintainable, and user-oriented documentation portals that could evolve alongside the products and support both French- and English-speaking audiences.
Key Deliverables
Documentation Portals & Content Modernization
I began by conducting a full audit of the Coheris CRM documentation and reviewing the applications hands-on to understand both technical workflows and business use cases.
Based on this analysis, I proposed and implemented a unified documentation architecture using Docusaurus and Markdown. The same principles were subsequently applied to the Merch-Nomad product line, with a dedicated portal for each documentation ecosystem.
The work included:
- migrating and restructuring legacy content;
- creating bilingual French–English documentation;
- rewriting installation, upgrade, configuration, administration, and business-feature content;
- producing realistic examples, screenshots, diagrams, and workflows;
- modernizing developer documentation for REST APIs and integrations;
- integrating ReDoc to improve API reference usability.
For each major product release, I produced and maintained a dedicated documentation website, covering four applications across the two product lines.
Docs-as-Code, Contribution & Governance
I established a GitLab-based docs-as-code workflow connected to the software development lifecycle.
Developers became documentation co-contributors through Git branches and merge requests, while Product Owners retained responsibility for functional validation. CI/CD workflows supported documentation builds, previews, and publication across development and release branches.
Beyond the technical workflow, I structured the documentation governance model through:
- documentation roadmaps aligned with product roadmaps;
- contribution and review processes;
- release-based documentation planning;
- prioritization across two product lines;
- systematic validation by Product Owners;
- transformation of Support and Customer Success feedback into reusable user documentation.
This approach made documentation a shared product responsibility while preserving editorial consistency and quality.
My Role
I managed the documentation lifecycle across Coheris CRM and Merch-Nomad, combining documentation strategy, architecture, technical writing, portal implementation, release management, and governance.
My role evolved from an initial consulting assignment into a transverse internal position at the interface of R&D, Product, Support, and Customer Success. I remained responsible for documentation coherence, quality, planning, and publication while enabling subject-matter experts to contribute effectively.
Technologies & Tools
Docusaurus, Markdown, GitLab, Git, CI/CD, Visual Studio and VS Code, Sourcetree, Confluence, REST APIs, OpenAPI, Swagger, ReDoc, React, CSS, and JavaScript.
Confidentiality
The documentation portals were secured and intended for customers, partners, and internal teams. They are therefore not publicly accessible and cannot be included directly in this portfolio.
This page presents the scope, approach, and responsibilities involved without disclosing proprietary documentation or product information.
©Author: Florence Venisse, Technical Documentation & AI Expert – Reviewed version of 07/21/2026.