Articles

To choose a tool appropriate to your needs is to understand what functions it will serve. This article identifies the key reasons why you would choose a static site generator (SSG) or a content management system (CMS) for constructing your devportal.

In the second part of our series, you will discover analytics and why it’s needed for Docs As Code. This post is focusing on the functional basis of Quality Assurance.

In the first part of our new Docs As Code series, you will read about the philosophy behind the approach coupled with Quality Assurance, and how you can get started.

We would like to introduce a new tool called _Rector_ that could speed up an upgrade process and can reduce upgrade costs. We run a proof of concept for the possible use cases in which Rector can be beneficial for Drupal developers - including but not limited to the automated update to Drupal 9.

On the Write The Docs London meetup in January speakers from leading Git code repositories talked about how their teams dogfood their own tools to do their documentation. _Version the Docs_ covered Bitbucket and GitLab, but we missed a GitHub presentation. To fill this gap, we interviewed Anne Gentle about GitHub, treating docs like code, and community contributions to documentation.

The annual North-American Write The Docs conference this year featured 2 API documentation redo presentations: 1. Lyzi Diamond described Mapbox (formerly a part of Development Seed) documentation automagic in detail, 2. Sarah Hersh talked about the journey that NPR One undertook towards a new task-based approach for their API's developer documentation. In this post we aim to give you an account of these presentations.