Rewrite the Directory Strategies section

Author: zsol

docs/reference/storage.md

@@ -6,61 +6,24 @@ uv persists data in several locations on your system.
 
 uv follows platform conventions (like
 [XDG](https://specifications.freedesktop.org/basedir-spec/latest/) on Unix) for determining where to
-store different types of data.
+store different types of data. Generally, it's best to configure these rather than each uv-specific storage location.
 
-Generally, it's best to configure these rather than each uv-specific storage location.
+Here's a summary of the locations uv uses on each platform:
 
-### Cache
+| Purpose | Unix Default | Windows Default |
+|---------|--------------|-----------------|
+| Temporary files and caches | `$XDG_CACHE_HOME/uv` or `~/.cache/uv` as a fallback | `%LOCALAPPDATA%\uv\cache` |
+| Persistent data | `$XDG_DATA_HOME/uv` or `~/.local/share/uv` as a fallback | `%APPDATA%\uv\data` if exists, otherwise `%APPDATA%\uv` |
+| User configuration files | `$XDG_CONFIG_HOME/uv` or `~/.config/uv` as a fallback | `%APPDATA%\uv` |
+| System configuration files | `$XDG_CONFIG_DIRS/uv` or `/etc/uv` as a fallback | `%PROGRAMDATA%\uv` |
+| Executables | `$XDG_BIN_HOME` or `$XDG_DATA_HOME/../bin` or `~/.local/bin` as a fallback | same as on Unix |
+| Environment | `.venv` in the project or workspace directory | same as on Unix |
 
-Storage location for temporary files and caches:
-
-- `$XDG_CACHE_HOME/uv` or `~/.cache/uv` on Unix systems
-- `%LOCALAPPDATA%\uv\cache` on Windows
-
-### Data
-
-Storage location for persistent application data:
-
-- `$XDG_DATA_HOME/uv` or `~/.local/share/uv` on Unix systems
-- `%APPDATA%\uv\data` on Windows
-- `.uv` in the working directory as a fallback
-
-### Config
-
-Storage location for user configuration files:
-
-- `$XDG_CONFIG_HOME/uv` or `~/.config/uv` on Unix systems
-- `%APPDATA%\uv` on Windows
-
-For system configuration files:
-
-- `$XDG_CONFIG_DIRS/uv` or `/etc/uv` on Unix systems
-- `%PROGRAMDATA%\uv` on Windows
-
-### Executables
-
-Unlike other directory schemes above, uv follows the XDG standard on _all platforms_ by default,
-notably including Windows and macOS, as there is no clear alternative location to place executables
-on these platforms.
-
-The installation directory is determined by consulting the following environment variables if
-they're set:
-
-- `$XDG_BIN_HOME`
-- `$XDG_DATA_HOME/../bin`
-- `~/.local/bin`
-
-The above can be overridden by an environment variable specific to [tools](#tool-executables) or
-[Python executables](#python-executables).
-
-uv itself is also installed in the above folders by [the installer](./installer.md), and it can be
-overridden via the `UV_INSTALL_DIR` environment variable.
-
-## Cache
+## Caching
 
 uv uses a local cache to avoid re-downloading and re-building dependencies.
 
-By default, the cache is stored in the [cache home](#cache), which can be overridden via command
+By default, the cache is stored according to [the table above](#directory-strategies), and can be overridden via command
 line arguments, environment variables, or settings as detailed in
 [the cache documentation](../concepts/cache.md#cache-directory).
 
@@ -73,24 +36,24 @@ It is important for performance for the cache directory to be on the same filesy
 
 uv can download and manage Python versions.
 
-By default, Python versions are stored in the [data home](#data) in a `python/` subdirectory, e.g.,
+By default, Python versions are stored as persistant data according to [the table above](#directory-strategies), in a `python/` subdirectory, e.g.,
 `~/.local/share/uv/python`.
 
 Use `uv python dir` to show the Python installation directory.
 
 Use the `UV_PYTHON_INSTALL_DIR` environment variable to configure the installation directory.
 
-For more details, see the [Python versions documentation](../concepts/python-versions.md).
+!!! note
 
-### Python executables
+    Changing where Python is installed will not be automatically reflected in existing virtual environments; they will keep referring to the old location, and will need to be updated manually (e.g. by re-creating them).
 
-!!! note
+For more details on how uv manages Python versions, see the [dedicated documentation page](../concepts/python-versions.md).
 
-    This feature is in preview, and is not enabled without `--preview` or `UV_PREVIEW`.
+### Python executables
 
 uv also supports adding Python executables to your `PATH`.
 
-By default, Python executables are stored in the [bin home](#executables).
+By default, Python executables are stored according to [the table above](#directory-strategies).
 
 Use `uv python dir --bin` to show the Python executable directory.
 
@@ -100,7 +63,7 @@ Use the `UV_PYTHON_BIN_DIR` environment variable to configure the executable dir
 
 uv can install Python applications as tools using `uv tool install`.
 
-By default, tools are installed in the [data home](#data) under a `tools/` subdirectory, e.g.,
+By default, tools are installed as persistant data according to [the table above](#directory-strategies), under a `tools/` subdirectory, e.g.,
 `~/.local/share/uv/tools`
 
 Use `uv tool dir` to show the tool installation directory.
@@ -113,28 +76,33 @@ For more details, see the [tools documentation](../concepts/tools.md).
 
 When installing tools, uv will add tools to your `PATH`.
 
-By default, tool executables are stored in the [bin home](#executables).
+By default, tool executables are stored according to [the table above](#directory-strategies).
 
 Use `uv tool dir --bin` to show the tool executable directory.
 
 Use the `UV_TOOL_BIN_DIR` environment variable to configure the executable directory.
 
+## uv
+
+uv itself is also installed by [the installer](./installer.md) into the executables folder from [the table above](#directory-strategies), and it can be
+overridden via the `UV_INSTALL_DIR` environment variable.
+
 ## Configuration
 
 uv's behavior (including most of the storage locations on this page) can be configured through
 configuration files stored in standard locations.
 
-Configuration files are located in the [config directories](#config).
+Configuration files are located in the corresponding system- or user-specific  locations from [the table above](#directory-strategies).
 
 For more details, see the [configuration files documentation](../concepts/configuration-files.md).
 
 ## Project environments
 
 uv creates virtual environments for projects to isolate their dependencies.
 
-By default, project virtual environments are created in `.venv` within the project directory.
+By default, project virtual environments are created in `.venv` within the project directory, and a workspace's environment is created with the same name in the workspace root.
 
-Use the `UV_PROJECT_ENVIRONMENT` environment variable to override this location.
+Use the `UV_PROJECT_ENVIRONMENT` environment variable to override this location, which is should be either an absolute path, or relative to the workspace root.
 
 For more details, see the
 [projects environment documentation](../concepts/projects/config.md#project-environment-path).