docs: redo docs, use zensical, and follow diatrix

Author: theskumar

.github/workflows/release.yml

@@ -38,7 +38,7 @@ jobs:
         run: |
           pip install -r requirements-docs.txt
           pip install -e .
-          mkdocs build
+          zensical build
 
       - name: Deploy to GitHub Pages
         uses: peaceiris/actions-gh-pages@v4

.gitignore

@@ -67,16 +67,6 @@ coverage.xml
 local_settings.py
 db.sqlite3
 
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
 # PyBuilder
 target/
 
@@ -90,9 +80,6 @@ ipython_config.py
 # pyenv
 .python-version
 
-# celery beat schedule file
-celerybeat-schedule
-
 # SageMath parsed files
 *.sage.py
 
@@ -112,7 +99,7 @@ venv.bak/
 # Rope project settings
 .ropeproject
 
-# mkdocs documentation
+# zensical documentation
 /site
 
 # mypy
@@ -125,5 +112,6 @@ dmypy.json
 
 ### Python Patch ###
 .venv/
+uv.lock
 
 # End of https://www.gitignore.io/api/python

CHANGELOG.md

@@ -488,6 +488,9 @@ os.PathLike]` instead of just `os.PathLike` (#347 by [@bbc2]).
 [@JYOuyang]: https://github.com/JYOuyang
 [@burnout-projects]: https://github.com/burnout-projects
 [@cpackham-atlnz]: https://github.com/cpackham-atlnz
+
+<!-- Releases -->
+
 [Unreleased]: https://github.com/theskumar/python-dotenv/compare/v1.2.2...HEAD
 [1.2.2]: https://github.com/theskumar/python-dotenv/compare/v1.2.1...v1.2.2
 [1.2.1]: https://github.com/theskumar/python-dotenv/compare/v1.2.0...v1.2.1

CONTRIBUTING.md

@@ -1,5 +1,4 @@
-Contributing
-============
+# Contributing
 
 All the contributions are welcome! Please open [an
 issue](https://github.com/theskumar/python-dotenv/issues/new) or send us
@@ -18,18 +17,15 @@ or with [tox](https://pypi.org/project/tox/) installed:
 
     $ tox
 
-
 Use of pre-commit is recommended:
 
     $ uv run precommit install
 
-
-Documentation is published with [mkdocs]():
+Documentation is published with [zensical](https://zensical.org/) and follows
+the approach established by [Diátaxis](https://diataxis.fr/):
 
 ```shell
-$ uv pip install -r requirements-docs.txt
-$ uv pip install -e .
-$ uv run mkdocs serve
+$ make serve-docs
 ```
 
 Open http://127.0.0.1:8000/ to view the documentation locally.

Makefile

@@ -33,3 +33,8 @@ coverage:
 
 coverage-html: coverage
 	coverage html
+
+serve-docs:
+	uv pip install -r requirements-docs.txt
+	uv pip install -e .
+	uv run zensical serve

README.md

@@ -7,17 +7,7 @@ python-dotenv reads key-value pairs from a `.env` file and can set them as
 environment variables. It helps in the development of applications following the
 [12-factor](https://12factor.net/) principles.
 
-- [Getting Started](#getting-started)
-- [Other Use Cases](#other-use-cases)
-  - [Load configuration without altering the environment](#load-configuration-without-altering-the-environment)
-  - [Parse configuration as a stream](#parse-configuration-as-a-stream)
-  - [Load .env files in IPython](#load-env-files-in-ipython)
-- [Command-line Interface](#command-line-interface)
-- [File format](#file-format)
-  - [Multiline values](#multiline-values)
-  - [Variable expansion](#variable-expansion)
-- [Related Projects](#related-projects)
-- [Acknowledgements](#acknowledgements)
+> **[Read the full documentation](https://theskumar.github.io/python-dotenv/)**
 
 ## Getting Started
 
@@ -73,163 +63,9 @@ like `${DOMAIN}`, as bare variables such as `$DOMAIN` are not expanded.
 You will probably want to add `.env` to your `.gitignore`, especially if it
 contains secrets like a password.
 
-See the section "[File format](#file-format)" below for more information about what you can write in a `.env` file.
-
-## Other Use Cases
-
-### Load configuration without altering the environment
-
-The function `dotenv_values` works more or less the same way as `load_dotenv`,
-except it doesn't touch the environment, it just returns a `dict` with the
-values parsed from the `.env` file.
-
-```python
-from dotenv import dotenv_values
-
-config = dotenv_values(".env")  # config = {"USER": "foo", "EMAIL": "foo@example.org"}
-```
-
-This notably enables advanced configuration management:
-
-```python
-import os
-from dotenv import dotenv_values
-
-config = {
-    **dotenv_values(".env.shared"),  # load shared development variables
-    **dotenv_values(".env.secret"),  # load sensitive variables
-    **os.environ,  # override loaded values with environment variables
-}
-```
-
-### Parse configuration as a stream
-
-`load_dotenv` and `dotenv_values` accept [streams][python_streams] via their
-`stream` argument. It is thus possible to load the variables from sources other
-than the filesystem (e.g. the network).
-
-```python
-from io import StringIO
-
-from dotenv import load_dotenv
-
-config = StringIO("USER=foo\nEMAIL=foo@example.org")
-load_dotenv(stream=config)
-```
-
-### Load .env files in IPython
-
-You can use dotenv in IPython. By default, it will use `find_dotenv` to search for a
-`.env` file:
-
-```python
-%load_ext dotenv
-%dotenv
-```
-
-You can also specify a path:
-
-```python
-%dotenv relative/or/absolute/path/to/.env
-```
-
-Optional flags:
-
-- `-o` to override existing variables.
-- `-v` for increased verbosity.
-
-### Disable load_dotenv
-
-Set `PYTHON_DOTENV_DISABLED=1` to disable `load_dotenv()` from loading .env
-files or streams. Useful when you can't modify third-party package calls or in
-production.
-
-## Command-line Interface
-
-A CLI interface `dotenv` is also included, which helps you manipulate the `.env`
-file without manually opening it.
-
-```shell
-$ pip install "python-dotenv[cli]"
-$ dotenv set USER foo
-$ dotenv set EMAIL foo@example.org
-$ dotenv list
-USER=foo
-EMAIL=foo@example.org
-$ dotenv list --format=json
-{
-  "USER": "foo",
-  "EMAIL": "foo@example.org"
-}
-$ dotenv run -- python foo.py
-```
-
-Run `dotenv --help` for more information about the options and subcommands.
-
-## File format
-
-The format is not formally specified and still improves over time. That being
-said, `.env` files should mostly look like Bash files. Reading from FIFOs (named
-pipes) on Unix systems is also supported.
-
-Keys can be unquoted or single-quoted. Values can be unquoted, single- or
-double-quoted. Spaces before and after keys, equal signs, and values are
-ignored. Values can be followed by a comment. Lines can start with the `export`
-directive, which does not affect their interpretation.
-
-Allowed escape sequences:
-
-- in single-quoted values: `\\`, `\'`
-- in double-quoted values: `\\`, `\'`, `\"`, `\a`, `\b`, `\f`, `\n`, `\r`, `\t`, `\v`
-
-### Multiline values
-
-It is possible for single- or double-quoted values to span multiple lines. The
-following examples are equivalent:
-
-```bash
-FOO="first line
-second line"
-```
-
-```bash
-FOO="first line\nsecond line"
-```
-
-### Variable without a value
-
-A variable can have no value:
-
-```bash
-FOO
-```
-
-It results in `dotenv_values` associating that variable name with the value
-`None` (e.g. `{"FOO": None}`. `load_dotenv`, on the other hand, simply ignores
-such variables.
-
-This shouldn't be confused with `FOO=`, in which case the variable is associated
-with the empty string.
-
-### Variable expansion
-
-python-dotenv can interpolate variables using POSIX variable expansion.
-
-With `load_dotenv(override=True)` or `dotenv_values()`, the value of a variable
-is the first of the values defined in the following list:
-
-- Value of that variable in the `.env` file.
-- Value of that variable in the environment.
-- Default value, if provided.
-- Empty string.
-
-With `load_dotenv(override=False)`, the value of a variable is the first of the
-values defined in the following list:
-
-- Value of that variable in the environment.
-- Value of that variable in the `.env` file.
-- Default value, if provided.
-- Empty string.
+See the [file format specification](https://theskumar.github.io/python-dotenv/reference/file-format/)
+for full details on `.env` syntax, multiline values, escape sequences, and
+variable expansion.
 
 ## Related Projects
 

docs/changelog.md

@@ -0,0 +1 @@
+--8<-- "CHANGELOG.md"

docs/changelog.md

@@ -0,0 +1 @@
+--8<-- "contributing.md"