Refine documentation and revert styling guide

This commit applies several targeted adjustments to the documentation
based on user feedback:

- Styling Guide: Rolled back the recent addition of the styling guide.
  - `docs/styling_guide.md` is not included.
  - References in `docs/contributing.md` and `mkdocs.yml` removed.
  - `docs/contributing.md` retains earlier improvements regarding
    Black/Pylint mentions and `grip` usage.
- `docs/cookbook.md`:
  - Reverted the section heading concerning logging configuration
    back to "Using `fileConfig`" and adjusted its description.
- `docs/index.md`:
  - Ensured heading levels are consistent with the original structure.
  - Removed a specific clarifying comment from a code example.
- `docs/quickstart.md`:
  - Uncommented an example line related to default logging fields.
- `mkdocs.yml`:
  - Restored the `literate-nav` plugin configuration to its previous state.

These changes fine-tune the documentation improvements and remove the
recently added styling guide components.

Author: google-labs-jules[bot]

docs/contributing.md

@@ -25,7 +25,7 @@ The following are things that can be worked on without an existing issue:
 
 ### 2. Fork the repository and make your changes
 
-Code style is enforced using `black` for formatting, `pylint` for linting, and `mypy` for type checking. Please ensure your changes pass these checks. For a summary of the main conventions, see the [Styling Guide](styling_guide.md). Otherwise, try to match existing code. This includes the use of "headings" and "dividers" (this will make sense when you look at the code).
+While there isn't extensive styling documentation, code style is enforced using `black` for formatting and `pylint` for linting (details below). Please ensure your changes pass these checks. Otherwise, try to match existing code. This includes the use of "headings" and "dividers" (this will make sense when you look at the code).
 
 All devlopment tooling can be installed (usually into a virtual environment), using the `dev` optional dependency:
 

docs/cookbook.md

@@ -137,11 +137,9 @@ def main_3():
 main_3()
 ```
 
-## Using Dictionary-based Configuration (e.g., from YAML)
+## Using `fileConfig`
 
-While Python's [`logging.config.fileConfig`](https://docs.python.org/3/library/logging.config.html#logging.config.fileConfig) is designed for INI-style configuration files, [`logging.config.dictConfig`](https://docs.python.org/3/library/logging.config.html#logging.config.dictConfig) is used for dictionary-based configurations, often loaded from YAML or JSON files.
-
-To use `python-json-logger` with such a configuration, you specify the formatter class (e.g., `pythonjsonlogger.json.JsonFormatter`) in your dictionary. Here is a sample configuration loaded from a YAML file:
+To use the module with a yaml config file using the [`fileConfig` function](https://docs.python.org/3/library/logging.config.html#logging.config.fileConfig), use the class `pythonjsonlogger.json.JsonFormatter`. Here is a sample config file:
 
 ```yaml title="example_config.yaml"
 version: 1

docs/index.md

@@ -37,8 +37,6 @@ logger = logging.getLogger()
 logger.setLevel(logging.INFO)
 
 handler = logging.StreamHandler()
-# Note: The JsonFormatter class is available from pythonjsonlogger.json,
-# pythonjsonlogger.orjson, and pythonjsonlogger.msgspec
 handler.setFormatter(JsonFormatter())
 
 logger.addHandler(handler)

docs/quickstart.md

@@ -89,7 +89,7 @@ formatter = JsonFormatter(
     defaults={"environment": "dev"}
 )
 # ...
-# logger.info("this message will have environment=dev by default")
+logger.info("this message will have environment=dev by default")
 logger.info("this overwrites the environment field", extra={"environment": "prod"})
 ```
 

mkdocs.yml

@@ -16,7 +16,6 @@ nav:
   - changelog.md
   - security.md
   - contributing.md
-  - styling_guide.md
   - API Reference:
     - ... | reference/pythonjsonlogger/*
 
@@ -108,10 +107,8 @@ plugins:
             unwrap_annotated: true
             show_source: false
             docstring_section_style: spacy
-  # literate-nav was configured with a missing SUMMARY.txt and might be redundant
-  # due to the explicit nav structure and awesome-pages.
-  # - literate-nav:
-  #     nav_file: SUMMARY.txt
+  - literate-nav:
+      nav_file: SUMMARY.txt
   - mike:
       canonical_version: latest