Tag: version-control
9 articles tagged version-control.
- A single repository?
A single Git repository for all technical documentation content maximizes reuse, consistency, and quality while simplifying collaboration across writing and dev teams.
- CMS: workflow as a bonus, but reliability to be tested
A CMS like SharePoint or Alfresco adds workflow and file-locking to technical writing, and some (DocZone, Componize) even handle DITA XML - but their reliability for archiving source files must be tested and backed by a solid backup strategy.
- Git: from file to content
Think content rather than files with Git: branches, commits, and diffs for technical documentation make collaboration and version management far simpler and safer.
- Repository
Content is a company's intangible capital. Learn how to choose and manage a documentation repository to protect, version, and share technical content across teams.
- Shared network directories - unsuitable for group work
Shared network drives are a common but inadequate solution for team documentation collaboration. Learn why they fail and what version-control alternatives work better.
- SQL database
In a CMS like Drupal, Joomla, or WordPress, technical content lives in an SQL database that keeps only per-article history and cannot search and replace across all content - one reason to manage it as text files instead.
- Using branches in source management systems
Use Git branches to manage parallel documentation projects, product variants, and translation workflows without conflicts - a practical guide for technical writers.
- Version management systems - rustic but reliable
Use Git or Subversion to manage technical documentation like source code: track changes, collaborate with your team, and roll back safely at any time.
- Which repository for group work?
Why folders and shared network drives fall short for collaborative technical writing: concurrent edits overwrite one another and file locking blocks batch changes - problems that version-control systems solve reliably.