This MR also removes the Mermaid diagram, because the text says it's about how the containers are built. This information would be for a developer who is generating the containers, not for someone who is deploying the solution, I think?
The goal should be to quickly get people to the details of how to implement and configure the solution. We can move the diagram to a development page if that makes sense. (If so, please let me know where.)
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If the content requires it, ensure the information is reviewed by a subject matter expert.
Technical writer review items:
Ensure docs metadata is present and up-to-date.
Ensure the appropriate labels are added to this MR.
Ensure a release milestone is set.
If relevant to this MR, ensure content topic type principles are in use, including:
The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
Any task steps should be written as a numbered list.
If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
