Docs reorg: part 1 - add section definitions

docs/README.md

@@ -1,14 +1,15 @@
 # Grafana Agent Documentation
 
-This directory contains documentation for Grafana Agent. It is split into two
-parts:
+This directory contains documentation for Grafana Agent. It is split into the
+following parts:
 
-* `user/`: Documentation for users. This directory is hosted on
-  [grafana.com/docs/agent](https://grafana.com/docs/agent/latest/) and we
-  recommend interacting with it there instead of viewing the markdown on
+* `sources/`: Source of user-facing documentation. This directory is hosted on
+  [grafana.com/docs/agent](https://grafana.com/docs/agent/latest/), and we
+  recommend viewing it there instead of the markdown on
   GitHub.
 * `developer/`: Documentation for contributors and maintainers.
 * `rfcs/`: RFCs for proposals relating to Grafana Agent.
+* `generator/`: Code for generating some parts of the documentation.
 
 ## Preview the website
 

docs/developer/writing-docs.md

@@ -0,0 +1,78 @@
+# Writing documentation
+
+This page is a collection of guidelines and best practices for writing
+documentation for Grafana Agent.
+
+## Flow Mode documentation organisation
+
+The Flow mode documentation is organized into the following sections:
+
+### Get started
+
+The best place to start for new users who are onboarding.
+
+We showcase the features of the Agent and help users decide when to use Flow and
+whether it's a good fit for them.
+
+This section includes how to quickly install the agent and get hands-on
+experience with a simple "hello world" configuration.
+
+### Concepts
+
+As defined in the [writer's toolkit][]:
+
+> Provides an overview and background information. Answers the question “What is
+> it?”.
+
+It helps users to learn the concepts of the Agent used throughout the
+documentation.
+
+### Tutorials
+
+As defined in the [writer's toolkit][]:
+
+> Provides procedures that users can safely reproduce and learn from. Answers
+> the question: “Can you teach me to …?”
+
+These are pages dedicated to learning. These are more broad,
+while [Tasks](#tasks) are focused on one objective. Tutorials may use
+non-production-ready examples to facilitate learning, while tasks are expected
+to provide production-ready solutions.
+
+### Tasks
+
+As defined in the [writer's toolkit][]:
+
+> Provides numbered steps that describe how to achieve an outcome. Answers the
+> question “How do I?”.
+
+However, in the Agent documentation we don't mandate the use of numbered steps.
+We do expect that tasks allow users to achieve a specific outcome by following
+the page step by step, but we don't require numbered steps because some tasks
+branch out into multiple paths, and numbering the steps would look more
+confusing.
+
+Tasks are production-ready and contain best practices and recommendations. They
+are quite detailed, with Reference pages being the only type of documentation
+that has more detail.
+
+Tasks should not be paraphrasing things which are already mentioned in the
+Reference pages, such as default values and the meaning of the arguments.
+Instead, they should link to relevant Reference pages.
+
+### Reference
+
+The Reference section is a collection of pages that describe the Agent
+components and their configuration options exhaustively. This is a more narrow
+definition than the one found in the [writer's toolkit][].
+
+This is our most detailed documentation, and it should be used as a source of
+truth. The contents of the Reference pages should not be repeated in other parts
+of the documentation.
+
+### Release notes
+
+Release notes contain all the notable changes in the Agent. They are updated as
+part of the release process.
+
+[writer's toolkit]: https://grafana.com/docs/writers-toolkit/structure/topic-types/

docs/sources/flow/_index.md

@@ -67,9 +67,10 @@ prometheus.remote_write "default" {
 }
 ```
 
-## {{% param "PRODUCT_ROOT_NAME" %}} configuration generator
 
-The {{< param "PRODUCT_ROOT_NAME" >}} [configuration generator](https://grafana.github.io/agent-configurator/) will help you get a head start on creating flow code.
+## {{< param "PRODUCT_NAME" >}} configuration generator
+
+The {{< param "PRODUCT_NAME" >}} [configuration generator](https://grafana.github.io/agent-configurator/) will help you get a head start on creating flow code.
 
 {{% admonition type="note" %}}
 This feature is experimental, and it doesn't support all River components.