# Writing Standards I Implement

Technical writing is not just a matter of documenting for the sake of tracking up stuff and methodologies.

The core of the job is to implement standards so that the objective audience can easily navigate through the documentation to solve their tasks using software.

This section describes the standard I implement in companies when writing documentation for them. We could call it: **my standard writing style guide**.

{% hint style="info" %}
**NOTE**: I'm migrating this section here from a private repo, so it's currently not 100% complete!
{% endhint %}

***

### Writing style guide

Recommended design practices, common mistakes to avoid, rules for everyday punctuation, grammar, and sources of information for the less common cases.

The objective of this writing style guide is to help companies communicate information in a clear, transparent fashion, and to facilitate consistency in tone and delivery. I write documentation for different companies for a variety of audiences, across multiple geographies and with very different skill sets and these are the standards I implement in companies, and share with their teams.

{% hint style="info" %}
**NOTE:** This document is freely inspired by the [**Red Hat Technical Writing Style Guide**](https://stylepedia.net/)
{% endhint %}

Table of contents:

1. [Grammar](/federico-trottas-portfolio/my-portfolio/writing-standards-i-implement/grammar.md)
2. [Overall design](/federico-trottas-portfolio/my-portfolio/writing-standards-i-implement/overall-design.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://federico-trotta.gitbook.io/federico-trottas-portfolio/my-portfolio/writing-standards-i-implement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.