docs: Community READMEs (and more), iteration 1

Author: mjang

.github/CODEOWNERS

@@ -1,3 +1,31 @@
-# Main global owner #
-#####################
-*
+# Each of these groups of CODEOWNERS have approval and merge authority over 
+# 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 `@`)
+# to the list of "Reviewers."
+#
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+# *.js    @js-owner #This is an inline comment.
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# DocOps
+*                           @nginxinc/nginx-docs
+# NGINX Plus
+content/nginx/*             @nginxinc/plus-docs-approvers
+# NGINX Agent
+content/nginx/nms/agent/*   @nginxinc/agent-docs-approvers
+# NGINX One
+content/nginx-one/*         @nginxinc/one-docs-approvers
+# NGINX Instance Manager
+content/nms/nim/*           @nginxinc/nim-docs-approvers
+content/nim/*               @nginxinc/nim-docs-approvers
+# NGINX App Protect WAF
+content/nap-waf/*           @nginxinc/nap-docs-approvers
+data/nap-waf/*              @nginxinc/nap-docs-approvers
+# NGINX App Protect DoS
+content/nap-dos/*           @nginxinc/dos-docs-approvers

CHANGELOG.md

@@ -1,5 +1,8 @@
 # Changelog
 
+<!-- While we have a changelog for current docs at https://github.com/nginxinc/docs/blob/main/CHANGELOG.md, I'm not convinced -->
+
 ## 1.0.0 (Month Date, Year)
 
-Initial release of the NGINX template repository.
+Initial open source release of the documentation repository for premium NGINX products. The content was previously in a closed repository.
+<!-- Is "premium" the right word? -->

CONTRIBUTING.md

@@ -1,57 +1,22 @@
-# Contributing Guidelines
+# Contributing guidelines
 
-The following is a set of guidelines for contributing to this project. We really appreciate that you are considering contributing!
+The following is a set of guidelines for contributing to this project. We really appreciate your desire to contribute!
 
-#### Table Of Contents
-
-[Getting Started](#getting-started)
-
-[Contributing](#contributing)
-
-[Code Guidelines](#code-guidelines)
-
-[Code of Conduct](/CODE_OF_CONDUCT.md)
-
-## Getting Started
-
-Follow the instructions on the README's [Getting Started](/README.md#Getting-Started) section to get this project up and running.
-
-<!-- ### Project Structure (OPTIONAL) -->
-
-## Contributing
-
-### Report a Bug
-
-To report a bug, open an issue on GitHub with the label `bug` using the available bug report issue template. Please ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using our [security policy](/SECURITY.md).**
-
-### Suggest a Feature or Enhancement
-
-To suggest a feature or enhancement, please create an issue on GitHub with the label `enhancement` using the available [feature request template](/.github/feature_request_template.md). Please ensure the feature or enhancement has not already been suggested.
-
-### Open a Pull Request (PR)
-
-- Fork the repo, create a branch, implement your changes, add any relevant tests, and submit a PR when your changes are **tested** and ready for review.
-- Fill in the [PR template](/.github/pull_request_template.md).
-
-**Note:** If you'd like to implement a new feature, please consider creating a [feature request issue](/.github/feature_request_template.md) first to start a discussion about the feature.
-
-#### F5 Contributor License Agreement (CLA)
+## F5 Contributor License Agreement (CLA)
 
 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 PRs.
+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.
+
+## Options to get started
 
-## Code Guidelines
+<!-- Separate doc pages, CONTRIBUTING_GIT.md and CONTRIBUTING_other.md. If we use Cloud Cannon, maybe we can link to their docs. For now, I'll. -->
 
-<!-- ### Go/Python/Bash/etc... Guidelines (OPTIONAL) -->
+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? 
 
-### Git Guidelines
+We're working on alternative contribution methods, described in CONTRIBUTING_OTHER.md
+-->
 
-- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR.
-- If possible and/or relevant, use the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format when writing a commit message, so that changelogs can be automatically generated.
-- 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`).
+Alternatively, you're welcome to highight problems with our documentation as
+described in our [support](./SUPPORT.md) page.

CONTRIBUTING_GIT.md

@@ -0,0 +1,63 @@
+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.
+
+## Static Site Generator (Hugo)
+
+We build our documentation with the [Hugo](https://gohugo.io/) static site generator. 
+
+## Images and downloads
+
+When you set up an image, this is the standard format:
+
+{{< img src="path/to/images/file-name.png" alt="descriptive text for screenreaders" >}}
+
+## 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.
+
+### Local docs development
+
+To build the docs locally, run the desired `make` command from the docs directory:
+
+```text
+make docs           -   runs a local hugo server so you can view docs in your browser while you work
+make hugo-mod       -   cleans the Hugo module cache and fetches the latest version of the theme module
+make docs-drafts    -   runs the local hugo server and includes all docs marked with `draft: true`
+make clean          -   removes the local `public` directory, which is the default output path used by Hugo
+```
+
+### 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:
+
+- concept: Helps a customer learn about a specific feature or feature set.
+- tutorial: Walks a customer through an example use case scenario; results in a functional PoC environment.
+- reference: Describes an API, command line tool, config options, etc.; should be generated automatically from source code. 
+- troubleshooting: Helps a customer solve a specific problem.
+- openapi: Contains front-matter and shortcode for rendering an openapi.yaml spec.
+
+### How to format docs
+
+#### How to format internal links
+
+Format links as [Hugo `refs`](https://gohugo.io/content-management/cross-references/). 
+
+- File extensions are optional.

GET_STARTED.md

@@ -0,0 +1,13 @@
+## Get Started
+
+You can find F5 NGINX docs at https://docs.nginx.com. You can use these docs to install and configure both open source and F5 NGINX products.
+
+This repository is focused on NGINX documentation. Each NGNIX product and module includes documentation on how you can install, and yes, get started with the product.
+
+Many of our products are open source. If you want to try one of our other products, you can:
+
+- Get a [trial license](https://www.f5.com/trials)
+  - Use the procedures in our [NGINX Solutions](https://docs.nginx.com/solutions/) site to download, install, and activate the product of your choice.
+
+The same procedures apply if you have a paid subscription.
+<!-- Ideal world, I'd include links to "Get started" or "Install" procedures for each product/module. -->