Build SSOT for account and limit settings
What does this MR do?
In #347004 (closed) Marcel identified duplication on data about repository limits:
- GitLab.com: https://docs.gitlab.com/ee/user/gitlab_com/#account-and-limit-settings
- Self-managed: https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html (various subheadings)
Goals:
- Put everyone's data in their respective corners.
- GitLab.com info stays in the
gitlab_com
directory - Self-managed data moves into the page in the
admin_area
directory
- GitLab.com info stays in the
- Look for crosslinks that should update. So far, looks good.
- Try not to wince at
user/admin_area/settings/account_and_limit_settings.md
because oh dear, it needs some love
Related issues
Related to #347004 (closed) where the need was identified by Marcel.
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
Ensure that the product tier badge is added to topic's h1
. -
Request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are 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.
Review 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. - 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 likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure 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. -
Ensure a release milestone is set.