refactor(docs): restructure with tabbed navigation

2026-01-28 22:01:24 +00:00 · 2025-09-28 13:09:19 -07:00
parent b7e0613ffb
commit 8d7ba0dd86
29 changed files with 1579 additions and 1241 deletions
--- a/docs/changelog.md
+++ b/docs/changelog.md
--- a/docs/library/tag_color.md
+++ b/docs/library/tag_color.md
@@ -2,7 +2,7 @@
 icon: material/palette
 ---

-# :material-palette: Tag Colors
+# :material-palette: Colors

 TagStudio features a variety of built-in tag colors, alongside the ability for users to create their own custom tag color palettes.

@@ -10,7 +10,7 @@ TagStudio features a variety of built-in tag colors, alongside the ability for u

 The Tag Color Manager is where you can create and manage your custom tag colors and associated namespaces. You can access the Tag Color Manager from the "File -> Manage Tag Colors" option in the menu bar.

-![Tag Color Manager](../assets/tag_color_manager.png)
+![Tag Color Manager](assets/tag_color_manager.png)

 ## Creating a Namespace

@@ -20,7 +20,7 @@ _\* Color pack sharing coming in a future update_

 To create your first namespace, either click the "New Namespace" button or the large button prompt underneath the built-in colors.

-![Create Namespace](../assets/create_namespace.png)
+![Create Namespace](assets/create_namespace.png)

 ### Name

@@ -40,7 +40,7 @@ Namespaces beginning with "tagstudio" are reserved by TagStudio and will automat

 Once you've created your first namespace, click the "+" button inside the namespace section to create a color. To edit a color that you've previously created, either click on the color name or right click and select "Edit Color" from the context menu.

-![Create Color (Primary Color)](../assets/custom_color_primary_only.png)
+![Create Color (Primary Color)](assets/custom_color_primary_only.png)

 ### Name

@@ -62,14 +62,14 @@ The primary color is used as the main tag color and by default is used as the ba

 By default, the secondary color is only used as an optional override for the tag text color. This color can be cleared by clicking the adjacent "Reset" button.

-![Create Color (Secondary Color)](../assets/custom_color_no_border.png)
+![Create Color (Secondary Color)](assets/custom_color_no_border.png)

 The secondary color can also be used as the tag border color by checking the "Use Secondary Color for Border" box.

-![Create Color (Use Secondary for Border)](../assets/custom_color_border.png)
+![Create Color (Use Secondary for Border)](assets/custom_color_border.png)

 ## Using Colors

 When editing a tag, click the tag color button to bring up the tag color selection panel. From here you can choose any built-in TagStudio color as well as any of your custom colors.

-![Tag Color Selection](../assets/tag_color_selection.png)
+![Tag Color Selection](assets/tag_color_selection.png)
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -0,0 +1,155 @@
+---
+icon: material/file-plus
+---
+
+# :material-file-plus: Contributing
+
+Thank you so much for showing interest in contributing to TagStudio! Here are a set of instructions and guidelines for contributing code or documentation to the project. This document will change over time, so make sure that your contributions still line up with the requirements here before submitting a pull request.
+
+## Getting Started
+
+-   Check the [Feature Roadmap](roadmap.md) page to see what priority features there are, the [FAQ](https://github.com/TagStudioDev/TagStudio/blob/main/README.md#faq), as well as the project's [Issues](https://github.com/TagStudioDev/TagStudio/issues) and [Pull Requests](https://github.com/TagStudioDev/TagStudio/pulls).
+-   If you'd like to add a feature that isn't on the feature roadmap or doesn't have an open issue, **PLEASE create a feature request** issue for it discussing your intentions so any feedback or important information can be given by the team first.
+    -   We don't want you wasting time developing a feature or making a change that can't/won't be added for any reason ranging from pre-existing refactors to design philosophy differences.
+-   **Please don't** create pull requests that consist of large refactors, _especially_ without discussing them with us first. These end up doing more harm than good for the project by continuously delaying progress and disrupting everyone else's work.
+-   If you wish to discuss TagStudio further, feel free to join the [Discord Server](https://discord.com/invite/hRNnVKhF2G)!
+
+### Contribution Checklist
+
+-   I've read the [Feature Roadmap](roadmap.md) page
+-   I've read the [FAQ](https://github.com/TagStudioDev/TagStudio/blob/main/README.md#faq)
+-   I've checked the project's [Issues](https://github.com/TagStudioDev/TagStudio/issues) and [Pull Requests](https://github.com/TagStudioDev/TagStudio/pulls)
+-   **I've created a new issue for my feature/fix _before_ starting work on it**, or have at least notified others in the relevant existing issue(s) of my intention to work on it
+-   I've set up my development environment including Ruff, Mypy, and PyTest
+-   I've read the CONTRIBUTING.md/Contributing page on the documentation site as well as the and/or [Style Guide](style.md)
+-   **_I mean it, I've found or created an issue for my feature/fix!_**
+
+<!-- prettier-ignore -->
+!!! note
+    If the fix is small and self-explanatory (i.e. a typo), then it doesn't require an issue to be opened first. Issue tracking is supposed to make our lives easier, not harder. Please use your best judgement to minimize the amount of work for everyone involved.
+
+## Creating a Development Environment
+
+If you wish to develop for TagStudio, you'll need to create a development environment by installing the required dependencies. You have a number of options depending on your level of experience and familiarly with existing Python toolchains.
+
+If you know what you're doing and have developed for Python projects in the past, you can get started quickly with the "Brief Instructions" below. Otherwise, please see the full instructions on the documentation website for "[Creating a Development Environment](https://docs.tagstud.io/install/#creating-a-development-environment)".
+
+### Brief Instructions
+
+1.  Have [Python 3.12](https://www.python.org/downloads/) and PIP installed. Also have [FFmpeg](https://ffmpeg.org/download.html) installed if you wish to have audio/video playback and thumbnails.
+2.  Clone the repository to the folder of your choosing:
+    ```
+    git clone https://github.com/TagStudioDev/TagStudio.git
+    ```
+3.  Use a dependency manager such as [uv](https://docs.astral.sh/uv/) or [Poetry 2.0](https://python-poetry.org/blog/category/releases/) to install the required dependencies, or alternatively create and activate a [virtual environment](https://docs.tagstud.io/install/#manual-installation) with `venv`.
+
+4.  If using a virtual environment instead of a dependency manager, install an editable version of the program and development dependencies with the following PIP command:
+
+    ```
+    pip install -e ".[dev]"
+    ```
+
+    Otherwise, modify the command above for use with your dependency manager of choice. For example if using uv, you may use this:
+
+    ```
+    uv pip install -e ".[dev]"
+    ```
+
+## Workflow Checks
+
+When pushing your code, several automated workflows will check it against predefined tests and style checks. It's _highly recommended_ that you run these checks locally beforehand to avoid having to fight back-and-forth with the workflow checks inside your pull requests.
+
+<!-- prettier-ignore -->
+!!! tip
+    To format the code automatically before each commit, there's a configured action available for the `pre-commit` hook. Install it by running `pre-commit install`. The hook will be executed each time on running `git commit`.
+
+### [Ruff](https://github.com/astral-sh/ruff)
+
+A Python linter and code formatter. Ruff uses the `pyproject.toml` as its config file and runs whenever code is pushed or pulled into the project.
+
+#### Running Locally
+
+Inside the root repository directory:
+
+-   Lint code with `ruff check`
+    -   Some linting suggestions can be automatically formatted with `ruff check --fix`
+-   Format code with `ruff format`
+
+Ruff should automatically discover the configuration options inside the [pyproject.toml](https://github.com/TagStudioDev/TagStudio/blob/main/pyproject.toml) file. For more information, see the [ruff configuration discovery docs](https://docs.astral.sh/ruff/configuration/#config-file-discovery).
+
+Ruff is also available as a VS Code [extension](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff), PyCharm [plugin](https://plugins.jetbrains.com/plugin/20574-ruff), and [more](https://docs.astral.sh/ruff/integrations/).
+
+### [Mypy](https://github.com/python/mypy)
+
+Mypy is a static type checker for Python. It sure has a lot to say sometimes, but we recommend you take its advice when possible. Mypy also uses the `pyproject.toml` as its config file and runs whenever code is pushed or pulled into the project.
+
+#### Running Locally
+
+-   **(First time only)** Run the following:
+    -   `mkdir -p .mypy_cache`
+    -   `mypy --install-types --non-interactive`
+-   You can now check code by running `mypy --config-file pyproject.toml .` in the repository root. _(Don't forget the "." at the end!)_
+
+Mypy is also available as a VS Code [extension](https://marketplace.visualstudio.com/items?itemName=matangover.mypy), PyCharm [plugin](https://plugins.jetbrains.com/plugin/11086-mypy), and [more](https://plugins.jetbrains.com/plugin/11086-mypy).
+
+### PyTest
+
+-   Run all tests by running `pytest tests/` in the repository root.
+
+## Code Style
+
+See the [Style Guide](style.md)
+
+### Modules & Implementations
+
+-   **Do not** modify legacy library code in the `src/core/library/json/` directory
+-   Avoid direct calls to `os`
+    -   Use `Pathlib` library instead of `os.path`
+    -   Use `platform.system()` instead of `os.name` and `sys.platform`
+-   Don't prepend local imports with `tagstudio`, stick to `src`
+-   Use the `logger` system instead of `print` statements
+-   Avoid nested f-strings
+-   Use HTML-like tags inside Qt widgets over stylesheets where possible
+
+### Commit and Pull Request Style
+
+-   Use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0) as a guideline for commit messages. This allows us to easily generate changelogs for releases.
+    -   See some [examples](https://www.conventionalcommits.org/en/v1.0.0/#examples) of what this looks like in practice.
+-   Use clear and concise commit messages. If your commit does too much, either consider breaking it up into smaller commits or providing extra detail in the commit description.
+-   Pull requests should have an adequate title and description which clearly outline your intentions and changes/additions. Feel free to provide screenshots, GIFs, or videos, especially for UI changes.
+-   Pull requests should ideally be limited to **a single** feature or fix.
+
+<!-- prettier-ignore -->
+!!! important
+    **Please do not force push if your PR is open for review!** Force pushing makes it impossible to discern which changes have already been reviewed and which haven't. This means a reviewer will then have to re-review all the already reviewed code, which is a lot of unnecessary work for reviewers.
+
+<!-- prettier-ignore -->
+!!! tip
+    If you're unsure where to stop the scope of your PR, ask yourself: _"If I broke this up, could any parts of it still be used by the project in the meantime?"_
+
+### Runtime Requirements
+
+-   Final code must function on supported versions of Windows, macOS, and Linux:
+    -   Windows: 10, 11
+    -   macOS: 13.0+
+    -   Linux: _Varies_
+-   Final code must **_NOT:_**
+    -   Contain superfluous or unnecessary logging statements
+    -   Cause unreasonable slowdowns to the program outside of a progress-indicated task
+    -   Cause undesirable visual glitches or artifacts on screen
+
+## Documentation Guidelines
+
+Documentation contributions include anything inside of the `docs/` folder, as well as the `README.md` and `CONTRIBUTING.md` files. Documentation inside the `docs/` folder is built and hosted on our static documentation site, [docs.tagstud.io](https://docs.tagstud.io/).
+
+-   Use "[dash-case / kebab-case](https://developer.mozilla.org/en-US/docs/Glossary/Kebab_case)" for file and folder names
+-   Follow the folder structure pattern
+-   Don't add images or other media with excessively large file sizes
+-   Provide alt text for all embedded media
+-   Use "[Title Case](https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case)" for title capitalization
+
+## Translation Guidelines
+
+Translations are performed on the TagStudio [Weblate project](https://hosted.weblate.org/projects/tagstudio/).
+
+_Translation guidelines coming soon._
--- a/docs/developing.md
+++ b/docs/developing.md
@@ -121,7 +121,7 @@ A reference `.envrc` is provided for use with [direnv](#direnv), see [`contrib/.

 ### Editor Integration

-The entry point for TagStudio is `src/tagstudio/main.py`. You can target this file from your IDE to run or connect a debug session. The example(s) below show off example launch scripts for different IDEs. Here you can also take advantage of [launch arguments](./usage.md/#launch-arguments) to pass your own test [libraries](./library/index.md) to use while developing. You can find more editor configurations in [`contrib`](https://github.com/TagStudioDev/TagStudio/tree/main/contrib).
+The entry point for TagStudio is `src/tagstudio/main.py`. You can target this file from your IDE to run or connect a debug session. The example(s) below show off example launch scripts for different IDEs. Here you can also take advantage of [launch arguments](./usage.md/#launch-arguments) to pass your own test [libraries](libraries.md) to use while developing. You can find more editor configurations in [`contrib`](https://github.com/TagStudioDev/TagStudio/tree/main/contrib).

 <!-- prettier-ignore -->
 === "VS Code"
--- a/docs/library/entry.md
+++ b/docs/library/entry.md
@@ -4,7 +4,7 @@ icon: material/file

 # :material-file: Entries

-Entries are the individual representations of your files inside a TagStudio [library](./index.md). Each one corresponds one-to-one to a file on disk, and tracks all of the additional [tags](tag.md) and metadata that you attach to it inside TagStudio.
+Entries are the individual representations of your files inside a TagStudio [library](./index.md). Each one corresponds one-to-one to a file on disk, and tracks all of the additional [tags](tags.md) and metadata that you attach to it inside TagStudio.

 ## Storage

--- a/docs/library/field.md
+++ b/docs/library/field.md
@@ -4,7 +4,7 @@ icon: material/text-box

 # :material-text-box: Fields

-Fields are additional types of metadata that you can attach to [file entries](./entry.md). Like [tags](./tag.md), fields are not stored inside files themselves nor in sidecar files, but rather inside the respective TagStudio [library](./index.md) save file.
+Fields are additional types of metadata that you can attach to [file entries](./entries.md). Like [tags](tags.md), fields are not stored inside files themselves nor in sidecar files, but rather inside the respective TagStudio [library](./index.md) save file.

 ## Field Types

@@ -20,7 +20,7 @@ A long string of text displayed as a box of text.

 -   e.g: Description, Notes, etc.

-### Datetime [WIP]
+### Datetime

 A date and time value.

--- a/docs/help/ffmpeg.md
+++ b/docs/help/ffmpeg.md
@@ -2,7 +2,7 @@
 icon: material/movie-open-cog
 ---

-# :material-movie-open-cog: FFmpeg
+# :material-movie-open-cog: Installing FFmpeg

 FFmpeg is required for thumbnail previews and playback features on audio and video files. FFmpeg is a free Open Source project dedicated to the handling of multimedia (video, audio, etc) files. For more information, see their official website at [ffmpeg.org](https://www.ffmpeg.org/).

--- a/docs/utilities/ignore.md
+++ b/docs/utilities/ignore.md
@@ -1,9 +1,9 @@
 ---
-title: Ignore Files
+title: Ignoring Files
 icon: material/file-document-remove
 ---

-# :material-file-document-remove: Ignore Files & Directories
+# :material-file-document-remove: Ignoring Files & Directories

 <!-- prettier-ignore -->
 !!! warning "Legacy File Extension Ignoring"
@@ -11,7 +11,7 @@ icon: material/file-document-remove

    If you're still running an older version of TagStudio in the meantime, you can access the legacy system by going to "Edit -> Manage File Extensions" in the menubar.

-TagStudio offers the ability to ignore specific files and directories via a `.ts_ignore` file located inside your [library's](../library/index.md) `.TagStudio` folder. This file is designed to use very similar [glob](<https://en.wikipedia.org/wiki/Glob_(programming)>)-style pattern matching as the [`.gitignore`](https://git-scm.com/docs/gitignore) file used by Git™[^1]. It can be edited within TagStudio or opened to edit with an external program by going to the "Edit -> Ignore Files" option in the menubar.
+TagStudio offers the ability to ignore specific files and directories via a `.ts_ignore` file located inside your [library's](libraries.md) `.TagStudio` folder. This file is designed to use very similar [glob](<https://en.wikipedia.org/wiki/Glob_(programming)>)-style pattern matching as the [`.gitignore`](https://git-scm.com/docs/gitignore) file used by Git™[^1]. It can be edited within TagStudio or opened to edit with an external program by going to the "Edit -> Ignore Files" option in the menubar.

 This file is only referenced when scanning directories for new files to add to your library, and does not apply to files that have already been added to your library.

--- a/docs/index.md
+++ b/docs/index.md
@@ -2,6 +2,7 @@
 title: Home
 hide:
    - toc
+    - navigation
 ---

 #
@@ -35,15 +36,15 @@ hide:

 <div class="grid cards" markdown>

-   :material-file-multiple:{ .lg .middle } **[All Files](./library/entry.md) Welcome**
+-   :material-file-multiple:{ .lg .middle } **[All Files](entries.md) Welcome**

    ***

    TagStudio works with photos, videos, music, documents, and more! **All file types** are recognized by TagStudio, with most common ones having built-in preview support.

-    [:material-arrow-right: See Full Preview Support](./library/index.md#preview-support)
+    [:material-arrow-right: See Full Preview Support](preview-support.md)

-   :material-tag-text:{ .lg .middle } **Create [Tags](./library/tag.md) Your Way**
+-   :material-tag-text:{ .lg .middle } **Create [Tags](tags.md) Your Way**

    ***

@@ -53,17 +54,17 @@ hide:
    -   :material-tag-multiple: Tags can be tagged with other tags!
    -   :material-star-four-points: And more!

-   :material-magnify:{ .lg .middle } **Powerful [Search](./library/library_search.md)**
+-   :material-magnify:{ .lg .middle } **Powerful [Search](search.md)**

    ***

-    -   Full [Boolean operator](./library/library_search.md) support
+    -   Full [Boolean operator](search.md) support
    -   Filenames, paths, and extensions with [glob](<https://en.wikipedia.org/wiki/Glob_(programming)>) syntax
    -   General media types (e.g. "Photo", "Video", "Document")
    -   Special searches (e.g. "Untagged")
-    -   "[Smartcase](./library/library_search.md#case-sensitivity)" case sensitivity
+    -   "[Smartcase](search.md#case-sensitivity)" case sensitivity

-   :material-text-box:{ .lg .middle } **Text and Date [Fields](./library/field.md)**
+-   :material-text-box:{ .lg .middle } **Text and Date [Fields](fields.md)**

    ***

@@ -85,15 +86,15 @@ hide:

    [:material-arrow-right: View License](https://github.com/TagStudioDev/TagStudio/blob/main/LICENSE)

-    [:material-arrow-right: Roadmap to MIT Core Library License](./updates/roadmap.md#core-library-api)
+    [:material-arrow-right: Roadmap to MIT Core Library License](roadmap.md#core-library-api)

 -   :material-database:{ .lg .middle } **Central Save File**

    ***

-    Apposed to filling your drives with [sidecar files](https://en.wikipedia.org/wiki/Sidecar_file), TagStudio uses a project-like [library](./library/index.md) system that stores your tags and metadata inside a single save file per-library.
+    Apposed to filling your drives with [sidecar files](https://en.wikipedia.org/wiki/Sidecar_file), TagStudio uses a project-like [library](libraries.md) system that stores your tags and metadata inside a single save file per-library.

-    [:material-arrow-right: Learn About the Format](./library/index.md)
+    [:material-arrow-right: Learn About the Format](libraries.md)

 </div>

@@ -105,6 +106,6 @@ TagStudio aims to create an **open** and **robust** format for file tagging that

 <div class="grid cards" markdown>

-   :material-map-check:{ .lg .middle } See the [**Roadmap**](./updates/roadmap.md) for future features and updates
+-   :material-map-check:{ .lg .middle } See the [**Roadmap**](roadmap.md) for future features and updates

 </div>
--- a/docs/install.md
+++ b/docs/install.md
@@ -4,7 +4,7 @@ icon: material/download

 # :material-download: Installation

-TagStudio provides [releases](https://github.com/TagStudioDev/TagStudio/releases) as well as full access to its [source code](https://github.com/TagStudioDev/TagStudio) under the [GPLv3](https://github.com/TagStudioDev/TagStudio/blob/main/LICENSE) license.
+TagStudio provides executable [releases](https://github.com/TagStudioDev/TagStudio/releases) as well as full access to its [source code](https://github.com/TagStudioDev/TagStudio) under the [GPLv3](https://github.com/TagStudioDev/TagStudio/blob/main/LICENSE) license.

 ## Executables

@@ -52,7 +52,7 @@ pip install .
    ```sh
    pip install -e ".[dev]"
    ```
-    _See more under "[Developing](./develop.md)"_
+    _See more under "[Developing](developing.md)"_

 TagStudio can now be launched via the `tagstudio` command in your terminal.

@@ -239,4 +239,4 @@ To generate thumbnails for RAR-based files (like `.cbr`) you'll need an extracto

 ### ripgrep

-A recommended tool to improve the performance of directory scanning is [`ripgrep`](https://github.com/BurntSushi/ripgrep), a Rust-based directory walker that natively integrates with our [`.ts_ignore`](./utilities/ignore.md) (`.gitignore`-style) pattern matching system for excluding files and directories. Ripgrep is already pre-installed on some Linux distributions and also available from several package managers.
+A recommended tool to improve the performance of directory scanning is [`ripgrep`](https://github.com/BurntSushi/ripgrep), a Rust-based directory walker that natively integrates with our [`.ts_ignore`](ignore.md) (`.gitignore`-style) pattern matching system for excluding files and directories. Ripgrep is already pre-installed on some Linux distributions and also available from several package managers.
--- a/docs/libraries.md
+++ b/docs/libraries.md
@@ -0,0 +1,13 @@
+---
+icon: material/database
+---
+
+# :material-database: Libraries
+
+<!-- prettier-ignore -->
+!!! info
+    This page is a work in progress and needs to be updated with additional information.
+
+The library is how TagStudio represents your chosen directory, with every file inside being represented by a [file entry](entries.md). You can have as many or few libraries as you wish, since each libraries' data is stored within a `.TagStudio` folder at its root. From there the library save file itself is stored as `ts_library.sqlite`, with TagStudio versions 9.4 and below using a the legacy `ts_library.json` format.
+
+Note that this means [tags](tags.md) you create only exist _per-library_. Global tags along with other library structure updates are planned for future releases on the [roadmap](roadmap.md#library).
--- a/docs/updates/schema_changes.md
+++ b/docs/updates/schema_changes.md
@@ -2,7 +2,7 @@
 icon: material/database-edit
 ---

-# :material-database-edit: Save Format Changes
+# :material-database-edit: Library Format

 This page outlines the various changes made to the TagStudio library save file format over time, sometimes referred to as the "database" or "database file".

@@ -75,7 +75,7 @@ Migration from the legacy JSON format is provided via a walkthrough when opening
 | ------------------------------------------------------------------------------- | ------ | ----------------------------------------------- |
 | [v9.5.0-pr4](https://github.com/TagStudioDev/TagStudio/releases/tag/v9.5.0-pr4) | SQLite | `<Library Folder>`/.TagStudio/ts_library.sqlite |

-   Adds the `color_border` column to the `tag_colors` table. Used for instructing the [secondary color](../library/tag_color.md#secondary-color) to apply to a tag's border as a new optional behavior.
+-   Adds the `color_border` column to the `tag_colors` table. Used for instructing the [secondary color](colors.md#secondary-color) to apply to a tag's border as a new optional behavior.
 -   Adds three new default colors: "Burgundy (TagStudio Shades)", "Dark Teal (TagStudio Shades)", and "Dark Lavender (TagStudio Shades)".
 -   Updates Neon colors to use the new `color_border` property.

--- a/docs/library/tag_categories.md
+++ b/docs/library/tag_categories.md
@@ -1,17 +0,0 @@
---
-icon: material/shape-plus
---
-
-# :material-shape-plus: Tag Categories
-
-The "Is Category" property of tags determines if a tag should be treated as a category itself when being organized inside the preview panel. Tags marked as categories will show themselves and all tags inheriting from it (including recursively) underneath a field-like section with the tag's name. This means that duplicates of tags can appear on entries if the tag inherits from multiple parent categories, however this is by design and reflects the nature of multiple inheritance. Any tags not inheriting from a category tag will simply show under a default "Tag" section.
-
-![Tag Categories Example](../assets/tag_categories_example.png)
-
-### Built-In Tags and Categories
-
-The built-in tags "Favorite" and "Archived" inherit from the built-in "Meta Tags" category which is marked as a category by default. This behavior of default tags can be fully customized by disabling the category option and/or by adding/removing the tags' Parent Tags.
-
-### Migrating from v9.4 Libraries
-
-Due to the nature of how tags and Tag Felids operated prior to v9.5, the organization style of Tag Categories vs Tag Fields is not 1:1. Instead of tags being organized into fields on a per-entry basis, tags themselves determine their organizational layout via the "Is Property" flag. Any tags _(not currently inheriting from either the "Favorite" or "Archived" tags)_ will be shown under the default "Tags" header upon migrating to the v9.5+ library format. Similar organization to Tag Fields can be achieved by using the built-in "Meta Tags" tag or any other marked with "Is Category" and then setting those tags as parents for other tags to inherit from.
--- a/docs/utilities/macro.md
+++ b/docs/utilities/macro.md
@@ -4,13 +4,13 @@ icon: material/script-text

 # :material-script-text: Tools & Macros

-Tools and macros are features that serve to create a more fluid [library](../library/index.md)-managing process, or provide some extra functionality. Please note that some are still in active development and will be fleshed out in future updates.
+Tools and macros are features that serve to create a more fluid [library](libraries.md)-managing process, or provide some extra functionality. Please note that some are still in active development and will be fleshed out in future updates.

 ## Tools

 ### Fix Unlinked Entries

-This tool displays the number of unlinked [entries](../library/entry.md), and some options for their resolution.
+This tool displays the number of unlinked [entries](entries.md), and some options for their resolution.

 Refresh
 : Scans through the library and updates the unlinked entry count.
@@ -29,7 +29,7 @@ Load DupeGuru File
 : load the "results" file created from a DupeGuru scan

 Mirror Entries
-: Duplicate entries will have their contents mirrored across all instances. This allows for duplicate files to then be deleted with DupeGuru as desired, without losing the [field](../library/field.md) data that has been assigned to either. (Once deleted, the "Fix Unlinked Entries" tool can be used to clean up the duplicates)
+: Duplicate entries will have their contents mirrored across all instances. This allows for duplicate files to then be deleted with DupeGuru as desired, without losing the [field](fields.md) data that has been assigned to either. (Once deleted, the "Fix Unlinked Entries" tool can be used to clean up the duplicates)

 ### Create Collage

@@ -43,8 +43,8 @@ Tool is in development and will be documented in a future update.

 ### Sort fields

-Tool is in development. Will allow for user-defined sorting of [fields](../library/field.md).
+Tool is in development. Will allow for user-defined sorting of [fields](fields.md).

 ### Folders to Tags

-Creates tags from the existing folder structure in the library, which are previewed in a hierarchy view for the user to confirm. A tag will be created for each folder and applied to all entries, with each subfolder being linked to the parent folder as a [parent tag](../library/tag.md#parent-tags). Tags will initially be named after the folders, but can be fully edited and customized afterwards.
+Creates tags from the existing folder structure in the library, which are previewed in a hierarchy view for the user to confirm. A tag will be created for each folder and applied to all entries, with each subfolder being linked to the parent folder as a [parent tag](tags.md#parent-tags). Tags will initially be named after the folders, but can be fully edited and customized afterwards.
--- a/docs/preview-support.md
+++ b/docs/preview-support.md
@@ -1,16 +1,8 @@
-# :material-database: Library
-
-<!-- prettier-ignore -->
-!!! info
-    This page is a work in progress and needs to be updated with additional information.
-
-The library is how TagStudio represents your chosen directory, with every file inside being represented by a [file entry](./entry.md). You can have as many or few libraries as you wish, since each libraries' data is stored within a `.TagStudio` folder at its root. From there the library save file itself is stored as `ts_library.sqlite`, with TagStudio versions 9.4 and below using a the legacy `ts_library.json` format.
-
-Note that this means [tags](./tag.md) you create only exist _per-library_. Global tags along with other library structure updates are planned for future releases on the [roadmap](../updates/roadmap.md#library).
-
+---
+icon: material/image-check
 ---

-## Preview Support
+# :material-image-check: Supported Previews

 TagStudio offers built-in preview and thumbnail support for a wide variety of file types. Files that don't have explicit support can still be added to your library like normal, they will just show a default icon for thumbnails and previews. TagStudio also references the file's [MIME](https://en.wikipedia.org/wiki/Media_type) type in an attempt to render previews for file types that haven't gained explicit support yet.

@@ -51,7 +43,7 @@ Images will generate thumbnails the first time they are viewed or since the last

 ### :material-movie-open: Videos

-Video thumbnails will default to the closest viable frame from the middle of the video. Both thumbnail generation and video playback in the Preview Panel requires [FFmpeg](../install.md#third-party-dependencies) installed on your system.
+Video thumbnails will default to the closest viable frame from the middle of the video. Both thumbnail generation and video playback in the Preview Panel requires [FFmpeg](install.md#third-party-dependencies) installed on your system.

 | Filetype              | Extensions              | Dependencies |
 | --------------------- | ----------------------- | :----------: |
@@ -69,7 +61,7 @@ Video thumbnails will default to the closest viable frame from the middle of the

 ### :material-sine-wave: Audio

-Audio thumbnails will default to embedded cover art (if any) andfallback to generated waveform thumbnails. Audio file playback is supported in the Preview Panel if you have [FFmpeg](../install.md#third-party-dependencies) installed on your system. Audio waveforms are currently not cached.
+Audio thumbnails will default to embedded cover art (if any) andfallback to generated waveform thumbnails. Audio file playback is supported in the Preview Panel if you have [FFmpeg](install.md#third-party-dependencies) installed on your system. Audio waveforms are currently not cached.

 | Filetype            | Extensions               | Dependencies |
 | ------------------- | ------------------------ | :----------: |
@@ -112,7 +104,7 @@ Preview support for office documents or well-known project file formats varies b

 <!-- prettier-ignore -->
 !!! failure "3D Model Support"
-    TagStudio does not currently support previews for 3D model files *(outside of Blender project embedded thumbnails)*. This is on our [roadmap](../updates/roadmap.md#uiux) for future features.
+    TagStudio does not currently support previews for 3D model files *(outside of Blender project embedded thumbnails)*. This is on our [roadmap](roadmap.md#uiux) for a future release.

 ### :material-format-font: Fonts

@@ -130,7 +122,7 @@ Font thumbnails will use a "Aa" example preview of the font, with a full alphanu
 !!! info "Plain Text Support"
    TagStudio supports the *vast* majority of files considered to be "[plain text](https://en.wikipedia.org/wiki/Plain_text)". If an extension or format is not listed here, odds are it's still supported anyway.

-Text files render the first 256 bytes of text information to an image preview for thumbnails and the Preview Panel. Improved thumbnails, full scrollable text, and syntax highlighting are on our [roadmap](../updates/roadmap.md#uiux) for future features.
+Text files render the first 256 bytes of text information to an image preview for thumbnails and the Preview Panel. Improved thumbnails, full scrollable text, and syntax highlighting are on our [roadmap](roadmap.md#uiux) for future features.

 | Filetype   | Extensions                                    |        Syntax Highlighting         |
 | ---------- | --------------------------------------------- | :--------------------------------: |
--- a/docs/updates/roadmap.md
+++ b/docs/updates/roadmap.md
@@ -39,7 +39,7 @@ Must be finalized or deemed "feature complete" before other core features are de
 !!! note
    See the "[Library](#library)" section for features related to the library database rather than the underlying schema.

-   [x] A SQLite-based library save file format **[[v9.5.0](./changelog.md#950-2025-03-03)]**
+-   [x] A SQLite-based library save file format **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
 -   [ ] Cached File Properties Table :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [x] Date Entry Added to Library :material-chevron-triple-up:{ .priority-high title="High Priority" }
    -   [ ] Date File Created :material-chevron-triple-up:{ .priority-high title="High Priority" }
@@ -77,14 +77,14 @@ A detailed written specification for the TagStudio tag and/or library format. In
 -   [ ] Lightbox View :material-chevron-triple-up:{ .priority-high title="High Priority" }
    -   Similar to List View in concept, but displays one large preview that can cycle back/forth between entries.
    -   [ ] Smaller thumbnails of immediate adjacent entries below :material-chevron-double-up:{ .priority-med title="Medium Priority" }
-   [x] Library Statistics Screen :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.5.4]**
-   [x] Unified Library Health/Cleanup Screen :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.5.4]**
+-   [x] Library Statistics Screen **[[v9.5.4](changelog.md#954-september-1st-2025)]**
+-   [x] Unified Library Health/Cleanup Screen **[[v9.5.4](changelog.md#954-september-1st-2025)]**
    -   [x] Fix Unlinked Entries
    -   [x] Fix Duplicate Files
    -   [x] ~~Fix Duplicate Entries~~
-    -   [x] Remove Ignored Entries :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.5.4]**
-    -   [x] Delete Old Backups :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.5.4]**
-    -   [x] Delete Legacy JSON File :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.5.4]**
+    -   [x] Remove Ignored Entries **[[v9.5.4](changelog.md#954-september-1st-2025)]**
+    -   [x] Delete Old Backups **[[v9.5.4](changelog.md#954-september-1st-2025)]**
+    -   [x] Delete Legacy JSON File **[[v9.5.4](changelog.md#954-september-1st-2025)]**
 -   [x] Translations
 -   [ ] Search Bar Rework :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.7.x]**
    -   [ ] Improved Tag Autocomplete :material-chevron-triple-up:{ .priority-high title="High Priority" }
@@ -125,7 +125,7 @@ A detailed written specification for the TagStudio tag and/or library format. In
    -   [x] Language
    -   [x] Date and Time Format
    -   [x] Theme
-    -   [x] Thumbnail Generation :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.5.4]**
+    -   [x] Thumbnail Generation **[[v9.5.4](changelog.md#954-september-1st-2025)]**
 -   [x] Configurable Page Size
 -   [ ] Library Settings :material-chevron-triple-up:{ .priority-high title="High Priority" }
    -   [ ] Stored in `.TagStudio` folder :material-chevron-triple-up:{ .priority-high title="High Priority" }
@@ -140,7 +140,7 @@ Some form of official plugin support for TagStudio, likely with its own API that

 ---

-## [Library](../library/index.md)
+## [Library](libraries.md)

 ### :material-wrench: Library Mechanics

@@ -154,10 +154,10 @@ Some form of official plugin support for TagStudio, likely with its own API that
    -   [ ] Detect Deletions :material-chevron-triple-up:{ .priority-high title="High Priority" }
    -   [ ] Performant :material-chevron-triple-up:{ .priority-high title="High Priority" }
 -   [ ] Background File Scanning :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.7.x]**
-   [x] Thumbnail Caching **[[v9.5.0](./changelog.md#950-2025-03-03)]**
+-   [x] Thumbnail Caching **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
    -   [ ] Audio Waveform Caching :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.7.x]**

-### :material-grid: [Entries](../library/entry.md)
+### :material-grid: [Entries](entries.md)

 Library representations of files or file-like objects.

@@ -167,7 +167,7 @@ Library representations of files or file-like objects.
 -   [x] Fields
    -   [x] Text Lines
    -   [x] Text Boxes
-    -   [x] Datetimes **[v9.5.4]**
+    -   [x] Datetimes **[[v9.5.4](changelog.md#954-september-1st-2025)]**
    -   [ ] User-Titled Fields :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
        -   [ ] Removal of Deprecated Fields :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
 -   [ ] Entry Groups :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.7.x]**
@@ -178,9 +178,9 @@ Library representations of files or file-like objects.
    -   [ ] Group is treated as entry with tags and metadata :material-chevron-double-up:{ .priority-med title="Medium Priority" }
    -   [ ] Nested groups :material-chevron-double-up:{ .priority-med title="Medium Priority" }

-### :material-tag-text: [Tags](../library/tag.md)
+### :material-tag-text: [Tags](tags.md)

-Discrete library objects representing [attributes](<https://en.wikipedia.org/wiki/Property_(philosophy)>). Can be applied to library [entries](../library/entry.md), or applied to other tags to build traversable relationships.
+Discrete library objects representing [attributes](<https://en.wikipedia.org/wiki/Property_(philosophy)>). Can be applied to library [entries](entries.md), or applied to other tags to build traversable relationships.

 -   [x] Tag Name **[v8.0.0]**
 -   [x] Tag Shorthand Name **[v8.0.0]**
@@ -189,52 +189,52 @@ Discrete library objects representing [attributes](<https://en.wikipedia.org/wik
 -   [ ] Tag Description :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.6.x]**
 -   [x] Tag Colors
    -   [x] Built-in Color Palette **[v8.0.0]**
-    -   [x] User-Defined Colors **[[v9.5.0](./changelog.md#950-2025-03-03)]**
-    -   [x] Primary and Secondary Colors **[[v9.5.0](./changelog.md#950-2025-03-03)]**
+    -   [x] User-Defined Colors **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
+    -   [x] Primary and Secondary Colors **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
 -   [ ] Tag Icons :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] Small Icons :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] Large Icons for Profiles :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.6.x]**
    -   [ ] Built-in Icon Packs (i.e. Boxicons) :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] User-Defined Icons :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
-   [x] [Category Property](../library/tag_categories.md) **[[v9.5.0](./changelog.md#950-2025-03-03)]**
+-   [x] [Category Property](tags.md#is-category) **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
    -   [x] Property available for tags that allow the tag and any inheriting from it to be displayed separately in the preview panel under a title
    -   [ ] Fine-tuned exclusion from categories :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
 -   [ ] Hidden Property :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] Built-in "Archived" tag has this property by default :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] Checkbox near search bar to show hidden tags in search :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
 -   [ ] Tag Relationships
-    -   [x] [Parent Tags](../library/tag.md#parent-tags) ([Inheritance](<https://en.wikipedia.org/wiki/Inheritance_(object-oriented_programming)>) Relationship) **[v9.0.0]**
-    -   [ ] [Component Tags](../library/tag.md#component-tags) ([Composition](https://en.wikipedia.org/wiki/Object_composition) Relationship) :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
+    -   [x] [Parent Tags](tags.md#parent-tags) ([Inheritance](<https://en.wikipedia.org/wiki/Inheritance_(object-oriented_programming)>) Relationship) **[v9.0.0]**
+    -   [ ] [Component Tags](tags.md#component-tags) ([Composition](https://en.wikipedia.org/wiki/Object_composition) Relationship) :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
 -   [ ] Multiple Language Support :material-chevron-up:{ .priority-low title="Low Priority" } **[v9.9.x]**
 -   [ ] Tag Overrides :material-chevron-double-up:{ .priority-med title="Medium Priority" }
 -   [ ] Tag Merging :material-chevron-double-up:{ .priority-med title="Medium Priority" }

-### :material-magnify: [Search](../library/library_search.md)
+### :material-magnify: [Search](search.md)

 -   [x] Tag Search **[v8.0.0]**
-   [x] Filename Search **[[v9.5.0](./changelog.md#950-2025-03-03)]**
-    -   [x] Glob Search **[[v9.5.0](./changelog.md#950-2025-03-03)]**
-   [x] Filetype Search **[[v9.5.0](./changelog.md#950-2025-03-03)]**
-    -   [x] Search by Extension (e.g. ".jpg", ".png") **[[v9.5.0](./changelog.md#950-2025-03-03)]**
-        -   [x] Optional consolidation of extension synonyms (i.e. ".jpg" can equal ".jpeg") **[[v9.5.0](./changelog.md#950-2025-03-03)]**
-    -   [x] Search by media type (e.g. "image", "video", "document") **[[v9.5.0](./changelog.md#950-2025-03-03)]**
+-   [x] Filename Search **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
+    -   [x] Glob Search **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
+-   [x] Filetype Search **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
+    -   [x] Search by Extension (e.g. ".jpg", ".png") **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
+        -   [x] Optional consolidation of extension synonyms (i.e. ".jpg" can equal ".jpeg") **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
+    -   [x] Search by media type (e.g. "image", "video", "document") **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
 -   [ ] Field Content Search :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
-   [x] [Boolean Operators](../library/library_search.md) **[[v9.5.0](./changelog.md#950-2025-03-03)]**
+-   [x] [Boolean Operators](search.md) **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
    -   [x] `AND` Operator
    -   [x] `OR` Operator
    -   [x] `NOT` Operator
    -   [x] Parenthesis Grouping
    -   [x] Character Escaping
-   [ ] `HAS` Operator (for [Component Tags](../library/tag.md#component-tags)) :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
+-   [ ] `HAS` Operator (for [Component Tags](tags.md#component-tags)) :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
 -   [ ] Conditional Search :material-chevron-double-up:{ .priority-med title="Medium Priority" } **[v9.7.x]**
    -   [ ] Compare Dates :material-chevron-double-up:{ .priority-med title="Medium Priority" }
    -   [ ] Compare Durations :material-chevron-double-up:{ .priority-med title="Medium Priority" }
    -   [ ] Compare File Sizes :material-chevron-double-up:{ .priority-med title="Medium Priority" }
    -   [ ] Compare Dimensions :material-chevron-double-up:{ .priority-med title="Medium Priority" }
-   [x] Smartcase Search [[v9.5.0](./changelog.md#950-2025-03-03)]
+-   [x] Smartcase Search **[[v9.5.0](changelog.md#950-march-3rd-2025)]**
 -   [ ] Search Result Sorting
-    -   [x] Sort by Filename **[[v9.5.2](./changelog.md#952-2025-03-31)]**
-    -   [x] Sort by Date Entry Added to Library **[[v9.5.2](./changelog.md#952-2025-03-31)]**
+    -   [x] Sort by Filename **[[v9.5.2](changelog.md#952-march-31st-2025)]**
+    -   [x] Sort by Date Entry Added to Library **[[v9.5.2](changelog.md#952-march-31st-2025)]**
    -   [ ] Sort by File Creation Date :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] Sort by File Modification Date :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.6.x]**
    -   [ ] Sort by File Modification Date :material-chevron-triple-up:{ .priority-high title="High Priority" }
@@ -243,7 +243,7 @@ Discrete library objects representing [attributes](<https://en.wikipedia.org/wik
 -   [ ] OCR Search :material-chevron-up:{ .priority-low title="Low Priority" }
 -   [ ] Fuzzy Search :material-chevron-up:{ .priority-low title="Low Priority" }

-### :material-file-cog: [Macros](../utilities/macro.md)
+### :material-file-cog: [Macros](macros.md)

 -   [ ] Standard, Human Readable Format (TOML) :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.5.x]**
 -   [ ] Versioning System :material-chevron-triple-up:{ .priority-high title="High Priority" } **[v9.5.x]**
--- a/docs/library/library_search.md
+++ b/docs/library/library_search.md
@@ -2,7 +2,7 @@
 icon: material/magnify
 ---

-# :material-magnify: Search
+# :material-magnify: Searching

 TagStudio provides various methods to search your library, ranging from TagStudio data such as tags to inherent file data such as paths or media types.

@@ -58,13 +58,13 @@ Sometimes search queries have ambiguous characters and need to be "escaped". Thi

 ## Tags

-[Tag](#tags) search is the default mode of file entry search in TagStudio. No keyword prefix is required, however using `tag:` will also work. The tag search attempts to match tag [names](./tag.md#name), [shorthands](./tag.md#shorthand), [aliases](./tag.md#aliases), as well as allows for tags to [substitute](./tag.md#intuition-via-substitution) in for any of their [parent tags](./tag.md#parent-tags).
+[Tag](#tags) search is the default mode of file entry search in TagStudio. No keyword prefix is required, however using `tag:` will also work. The tag search attempts to match tag [names](tags.md#name), [shorthands](tags.md#shorthand), [aliases](tags.md#aliases), as well as allows for tags to [substitute](tags.md#intuition-via-substitution) in for any of their [parent tags](tags.md#parent-tags).

 You may also see the `tag_id:` prefix keyword show up when using the right-click "Search for Tag" option on tags. This is meant for internal use, and eventually will not be displayed or accessible to the user.

 ## Fields

-_[Field](./field.md) search is currently not in the program, however is coming in a future version._
+_[Field](fields.md) search is currently not in the program, however is coming in a future version._

 ## File Entry Search

--- a/docs/style.md
+++ b/docs/style.md
@@ -0,0 +1,96 @@
+---
+icon: material/sign-text
+---
+
+# :material-sign-text: Style Guide
+
+## Formatting
+
+Most of the style guidelines can be checked, fixed, and enforced via Ruff. Older code may not be adhering to all of these guidelines, in which case _"do as I say, not as I do"..._
+
+-   Do your best to write clear, concise, and modular code.
+    -   This should include making methods private by default (e.g. `__method()`)
+    -   Methods should only be protected (e.g. `_method()`) or public (e.g. `method()`) when needed and warranted
+-   Keep a maximum column width of no more than **100** characters.
+-   Code comments should be used to help describe sections of code that can't speak for themselves.
+-   Use [Google style](https://google.github.io/styleguide/pyguide.html#s3.8-comments-and-docstrings) docstrings for any classes and functions you add.
+    -   If you're modifying an existing function that does _not_ have docstrings, you don't _have_ to add docstrings to it... but it would be pretty cool if you did ;)
+-   Imports should be ordered alphabetically.
+-   Lists of values should be ordered using their [natural sort order](https://en.wikipedia.org/wiki/Natural_sort_order).
+    -   Some files have their methods ordered alphabetically as well (i.e. [`thumb_renderer`](https://github.com/TagStudioDev/TagStudio/blob/main/src/tagstudio/qt/widgets/thumb_renderer.py)). If you're working in a file and notice this, please try and keep to the pattern.
+-   When writing text for window titles or form titles, use "[Title Case](https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case)" capitalization. Your IDE may have a command to format this for you automatically, although some may incorrectly capitalize short prepositions. In a pinch you can use a website such as [capitalizemytitle.com](https://capitalizemytitle.com/) to check.
+-   If it wasn't mentioned above, then stick to [**PEP-8**](https://peps.python.org/pep-0008/)!
+
+## Qt
+
+As of writing this section, the QT part of the code base is quite unstructured and the View and Controller parts are completely intermixed[^1]. This makes maintenance, fixes and general understanding of the code base quite challenging, because the interesting parts you are looking for are entangled in a bunch of repetitive UI setup code. To address this we are aiming to more strictly separate the view and controller aspects of the QT frontend.
+
+The general structure of the QT code base should look like this:
+
+```
+qt
+├── controllers
+│   ├── widgets
+│   │   └── preview_panel_controller.py
+│   └── main_window_controller.py
+├── views
+│   ├── widgets
+│   │   └── preview_panel_view.py
+│   └── main_window_view.py
+├── ts_qt.py
+└── mixed.py
+```
+
+In this structure there are the `views` and `controllers` sub-directories. They have the exact same structure and for every `<component>_view.py` there is a `<component>_controller.py` at the same location in the other subdirectory and vice versa.
+
+Typically the classes should look like this:
+
+```py
+# my_cool_widget_view.py
+class MyCoolWidgetView(QWidget):
+    def __init__(self):
+        super().__init__()
+        self.__button = QPushButton()
+        self.__color_dropdown = QComboBox()
+        # ...
+        self.__connect_callbacks()
+
+    def __connect_callbacks(self):
+        self.__button.clicked.connect(self._button_click_callback)
+        self.__color_dropdown.currentIndexChanged.connect(
+            lambda idx: self._color_dropdown_callback(self.__color_dropdown.itemData(idx))
+        )
+
+    def _button_click_callback(self):
+        raise NotImplementedError()
+```
+
+```py
+# my_cool_widget_controller.py
+class MyCoolWidget(MyCoolWidgetView):
+    def __init__(self):
+        super().__init__()
+
+    def _button_click_callback(self):
+        print("Button was clicked!")
+
+    def _color_dropdown_callback(self, color: Color):
+        print(f"The selected color is now: {color}")
+```
+
+Observe the following key aspects of this example:
+
+-   The Controller is just called `MyCoolWidget` instead of `MyCoolWidgetController` as it will be directly used by other code
+-   The UI elements are in private variables
+    -   This enforces that the controller shouldn't directly access UI elements
+    -   Instead the view should provide a protected API (e.g. `_get_color()`) for things like setting/getting the value of a dropdown, etc.
+    -   Instead of `_get_color()` there could also be a `_color` method marked with `@property`
+-   The callback methods are already defined as protected methods with NotImplementedErrors
+    -   Defines the interface the callbacks
+    -   Enforces that UI events be handled
+
+<!-- prettier-ignore -->
+!!! tip
+    A good (non-exhaustive) rule of thumb is: If it requires a non-UI import, then it doesn't belong in the `*_view.py` file.
+
+[^1]: For an explanation of the Model-View-Controller (MVC) Model, checkout this article: [MVC Framework Introduction](https://www.geeksforgeeks.org/mvc-framework-introduction/).
--- a/docs/stylesheets/extra.css
+++ b/docs/stylesheets/extra.css
@@ -26,6 +26,36 @@
    );
 }

+.md-tabs {
+    background: none;
+    font-family: "Bai Jamjuree", Roboto, sans-serif;
+    font-weight: 500;
+    letter-spacing: -0.05rem !important;
+}
+.md-tabs__link {
+    opacity: 1;
+    color: var(--md-default-fg-color--light);
+    padding: 0.1rem;
+}
+.md-tabs__link:hover {
+    color: var(--md-accent-fg-color) !important;
+}
+.md-tabs__item--active {
+    color: var(--md-typeset-a-color) !important;
+
+    border-color: var(--md-typeset-a-color) !important;
+    border-width: 0 0 2px 0 !important;
+    border: solid;
+}
+.md-tabs__item {
+    height: 1.8rem;
+}
+.md-tabs__link {
+    font-size: 0.8rem;
+    margin-top: 0.2rem;
+    margin-bottom: 0.2rem;
+}
+
 /* Mobile Nav Header */
 .md-nav__source {
    background: linear-gradient(
@@ -43,6 +73,15 @@ td {
    padding: 0.5em 1em 0.5em 1em !important;
 }

+.md-typeset ul li ul {
+    margin-top: 0;
+    margin-bottom: 0.1rem;
+}
+
+.md-typeset ul li {
+    margin-bottom: 0.1rem;
+}
+
 .md-header {
    border-style: solid;
    border-width: 0 0 2px 0;
--- a/docs/stylesheets/home.css
+++ b/docs/stylesheets/home.css
@@ -12,3 +12,16 @@ h2 {
    font-size: 1rem !important;
    line-height: 1.25rem;
 }
+
+.md-content {
+    margin-left: 5.5rem;
+    margin-right: 5.5rem;
+}
+
+/* Keeps four cards in a square on all screens */
+@media screen and (max-width: 64em) {
+    .md-content {
+        margin-left: 0;
+        margin-right: 0;
+    }
+}
--- a/docs/library/tag.md
+++ b/docs/library/tag.md
@@ -26,15 +26,15 @@ This is a special type of alias that's used for shortening the tag name under sp

 Aliases are alternate names that the tag can go by. This may include individual first names for people, alternate spellings, shortened names, and more. If there's a common abbreviation or shortened name for your tag, it's recommended to use the [shorthand](#shorthand) field for this instead.

-When searching for a tag, aliases (including the shorthand) can also be used to find the tag. This not only includes searching for tags themselves, but for tagged [file entries](./entry.md) as well!
+When searching for a tag, aliases (including the shorthand) can also be used to find the tag. This not only includes searching for tags themselves, but for tagged [file entries](entries.md) as well!

-### Automatic Disambiguation
+### Disambiguation

 Just as in real life, sometimes there are different attributes that share the same name with one another. The process of adding specificity to something in order to not confuse it with something similar is known as [disambiguation](https://en.wikipedia.org/wiki/Word-sense_disambiguation). In TagStudio we give the option to automatically disambiguate tag names based on a specially marked [Parent Tag](#parent-tags). Parent tags are explained in further detail below, but for the purposes of tag names they can lend themselves to clarifying the name of a tag without the user needing to manually change the name or add complicated aliases.

 Given a tag named "Freddy", we may confuse it with other "Freddy" tags in our library. There are lots of Freddys in the world, after all. If we're talking about Freddy from "Five Nights at Freddy's", then we may already (and likely should) have a separate "Five Nights at Freddy's" tag added as a parent tag. When the disambiguation box next to a parent tag is selected (see image below) then our tag name will automatically display its name with that parent tag's name (or shorthand if available) in parentheses.

-![Tag Disambiguation Example](../assets/tag_disambiguation_example.png)
+![Tag Disambiguation Example](assets/tag_disambiguation_example.png)

 So if the "Five Nights at Freddy's" tag is added as a parent tag on the "Freddy" tag, and the disambiguation box next to it is checked, then our tag name will automatically be displayed as "Freddy (Five Nights at Freddy's)". Better yet, if the "Five Nights at Freddy's" tag has a shorthand such as "FNAF", then our "Freddy" tag will be displayed as "Freddy (FNAF)". This process preserves our base tag name ("Freddy") and provides an option to get a clean and consistent method to display disambiguating parent categories, rather than having to type this information in manually for each applicable tag.

@@ -52,7 +52,7 @@ One of the core properties of tags in TagStudio is their ability to form relatio

 In a system where tags have no relationships, you're required to add as many tags as you possibly can to describe every last element of an image or file. If you want to tag an image of Shrek, you need to add a tag for `Shrek` himself, a `Character` tag since he's a character, a `Movie` and perhaps `Dreamworks` tag since he's a character from a movie, or perhaps a `Book` tag if we're talking about the original character, and then of course tags for every other attribute of Shrek shown or implied. By allowing tags to have inheritance relationships, we can have a single `Shrek` tag inherit from `Character` (Shrek IS a character) as well as from a separate `Shrek (Movie Franchise)` tag that itself inherits from `Movie Franchise` and `Dreamworks`. Now by simply adding the `Shrek` tag to an image, we've effectively also added the `Character`, `Shrek (Move Franchise)`, `Movie Franchise`, and `Dreamworks` attributes all in one go. On the image entry itself we only see `Shrek`, but the rest of the attributes are implied.

-![Shrek Tag Details](../assets/built_tag_shrek.png)
+![Shrek Tag Details](assets/built_tag_shrek.png)

 #### Intuition via Substitution

@@ -64,7 +64,9 @@ Lastly, when searching your files with broader categories such as `Character` or

 ### Component Tags

-**_Coming in version 9.6_**
+<!-- prettier-ignore -->
+!!! warning ""
+    **_Coming in version 9.6.x_**

 Component tags will be built from a composition-based, or "HAS" type relationship between tags. This takes care of instances where an attribute may "have" another attribute, but doesn't inherit from it. Shrek may be an `Ogre`, he may be a `Character`, but he is NOT a `Leather Vest` - even if he's commonly seen _with_ it. Component tags, along with the upcoming "Tag Override" feature, are built to handle these cases in a way that still simplifies the tagging process without adding too much undue complexity for the user.

@@ -74,17 +76,19 @@ Component tags will be built from a composition-based, or "HAS" type relationshi

 Tags use a default uncolored appearance by default, however can take on a number of built-in and user-created colors and color palettes! Tag color palettes can be based on a single color value (see: TagStudio Standard, TagStudio Shades, TagStudio Pastels) or use an optional secondary color use for the text and optionally the tag border (e.g. TagStudio Neon).

-![Tag Color Selection](../assets/tag_color_selection.png)
+![Tag Color Selection](assets/tag_color_selection.png)

 #### User-Created Colors

-Custom palettes and colors can be created via the [Tag Color Manager](./tag_color.md). These colors will display alongside the built-in colors inside the tag selection window and are separated by their namespace names. Colors which use the secondary color for the tag border will be outlined in that color, otherwise they will only display the secondary color on the bottom of the swatch to indicate at a glance that the text colors are different.
+Custom palettes and colors can be created via the [Tag Color Manager](colors.md). These colors will display alongside the built-in colors inside the tag selection window and are separated by their namespace names. Colors which use the secondary color for the tag border will be outlined in that color, otherwise they will only display the secondary color on the bottom of the swatch to indicate at a glance that the text colors are different.

-![Custom Tag Color Selection](../assets/custom_tag_color_selection.png)
+![Custom Tag Color Selection](assets/custom_tag_color_selection.png)

 ### Icon

-**_Coming in version 9.6_**
+<!-- prettier-ignore -->
+!!! warning ""
+    **_Coming in version 9.6.x_**

 ## Tag Properties

@@ -92,13 +96,25 @@ Properties are special attributes of tags that change their behavior in some way

 #### Is Category

-When the "Is Category" property is checked, this tag now acts as a category separator inside the preview panel. If this tag or any tags inheriting from this tag (i.e. tags that have this tag as a "[Parent Tag](#parent-tags)"), then these tags will appear under a separated group that's named after this tag. Tags inheriting from multiple "category tags" will still show up under any applicable category. _Read more under: [Tag Categories](../library/tag_categories.md)._
+The "Is Category" property of tags determines if a tag should be treated as a category itself when being organized inside the preview panel. If this tag or any tags inheriting from this tag (i.e. tags that have this tag as a "[Parent Tag](#parent-tags)"), then these tags will appear under a separated group that's named after this tag. Tags inheriting from multiple "category tags" will still show up under any applicable category.

-![Tag Category Example](../assets/tag_categories_example.png)
+This means that duplicates of tags can appear on entries if the tag inherits from multiple parent categories, however this is by design and reflects the nature of multiple inheritance. Any tags not inheriting from a category tag will simply show under a default "Tag" section.
+
+![Tag Category Example](assets/tag_categories_example.png)
+
+### Built-In Tags and Categories
+
+The built-in tags "Favorite" and "Archived" inherit from the built-in "Meta Tags" category which is marked as a category by default. This behavior of default tags can be fully customized by disabling the category option and/or by adding/removing the tags' Parent Tags.
+
+### Migrating from v9.4 Libraries
+
+Due to the nature of how tags and Tag Felids operated prior to v9.5, the organization style of Tag Categories vs Tag Fields is not 1:1. Instead of tags being organized into fields on a per-entry basis, tags themselves determine their organizational layout via the "Is Property" flag. Any tags _(not currently inheriting from either the "Favorite" or "Archived" tags)_ will be shown under the default "Tags" header upon migrating to the v9.5+ library format. Similar organization to Tag Fields can be achieved by using the built-in "Meta Tags" tag or any other marked with "Is Category" and then setting those tags as parents for other tags to inherit from.

 #### Is Hidden

-**_Coming in version 9.6_**
+<!-- prettier-ignore -->
+!!! warning ""
+    **_Coming in version 9.6.x_**

 When the "Is Hidden" property is checked, any file entries tagged with this tag will not show up in searches by default. This property comes by default with the built-in "Archived" tag.

--- a/docs/updates/changelog.md
+++ b/docs/updates/changelog.md
@@ -1,6 +0,0 @@
---
-title: Changelog
-icon: material/list-status
---
-
--8<-- "CHANGELOG.md"
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -2,7 +2,7 @@
 icon: material/mouse
 ---

-# :material-mouse: Usage
+# :material-mouse: Basic Usage

 ## Creating/Opening a Library