Skip to content

Fixed broken link

Suzanne Selhorn requested to merge docs-selhorn-brokenlinks-2 into master

What does this MR do?

Update broken external links as part of the monthly tech writer cleanup tasks.

  public/omnibus/roles/README.html:
    [ ERROR ] external_links - broken reference to https://docs.gitlab.com/ee/administration/pages: 404
  public/omnibus/roles/index.html:
    [ ERROR ] external_links - broken reference to https://docs.gitlab.com/ee/administration/pages: 404

 public/omnibus/package-information/licensing.html:
    [ ERROR ] external_links - broken reference to https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/: link has moved permanently to 'https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/'

  public/omnibus/settings/smtp.html:
    [ ERROR ] external_links - broken reference to https://sendgrid.com/docs/API_Reference/SMTP_API/integrating_with_the_smtp_api.html: link has moved permanently to 'https://sendgrid.com/docs/for-developers/sending-email/getting-started-smtp/'

  public/omnibus/settings/dns.html:
    [ ERROR ] external_links - broken reference to https://www.namecheap.com/support/knowledgebase/article.aspx/9776/2237/how-to-create-a-subdomain-for-my-domain: link has moved permanently to 'https://www.namecheap.com/support/knowledgebase/article.aspx/9776/2237/how-to-create-a-subdomain-for-my-domain/'

I can't figure this one out:

  public/omnibus/settings/dns.html:
    [ ERROR ] external_links - broken reference to http://xip.io: Failed to open TCP connection to xip.io:80 (getaddrinfo: Name does not resolve)

Related issues

Related to: technical-writing#353 (closed)

Author's checklist (required)

Do not add the ~"feature", frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

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

  • 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

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Suzanne Selhorn

Merge request reports

Loading