Add stage metadata to files - repo/ and project/

- Add Create stage metadata to files under repo/*/
- Add Create stage metadata to files under project/*/

.gitlab/CODEOWNERS

@@ -40,6 +40,27 @@
 /doc/user/project/repository/index.md @marcia
 /doc/user/project/repository/repository_mirroring.md @marcia
 /doc/user/project/repository/web_editor.md @marcia
+/doc/user/project/autocomplete_characters.md @marcia
+/doc/user/project/badges.md @marcia
+/doc/user/project/code_intelligence.md @marcia
+/doc/user/project/code_owners.md @marcia
+/doc/user/project/file_lock.md @marcia
+/doc/user/project/git_attributes.md @marcia
+/doc/user/project/highlighting.md @marcia
+/doc/user/project/index.md @marcia
+/doc/user/project/protected_branches.md @marcia
+/doc/user/project/protected_tags.md @marcia
+/doc/user/project/push_options.md @marcia
+/doc/user/project/repository/branches/index.md @marcia
+/doc/user/project/repository/gpg_signed_commits/index.md @marcia
+/doc/user/project/repository/jupyter_notebooks/index.md @marcia
+/doc/user/project/repository/x509_signed_commits/index.md @marcia
+/doc/user/project/settings/import_export.md @marcia
+/doc/user/project/settings/index.md @marcia
+/doc/user/project/settings/project_access_tokens.md @marcia
+/doc/user/project/static_site_editor/index.md @marcia
+/doc/user/project/web_ide/index.md @marcia
+/doc/user/project/wiki/index.md @marcia
 
 [Frontend]
 *.scss @annabeldunstone @gitlab-org/maintainers/frontend

doc/user/project/autocomplete_characters.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference
+description: "Autocomplete chars in Markdown fields."
+---
+
 # Autocomplete characters
 
 The autocomplete characters provide a quick way of entering field values into

doc/user/project/badges.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, howto
+---
+
 # Badges
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41174) in GitLab 10.7.

doc/user/project/code_intelligence.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: reference
 ---
 
@@ -10,7 +13,7 @@ Code Intelligence adds code navigation features common to interactive
 development environments (IDE), including:
 
 - Type signatures and symbol documentation.
-- Go-to definition
+- Go-to definition.
 
 Code Intelligence is built into GitLab and powered by [LSIF](https://lsif.dev/)
 (Language Server Index Format), a file format for precomputed code

doc/user/project/code_owners.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: reference
 ---
 

doc/user/project/file_lock.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, howto
+---
+
 # File Locking **(PREMIUM)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/440) in [GitLab Premium](https://about.gitlab.com/pricing/) 8.9.

doc/user/project/git_attributes.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference
+---
+
 # Git Attributes
 
 GitLab supports defining custom [Git attributes](https://git-scm.com/docs/gitattributes) such as what

doc/user/project/highlighting.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference
+---
+
 # Syntax Highlighting
 
 GitLab provides syntax highlighting on all files through the [Rouge](https://rubygems.org/gems/rouge) Ruby gem. It will try to guess what language to use based on the file extension, which most of the time is sufficient.

doc/user/project/index.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference
+---
+
 # Projects
 
 In GitLab, you can create projects for hosting

doc/user/project/protected_branches.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: reference, howto
 ---
 

doc/user/project/protected_tags.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: reference, howto
 ---
 

doc/user/project/push_options.md

 ---
-type: reference
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, howto
 ---
 
 # Push Options

doc/user/project/repository/branches/index.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: concepts, howto
 ---
 

doc/user/project/repository/gpg_signed_commits/index.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: concepts, howto
 ---
 

doc/user/project/repository/jupyter_notebooks/index.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference
+---
 # Jupyter Notebook Files
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/2508/) in GitLab 9.1.

doc/user/project/repository/x509_signed_commits/index.md

 ---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: concepts, howto
 ---
 

doc/user/project/settings/import_export.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, howto
+---
+
 # Project import/export
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/3050) in GitLab 8.9.

doc/user/project/settings/index.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, index, howto
+---
+
 # Project settings
 
 NOTE: **Note:**

doc/user/project/settings/project_access_tokens.md

+---
+stage: Create
+group: Source Code
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, howto
+---
+
 # Project access tokens (Alpha) **(CORE ONLY)**
 
 CAUTION: **Warning:**

doc/user/project/static_site_editor/index.md

 ---
+stage: Create
+group: Static Site Editor
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
 type: reference, how-to
 description: "The static site editor enables users to edit content on static websites without prior knowledge of the underlying templating language, site architecture or Git commands."
 ---

doc/user/project/web_ide/index.md

+---
+stage: Create
+group: Editor
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, how-to
+---
+
 # Web IDE
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4539) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 10.4.

doc/user/project/wiki/index.md

+---
+stage: Create
+group: Knowledge
+info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
+type: reference, how-to
+---
+
 # Wiki
 
 A separate system for documentation called Wiki, is built right into each