✅ Ready to clone and code.

Co-authored-by: Alessandro Fael Garcia <alessfg@hotmail.com>

Author: mjang

.github/CODEOWNERS

@@ -2,7 +2,7 @@
 # the noted directories.
 #
 # If you want to add, modify, or delete files in any of these directories,
-# open a pull request. Then add the approrpriate group name (without the `@`)
+# open a pull request. Then add the appropriate group name (without the `@`)
 # to the list of "Reviewers."
 #
 # Order is important; the last matching pattern takes precedence. 

.github/workflows/rename_template.yml

@@ -4,4 +4,4 @@
 
 ## 1.0.0 (Month Date, Year)
 
-Initial open source release of the documentation repository for enterprise NGINX products. The content was previously in a closed repository.
+Initial open source release of the documentation repository for enterprise NGINX products. This is a filtered mirror of an internal repository.

.github/workflows/scripts/rename_project.sh

@@ -1,35 +1,33 @@
-# Contributing Guidelines
+# Contributing guidelines
 
 The following is a set of guidelines for contributing to this project.
 We really appreciate your desire to contribute!
 
-## Table of Contents
+## Table of contents
 
-- [Ask a Question](#ask-a-question)
 - [Report a Bug](#report-a-bug)
 - [Suggest a Feature or Enhancement](#suggest-a-feature-or-enhancement)
 - [Open a Discussion](#open-a-discussion)
 - [Submit a Pull Request](#submit-a-pull-request)
+  - Review our [Git style guide](#git-style-guide)
+  - Review our Documentation [style guide](./templates/style-guide.md)
 - [Issue Lifecycle](#issue-lifecycle)
+- [Content edited elsewhere](#content-edited-elsewhere)
 - [F5 Contributor License Agreement (CLA)](#f5-contributor-license-agreement)
 
-## Ask a Question
-
-To ask a question, open an issue on GitHub with the label `question`.
-
-## Report a Bug
+## Report a bug
 
 To report a bug, open an issue on GitHub with the label `bug` using the
 available bug report issue template. Before reporting a bug, make sure the
 issue has not already been reported.
 
-## Suggest a Feature or Enhancement
+## Suggest a feature or enhancement
 
 To suggest a feature or enhancement, open an issue on GitHub with the label
 `feature` or `enhancement` using the available feature request issue template.
 Please ensure the feature or enhancement has not already been suggested.
 
-## Open a Discussion
+## Open a discussion
 
 If you want to start a conversation with the community and maintainers,
 we encourage you to use
@@ -44,32 +42,49 @@ To contribute to NGINX documentation, follow these steps:
 - Implement your changes in your branch
 - Submit a pull request (PR) when your changes are ready for review
 
-## Contributing with Git
+Alternatively, you're welcome to suggest improvements to highlight problems with
+our documentation as described in our [support](./SUPPORT.md) page.
 
-<!-- Separate doc pages, CONTRIBUTING_GIT.md and CONTRIBUTING_other.md. 
-Need: issue to include "Edit this page" links, similar to what we already do for N Unit docs, https://unit.nginx.org/ -->
+### Git Style Guide
 
-At this time, we support contributions using Git. We expect this audience to also know how to build documentation using the command line. If you're in this group, start with how you can [contribute with Git](./CONTRIBUTING_GIT.md).
-<!-- People who contribute via CloudCannon? 
+- Keep a clean, concise and meaningful Git commit history on your branch, rebasing locally and squashing before you submit a PR
+- Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/>
+  and summarized in the next few points:
 
-We're working on alternative contribution methods, described in CONTRIBUTING_OTHER.md
--->
+  - In the subject line, use the present tense ("Add feature" not "Added feature")
+  - In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+  - Limit the subject line to 72 characters or less
+  - Reference issues and pull requests liberally after the subject line
+  - Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in
+    your text editor to write a good message instead of `git commit -am`)
 
-Alternatively, you're welcome to highlight problems with our documentation as
-described in our [support](./SUPPORT.md) page.
+### Docuemntation style guide
 
-## Issue Lifecycle
+For detailed guidance, see our documentation [style guide](./templates/style-guide.md).
+
+## Issue lifecycle
 
 To ensure a balance between work carried out by the NGINX team while encouraging community involvement on this project, we use the following
 issue lifecycle:
 
 - A new issue is created by a community member
 - An owner on the NGINX team is assigned to the issue; this owner shepherds the issue through the subsequent stages in the issue lifecycle
 - The owner assigns one or more [labels](https://github.com/nginxinc/oss-docs/issues/labels) to the issue
-- The owner, in collaboration with the wider team, determines what milestone to attach to an issue. They may be milestones correspond to product releases
+- The owner, in collaboration with the community member, determines what milestone to attach to an issue. They may be milestones correspond to product releases
+
+## Content edited elsewhere
+
+This repository does not include all documentation available at https://docs.nginx.com. Other relevant repositories include:
+
+- [NGINX Open Source](https://github.com/nginx/nginx)
+- [NGINX Unit](https://github.com/nginx/unit)
+- [NGINX Ingress Controller](https://github.com/nginxinc/kubernetes-ingress/)
+- [NGINX Gateway Fabric](https://github.com/nginxinc/nginx-gateway-fabric)
+
+You can find documentation source code in the `docs` or `site` subdirectories.
 
 ## F5 Contributor License Agreement
 
-F5 requires all external contributors to agree to the terms of the [F5 CLA](./CLA/cla-markdown.md), before any of their changes can be incorporated into an F5 Open Source repository.
+F5 requires all external contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)) before any of their changes can be incorporated into an F5 Open Source repository.
 
-If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future Pull or Merge Requests.
+If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future PRs.

CHANGELOG.md

@@ -1,14 +1,15 @@
+# Contributing guidelines for experts
+
 If you want to contribute, know Git, and can work from the command line, this page can help you. As noted in the [README](./README.md), we create source content for our documentation in Markdown.
 
 Once you add and/or edit our Markdown source files, you can build the content locally as described on this page.
 Before you [Submit a Pull Request](#submit-a-pull-request), we recommend that you first:
 
 - Set up our [Static site generator](#static-site-generator)
-- Review how to [Include images](#include-images)
-- Review our [Git style guide](#git-style-guide)
+- If you want to add images, review how to [Include images](#include-images)
 - Learn how to [Build documentation locally](#build-documentation-locally)
 
-## Static Site Generator
+## Static site generator
 
 You will need to install Hugo to build and preview docs in your local development environment.
 Refer to the [Hugo installation instructions](https://gohugo.io/getting-started/installing/) for more information.
@@ -21,13 +22,14 @@ When you set up an image, this is the standard format:
 
 {{< img src="path/to/images/file-name.png" alt="descriptive text for screenreaders" >}}
 
+You'll find images in the [static](../static) subdirectory, in a directory assocaited with the documentation. For example, if you've set up the `file-name.png`
+image, you should copy that file to the `static/path/to/images` directory.
+
 ## Build documentation locally
 
 To build and preview docs in your local development environment, you need to install Hugo.
 Refer to the [Hugo installation instructions](https://gohugo.io/getting-started/installing/) for more information.
 
-**NOTE**: We are currently running [Hugo v0.115.3](https://github.com/gohugoio/hugo/releases/tag/v0.115.3) in production. If you run a different version of Hugo (older or newer), you might see unexpected errors.
-
 ## Submit a Pull Request
 
 Follow this plan to contribute a change to NGINX source code:
@@ -37,35 +39,7 @@ Follow this plan to contribute a change to NGINX source code:
 - Implement your changes in this branch
 - Submit a pull request (PR) when your changes are tested and ready for review
 
-### Git Style Guide
-
-- Keep a clean, concise and meaningful git commit history on your branch, rebasing locally and squashing before
-  submitting a PR
-- Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/>
-  and summarized in the next few points:
-
-  - In the subject line, use the present tense ("Add feature" not "Added feature")
-  - In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...")
-  - Limit the subject line to 72 characters or less
-  - Reference issues and pull requests liberally after the subject line
-  - Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in
-    your text editor to write a good message instead of `git commit -am`)
-
 ### Add new docs
-<!--
-#### Generate a new doc file using Hugo
-
-To create a new doc file that contains all of the pre-configured Hugo front-matter and the docs task template, run the following command:
-
-`hugo new <SECTIONNAME>/<FILENAME>.<FORMAT>`
-
-For example:
-
-`hugo new getting-started/install.md`
-
-The default template -- task -- should be used for most docs. To create docs using the other content templates, you can use the `--kind` flag:
-
-`hugo new tutorials/deploy.md --kind tutorial` -->
 
 Consistent with the [Diataxis](https://diataxis.fr) framework, our documentation includes the following content types:
 

CONTRIBUTING.md

@@ -10,12 +10,10 @@
 
 If you want to contribute to F5 NGINX documentation, you've come to the right place. We've organized a series of README-type files to help you get started:
 
-- [Get started](/GET_STARTED.md) to help you get started with NGINX and our documentation.
 - [Contributing](/CONTRIBUTING.md) describes how you can contribute to our documentation.
-  - [Contributing with Git](/CONTRIBUTING_GIT.md) describes how you can contribute (and check your work) with Git and command line tools.
+  - [Contributing guidelines for experts](/CONTRIBUTING_DOCS.md) describes how you can contribute (and check your work) with Hugo, our static site generator
 - [Code of Conduct](/CODE_OF_CONDUCT.md) describes expectations in the NGINX open source community.
-- [Creative Commons License](/LICENSE) shows the Creative Commons license associated with work on this repository.
-- [Prerequisties](/PREREQUISITES.md) lists the hardware and software that you need to get started with NGINX.
+- [License](/LICENSE) shows the license associated with work on this repository.
 - [Security](/SECURITY.md) describes the procedures we would like you to follow if you find a security issue.
 - [Support](/SUPPORT.md) lists how you can get support as a customer or a community member.
 

CONTRIBUTING_GIT.md renamed to CONTRIBUTING_DOCS.md

@@ -8,21 +8,10 @@ Don't know how something in this project works? Curious if this project can achi
 
 Alternatively, open a [discussion](https://github.com/nginxinc/oss-docs/discussions) in this repository.
 
-If you know the answer, open a pull request!
-<!-- Add a link to GH issues, Discourse, F5 Dev Central, Qualtrix?-->
-
 ## NGINX Specific Questions and/or Issues
 
 This isn't the right place to get support for NGINX specific questions, but the following resources are available below. Thanks for your understanding!
 
-<!-- ### Discourse
-
-We have a community [Slack](https://nginxcommunity.slack.com/)!
-
-If you are not a member, click [here](https://community.nginx.org/joinslack) to sign up. (Let us know if the link does not seem to be working at <nginx-oss-community@f5.com>!)
-
-Once you join, check out the `#beginner-questions` and `nginx-users` channels :) -->
-
 ### Mailing List
 
 Want to get in touch with the NGINX development team directly? Try using the relevant mailing list found at <https://mailman.nginx.org/mailman3/lists/>!