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
CMS platforms like SharePoint, Alfresco, or Drupal add workflow to technical writing but introduce reliability risks. Learn what to evaluate before committing to one.
- 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. Understand the implications for backup, content migration, and reuse at scale.
- 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, Subversion, or SourceSafe 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?
Choosing the right repository for collaborative technical writing: compare shared drives, CMS, version control systems, and cloud platforms for documentation teams.