fix docs build and docs around standards, towncrier, etc.

Author: jeffkala

docs/admin/install.md

@@ -11,7 +11,7 @@ Option 2: Manually install via Poetry.
 ```
 git clone https://github.com/networktocode/pyntc.git
 cd pyntc
-pip install poetry
+curl -sSL https://install.python-poetry.org | python3 -
 poetry install
 ```
 

docs/dev/contributing.md

@@ -4,15 +4,44 @@ Pull requests are welcomed and automatically built and tested against multiple v
 
 Except for unit tests, testing is only supported on Python 3.9.
 
-The project is packaged with a light development environment based on `Docker` to help with the local development of the project and to run tests within  GitHub Actions.
+The project is packaged with a light development environment based on `Docker` to help with the local development of the project and to run tests within GitHub Actions.
 
-The project is following Network to Code software development guidelines and are leveraging the following:
+The project is following Network to Code software development guidelines and is leveraging the following:
 
-- Black, Pylint, Bandit, flake8, and pydocstyle for Python linting and formatting.
-- pytest, coverage, and unittest for unit tests.
+- Python linting and formatting: `pylint` and `ruff`.
+- YAML linting is done with `yamllint`.
 
 Documentation is built using [mkdocs](https://www.mkdocs.org/). The [Docker based development environment](dev_environment.md#docker-development-environment) can be started by running `invoke docs` [http://localhost:8001](http://localhost:8001) that auto-refreshes when you make any changes to your local files.
 
+## Creating Changelog Fragments
+
+All pull requests to `next` or `develop` must include a changelog fragment file in the `./changes` directory. To create a fragment, use your GitHub issue number and fragment type as the filename. For example, `2362.added`. Valid fragment types are `added`, `changed`, `deprecated`, `fixed`, `removed`, and `security`. The change summary is added to the file in plain text. Change summaries should be complete sentences, starting with a capital letter and ending with a period, and be in past tense. Each line of the change fragment will generate a single change entry in the release notes. Use multiple lines in the same file if your change needs to generate multiple release notes in the same category. If the change needs to create multiple entries in separate categories, create multiple files.
+
+!!! example
+
+    **Wrong**
+    ```plaintext title="changes/1234.fixed"
+    fix critical bug in documentation
+    ```
+
+    **Right**
+    ```plaintext title="changes/1234.fixed"
+    Fixed critical bug in documentation.
+    ```
+
+!!! example "Multiple Entry Example"
+
+    This will generate 2 entries in the `fixed` category and one entry in the `changed` category.
+
+    ```plaintext title="changes/1234.fixed"
+    Fixed critical bug in documentation.
+    Fixed release notes generation.
+    ```
+
+    ```plaintext title="changes/1234.changed"
+    Changed release notes generation.
+    ```
+
 ## Branching Policy
 
 The branching policy includes the following tenets:
@@ -45,4 +74,4 @@ When a new release is created the following should happen.
 - A post release PR is created with.
     - Change the version from `<major>.<minor>.<patch>` to `<major>.<minor>.<patch + 1>-beta` pyproject.toml.
     - Set the PR to the `develop`.
-    - Once tests pass, merge.
+    - Once tests pass, merge.

docs/dev/dev_environment.md

@@ -32,7 +32,6 @@ Once you have Poetry and Docker installed you can run the following commands (in
 ```shell
 poetry shell
 poetry install
-cp development/creds.example.env development/creds.env
 invoke build
 invoke start
 ```
@@ -51,7 +50,7 @@ Poetry is used in lieu of the "virtualenv" commands and is leveraged in both env
 The `pyproject.toml` file outlines all of the relevant dependencies for the project:
 
 - `tool.poetry.dependencies` - the main list of dependencies.
-- `tool.poetry.dev-dependencies` - development dependencies, to facilitate linting, testing, and documentation building.
+- `tool.poetry.group.dev.dependencies` - development dependencies, to facilitate linting, testing, and documentation building.
 
 The `poetry shell` command is used to create and enable a virtual environment managed by Poetry, so all commands ran going forward are executed within the virtual environment. This is similar to running the `source venv/bin/activate` command with virtualenvs. To install project dependencies in the virtual environment, you should run `poetry install` - this will install **both** project and development dependencies.
 
@@ -82,21 +81,18 @@ Each command can be executed with `invoke <command>`. Each command also has its
 ### Utility
 
 ```
-  cli                Enter the image to perform troubleshooting or dev work.
-  clean-container    Remove stopped containers that source for image `pyntc:`
+  cli                       Enter the image to perform troubleshooting or dev work.
+  clean                     Remove stopped containers that source for image `pyntc:`
+  generate-release-notes    Generate Release Notes using Towncrier.
 ```
 
 ### Testing
 
 ```
-  bandit             Run bandit to validate basic static code security analysis.
-  black              Run black to check that Python files adhere to its style standards.
-  coverage           Run the coverage report against pytest.
-  flake8             Run flake8 to check that Python files adhere to its style standards.
-  mypy               Run mypy to validate typing-hints.
-  pylint             Run pylint code analysis.
-  pydocstyle         Run pydocstyle to validate docstring formatting adheres to NTC defined standards.
-  pytest             Run pytest for the specified name and Python version.
-  tests              Run all tests for the specified name and Python version.
-  yamllint           Run yamllint to validate formatting adheres to NTC defined YAML standards.
+  autoformat (a)    Run code autoformatting.
+  pylint            Run pylint for the specified name and Python version.
+  ruff              Run ruff to perform code formatting and/or linting.
+  pytest            Run pytest for the specified name and Python version.
+  tests             Run all tests for the specified name and Python version.
+  yamllint          Run yamllint to validate formatting adheres to NTC defined YAML standards.
 ```

docs/requirements.txt

@@ -1,9 +1,9 @@
 mkdocs==1.6.0
-# Material for MkDocs theme
 mkdocs-material==9.5.32
-# Render custom markdown for version added/changed/remove notes
-mkdocs-version-annotations==1.0.0
-# Automatic documentation from sources, for MkDocs
-mkdocstrings==0.25.2
+markdown-version-annotations==1.0.1
+griffe==1.1.1
 mkdocstrings-python==1.10.8
-griffe==1.1.1
+mkdocstrings==0.25.2
+mkdocs-autorefs==1.2.0
+# Unique requirements
+mkdocs-python-classy==0.1.3

mkdocs.yml

@@ -14,13 +14,14 @@ theme:
     - "python"
     - "yaml"
   features:
-    - "navigation.tracking"
+    - "content.code.copy"
+    - "navigation.indexes"
     - "navigation.tabs"
     - "navigation.tabs.sticky"
-    - "search.suggest"
+    - "navigation.tracking"
     - "search.highlight"
     - "search.share"
-    - "navigation.indexes"
+    - "search.suggest"
   favicon: "assets/favicon.ico"
   logo: "assets/networktocode_logo.svg"
   palette:
@@ -88,7 +89,10 @@ plugins:
         python:
           paths: ["."]
           options:
+            heading_level: 1
             show_root_heading: true
+            show_root_members_full_path: true
+            show_source: false
 watch:
   - "README.md"
 

poetry.lock

@@ -43,13 +43,7 @@ pyntc = 'pyntc.cli:main'
 requests_mock = "*"
 pytest = "*"
 mock = "*"
-mkdocs = "^1.6.0"
-mkdocs-material = "9.5.32"
-mkdocstrings = "0.25.2"
-mkdocstrings-python =  "1.10.8"
 griffe = "1.1.1"
-markdown-data-tables = "^1.0.0"
-mkdocs-version-annotations = "^1.0.0"
 pyyaml = "^6.0.1"
 pylint = "^3.1.0"
 yamllint = "^1.35.1"
@@ -58,6 +52,18 @@ toml = "^0.10.2"
 attrs = "^23.2.0"
 towncrier = "^24.8.0"
 ruff = "*"
+Markdown = "*"
+# Render custom markdown for version added/changed/remove notes
+mkdocs-version-annotations = "^1.0.0"
+# Rendering docs to HTML
+mkdocs = "^1.6.0"
+# Material for MkDocs theme
+mkdocs-material = "9.5.32"
+# Automatic documentation from sources, for MkDocs
+mkdocstrings = "0.25.2"
+mkdocstrings-python = "1.10.8"
+mkdocs-autorefs = "1.2.0"
+markdown-data-tables = "^1.0.0"
 
 [tool.pyntc]
 string_required = "some string"