docs: add documentation on documentation deployment (#13739)

docs/DOC_WRITING_GUIDELINES.md

@@ -10,6 +10,31 @@
 * Check the meaning of words in Microsoft's [A-Z word list and term collections](https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/accessibility-terms) (use the search input!).
 * RFC keywords should be used in technical documents (uppercase) and we recommend to use them in user documentation (lowercase). The RFC keywords are: "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL. They are to be interpreted as described in [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
 
+### Links
+
+**NOTE:** Strongly consider the existing links - both within this directory and to the website docs - when moving or deleting files.
+
+Relative links should be used nearly everywhere, due to versioning. Note that in case of page reshuffling, you must update all links references.
+When deleting a link, redirects must be created in `docusaurus.config.js` to preserve the user flow.
+
+### Code Snippets
+
+Code snippets can be included in the documentation using normal Markdown code blocks. For example:
+
+```md
+    ```go
+    func() {}
+    ```
+```
+
+It is also possible to include code snippets from GitHub files by referencing the files directly (and the line numbers if needed). For example:
+
+```md
+    ```go reference
+    https://github.com/cosmos/cosmos-sdk/blob/v0.46.0/server/types/app.go#L57-L59
+    ```
+```
+
 ## Technical Writing Course
 
 Google provides a free [course](https://developers.google.com/tech-writing/overview) for technical writing.