Added metadata for Pages docs

What does this MR do?

This update adds metadata (group and stage) to the Pages topic so it's easier to find the docs owner.

Related issues

Related to: #216290 (closed)

Author's checklist (required)

• Follow the Documentation Guidelines and Style Guide.
• If you have developer access or higher (for example, GitLab team members or Core Team members)
  • Apply the documentation label, plus:
    • The corresponding DevOps stage and group label, if applicable.
    • development guidelines when changing docs under doc/development/*, CONTRIBUTING.md, or README.md.
    • development guidelines and Documentation guidelines when changing docs under development/documentation/*.
    • development guidelines and Description templates (.gitlab/*) when creating/updating issue and MR description templates.
  • Assign the designated Technical Writer.

When applicable:

• Update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Add GitLab's version history note(s).
• Add the product tier badge.
• Add/update the feature flag section.
• If you're changing document headings, search doc/*, app/views/*, and ee/app/views/* for old headings replacing with the new ones to avoid broken anchors.

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.
  • Add Technical Writing and docs:: workflow label.
  • Add docs-only when the only files changed are under doc/*.

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.

changed milestone to %13.0

added Technical Writing docs-only docsnon-content documentation labels

resolved all threads

added 1 commit

• 56fffb35 - Apply suggestion to doc/user/project/pages/pages_access_control.md

Compare with previous version

resolved all threads

added 1 commit

• 70755fb5 - Apply suggestion to doc/user/project/pages/pages_access_control.md

Compare with previous version

assigned to @eread

@eread Are you the one to assign to?

This should be pretty straightforward. One folder, one owner. https://about.gitlab.com/handbook/product/categories/#release-management-group

I left the other metadata that was in there from before...

approved this merge request

resolved all threads

merged

mentioned in commit 6bdcfb69

added workflowcanary label

added workflowproduction label and removed workflowcanary label

This merge request has been deployed to the pre.gitlab.com environment, and will be included in the upcoming self-managed GitLab 13.0.0 release.

---

🤖 This comment is generated automatically using the Release Tools project.

added published label

added devopsrelease [DEPRECATED] + 1 deleted label

changed title from Added metadata for pages docs to Added metadata for Pages docs

changed the description

changed the description

added typemaintenance label