documentation

Start Your Drupal Automated Performance Testing Today

janez — Mon, 25 Mar 2024 20:27:42 +0000

Ensure your Drupal websites run smoothly. Gander documentation walks you through setting up and using the performance testing framework.

janez Mon, 03/25/2024 - 13:27

On 20 Years of Drupal - an interview with Emma Jane Hogbin

lynette@tag1consulting.com — Wed, 12 May 2021 14:00:20 +0000

Many of Tag1’s team members have worked in various other companies and organizations during the 20 years Drupal has existed. In those many years, we have worked for and collaborated with other Drupal users and developers all over the world. This Tag1 Team Talk highlights one of those people.

lynette@tag1co… Wed, 05/12/2021 - 07:00

Documentation as code: Part 3: A Linting How To - The Vale Linter in action (Demo) - Tag1 TeamTalk #027.3

lynette@tag1consulting.com — Mon, 26 Oct 2020 12:32:39 +0000

In part 3 of our Tag 1 Team talks about documentation as code: linting for prose, we demonstrate the Vale linter in action. This open-source linter for prose is highly customizable, making it possible for writers with little coding experience or developers with little writing experience to start testing their work.

lynette@tag1co… Mon, 10/26/2020 - 05:32

Documentation as code: Part 2: A Linting How To - What tools are out there and how do they work? - Tag1 TeamTalk #027.2

lynette@tag1consulting.com — Mon, 19 Oct 2020 17:59:31 +0000

One well-known type of tool in the software world, but less so in the writing world is the linter. Software developers often consider their linters to be invaluable in catching or preventing errors, as well as enforcing defined stylistic guidelines before errors get out in front of the world.

lynette@tag1co… Mon, 10/19/2020 - 10:59

Documentation as code: Part 1: A Linting How To - What, Why, and How? - Tag1 TeamTalk #027.1

lynette@tag1consulting.com — Tue, 13 Oct 2020 13:25:29 +0000

Documentation is a critical part of any customer-facing product or service. Without it, your customers need hand-holding, your support staff struggles to help your users, and your company spends money on unhappy customers instead of creating new products.

lynette@tag1co… Tue, 10/13/2020 - 06:25

Enabling your developers with docs-as-code methodologies: linting prose

lynette@tag1consulting.com — Mon, 28 Sep 2020 13:20:23 +0000

If you’ve been part of a writing team, known a writer, or ever considered documentation to be an important aspect of your business, you may have heard of docs-as-code. If you haven’t, buckle up, because using these methodologies can lower the bar for your developers to contribute quality documentation to your project. At the same time, it also reduces the work your writing team has to do to ensure your documentation meets your company style and standards. ## Why docs as code? The Write the Docs community of technical writers has been exploring the concept of docs as code for years. As a community, they define this concept as a philosophy that you should be writing documentation with the same tools as code: * Issue Trackers * Version Control (Git) * Plain Text Markup (Markdown, reStructuredText, AsciiDoc) * Code Reviews With this philosophy, your writers use the same (or at least similar) tools and workflows as your developers. Your writers can be more easily embedded in your development teams, and can write the first draft of documentation. This speeds final drafts to conclusion. When your writers and developers are using the same tools, collaboration is faster and easier. Writers and...

lynette@tag1co… Mon, 09/28/2020 - 06:20