New_cdot_navigation docs integration
What does this MR do and why?
Related to customers-gitlab-com#7008 (closed)
new_cdot_navigation
feature flag rollout).
An integration branch of updates for the new_cdot_navigation
feature.
Updates:
Documentation link | Original MR | Status |
---|---|---|
payment methods documentation | Update CustomersPortal payment docs (!136124 - merged) | Reviewed ![]() |
account owner/company details documentation, GL account linking documentation | Update personal and company information docs (!136126 - merged) | Reviewed ![]() |
GitLab SaaS/SM & QSR payment method pages | Update GitLab SaaS/SM payment docs (!136520 - merged) | Reviewed ![]() |
Billing/subscription contact (New section) | Add documentation for billing contacts (!136525 - merged) | Reviewed ![]() |
Contact troubleshooting (New section) | Billing contact troubleshooting (!137401 - merged) | Reviewed ![]() |
to support the new CDot Navigation UI flow
Screenshots or screen recordings
See original MRs for examples of new UI flows
How to set up and validate locally
- Run the
review-docs-deploy
pipeline job - Click on the deployed app to view changes
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
changed milestone to %16.8
assigned to @lcallahan
mentioned in merge request !136126 (merged)
mentioned in merge request !136124 (merged)
mentioned in merge request !136520 (merged)
mentioned in merge request !136525 (merged)
- Resolved by Michael Lunøe
@lcallahan - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request.
1 Warning 8b74d0bb: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines. 1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/subscriptions/gitlab_com/index.md
(Link to current live version) -
doc/subscriptions/self_managed/index.md
(Link to current live version) -
doc/subscriptions/customers_portal.md
(Link to current live version) -
doc/subscriptions/quarterly_reconciliation.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Ghost User-
mentioned in issue customers-gitlab-com#7008 (closed)