Improve structure and SEO of notifications docs
What does this MR do?
- Improves the structure and SEO of the notifications docs
- Improves the introduction of important notification concepts
The aim of these changes is to make it easier for the reader to achieve the following:
(1) Find what they're looking for.
(2) Understand how to implement the notification options to suit their needs.
Related issues
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. - [-] If applicable, update the permissions table.
- [-] Link docs to and from the higher-level index page, plus other related docs where helpful.
-
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖