Deploying to prod from @ ded9d95 🚀

.gitattributes

@@ -1,2 +1,23 @@
-*.js              text eol=lf
-*.json            text eol=lf
+# Auto detect text files and perform LF normalization
+*             text=auto eol=lf
+
+# Documents
+*.md          text diff=markdown
+*.license     text
+
+# Graphics and assets
+*.gif         binary
+*.icns        binary
+*.ico         binary
+*.jpg         binary
+*.jpeg        binary
+*.otf         binary
+*.png         binary
+*.svg         binary
+*.ttf         binary
+*.webp        binary
+*.woff        binary
+*.woff2       binary
+
+# Overrides
+*.license     linguist-documentation

README.md

@@ -1,51 +1,56 @@
-# Pf2e.Tools
+# Pf2eTools
 
 [![pages-build-deployment](https://github.com/Pf2eToolsOrg/Pf2eTools/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/Pf2eToolsOrg/Pf2eTools/actions/workflows/pages/pages-build-deployment) [![Build and Deploy](https://github.com/Pf2eToolsOrg/Pf2eTools/actions/workflows/main.yml/badge.svg)](https://github.com/Pf2eToolsOrg/Pf2eTools/actions/workflows/main.yml)
 
-Visit the main site (not yet) or go to the unofficial GitHub [mirror](https://pf2etools.com).
+-   **Main site:** [https://pf2etools.com](https://pf2etools.com) (recommended)
+-   **Mirror 1:** [https://pf2oo.ls](https://pf2oo.ls)
+-   **Mirror 2:** [https://pf2e.tools](https://pf2e.tools)
 
-[Join the Pf2eTools Discord here!](https://discord.gg/2hzNxErtVu)
+Live development branch available on the [`dev` subdomain](https://dev.pf2etools.com).
 
-## Help and Support
+#### Join our [Discord server](https://discord.gg/2hzNxErtVu)!
 
-Please see [our Discord server](https://discord.gg/2hzNxErtVu) for FAQs, installation guides, supported integrations, and more.
+## Help and support
 
----
+Please see our [wiki](https://github.com/Pf2eToolsOrg/Pf2eTools/wiki) for an installation guide. For everything else, we have a variety of FAQs answered on our [Discord server](https://discord.gg/2hzNxErtVu), plus we're available for direct questions!
 
-## Developer Notes
+## Developer notes
 
-### Data Sources and Versioning
+<details>
+<summary>Developer notes</summary>
+
+### Data sources and versioning
 
 Only "official" (that is, published by Paizo) data is to be included in the site. Anything else should be added to the homebrew repository.
 
 Prioritise RAW above all else. Aim to provide a 1:1 copy of the original data. Obvious typos (for instance, mathematical errors in creature statblocks) may be corrected at the discretion of the maintainer(s).
 
 Aim to use the latest version of any published material. Older versions which are sufficiently different (and relevant to community interests) can be moved to the homebrew repository.
 
-### Target JavaScript Version
+### Target JavaScript version
 
 Targeting ES6 was the original intent, but more modern features have long since crept into the code. Therefore, if something is available as standard in both Chrome and Firefox (preferably in versions dating back at least a couple of months), and isn't bleeding-edge, one can reasonable justify using it. As with all things, use common sense.
 
-### Style Guidelines
+### Style guidelines
 
 #### Code
 
-- Use tabs over spaces.
+-   Use tabs over spaces.
 
 #### CSS
 
-- The [BEM](http://getbem.com/) ("Block Element Modifier") naming strategy should be used where possible.
+-   The [BEM](http://getbem.com/) ("Block Element Modifier") naming strategy should be used where possible.
 
-#### Data/Text
+#### Data/text
 
-- Format JSON to match the default output of JavaScript's `JSON.stringify` (using tabs for indentation), i.e. one line per bracket and one line per value. JSON files programmatically generated from other JSON files (i.e. those stored in `data/generated`) should be minified, however.
+-   Format JSON to match the default output of JavaScript's `JSON.stringify` (using tabs for indentation), i.e. one line per bracket and one line per value. JSON files programmatically generated from other JSON files (i.e. those stored in `data/generated`) should be minified, however.
 
-- When "tagging" references in data (e.g. `{@creature goblin}`), the following rules apply:
-  - Only tag references which are _intended as references_. For example, the Wizard class in `You gain one cantrip of your choice from the wizard spell list` should be tagged, whereas the Wizard class in `Together, a group of seven powerful wizards sought to contain the demon` should not be tagged. One is a reference to the mechanical class, one is merely the casual usage of the word "wizard."
-  - In a similar vein, never tag anything within a `quote`-type block. Even if the quote directly refers to a specific creature, we can assume the quote is from a universe/perspective in which (for example) statblocks don't exist, and therefore the tag should be omitted to maintain the flavour of the quote.
-  - Within data from a source, avoid referencing content from a source printed after the publication of that source.
+-   When "tagging" references in data (e.g. `{@creature goblin}`), the following rules apply:
+    -   Only tag references which are _intended as references_. For example, the Wizard class in `You gain one cantrip of your choice from the wizard spell list` should be tagged, whereas the Wizard class in `Together, a group of seven powerful wizards sought to contain the demon` should not be tagged. One is a reference to the mechanical class, one is merely the casual usage of the word "wizard."
+    -   In a similar vein, never tag anything within a `quote`-type block. Even if the quote directly refers to a specific creature, we can assume the quote is from a universe/perspective in which (for example) statblocks don't exist, and therefore the tag should be omitted to maintain the flavour of the quote.
+    -   Within data from a source, avoid referencing content from a source printed after the publication of that source.
 
-### JSON Cleaning
+### JSON-cleaning
 
 Parts of the JSON cleaning & style guidelines are also automated and can be applied using `npm run clean-jsons`. Additionally, this cleanup script is also run automatically as part of `npm run build`.
 
@@ -59,46 +64,46 @@ Replace: `$1$3`
 
 #### Character replacement
 
-- `’` should be replaced with `'`
-- `“` and `”` should be replaced with `"`
-- `—` (em dash) should be replaced with `\u2014` (Unicode for em dash)
-- `–` should be replaced with `\u2013` (Unicode for en dash)
-- `−` should be replaced with `\u2212` (Unicode for minus sign)
-- `•` should be not be used unless the JSON in question is not yet covered by the entryRenderer, i.e. should be encoded as a list
-- the only Unicode escape sequences allowed are `\u2014`, `\u2013`, and `\u2212`; all other characters (unless noted above) should be stored as-is
+-   `’` should be replaced with `'`
+-   `“` and `”` should be replaced with `"`
+-   `—` (em dash) should be replaced with `\u2014` (Unicode for em dash)
+-   `–` should be replaced with `\u2013` (Unicode for en dash)
+-   `−` should be replaced with `\u2212` (Unicode for minus sign)
+-   `•` should be not be used unless the JSON in question is not yet covered by the entryRenderer, i.e. should be encoded as a list
+-   the only Unicode escape sequences allowed are `\u2014`, `\u2013`, and `\u2212`; all other characters (unless noted above) should be stored as-is
 
 #### Convention for dashes
 
-- `-` (hyphen) should **only** be used to hyphenate words, e.g. `60-foot` and `18th-level`
-- `\u2014` should be used for parenthetical dash pairs, or for marking empty table rows.
-- `\u2013` should be used for joining numerical ranges, e.g. `1-5` should become `1\u20135`.
-- `\u2212` should be used for unary minus signs, in the case of penalties. For example, `"You have a -5 penalty to..."` should become `"You have a \u22125 penalty to..."`.
-- any whitespace on any side of a `\u2014` should be removed
+-   `-` (hyphen) should **only** be used to hyphenate words, e.g. `60-foot` and `18th-level`
+-   `\u2014` should be used for parenthetical dash pairs, or for marking empty table rows.
+-   `\u2013` should be used for joining numerical ranges, e.g. `1-5` should become `1\u20135`.
+-   `\u2212` should be used for unary minus signs, in the case of penalties. For example, `"You have a -5 penalty to..."` should become `"You have a \u22125 penalty to..."`.
+-   any whitespace on any side of a `\u2014` should be removed
 
 #### Convention for measurement
 
-- Adjectives: a hyphen and the full name of the unit of measure should be used, e.g. dragon exhales acid in a `60-foot line`
-- Nouns: a space and the short name of the unit of measure (including the trailing period) should be used, e.g. `blindsight 60 ft.`, `darkvision 120 ft.`
-- Time: a slash, `/`, with no spaces on either side followed by the capitalised unit of time, e.g. `2/Turn`, `3/Day`
+-   Adjectives: a hyphen and the full name of the unit of measure should be used, e.g. dragon exhales acid in a `60-foot line`
+-   Nouns: a space and the short name of the unit of measure (including the trailing period) should be used, e.g. `blindsight 60 ft.`, `darkvision 120 ft.`
+-   Time: a slash, `/`, with no spaces on either side followed by the capitalised unit of time, e.g. `2/Turn`, `3/Day`
 
-#### Convention for Dice
+#### Convention for dice
 
 Dice should be written as `[X]dY[ <+|-|×> Z]`, i.e. with a space between dice and operator, and a space between operator and modifier. Some examples of acceptable formatting are: `d6`, `2d6`, or `2d6 + 1`.
 
-#### Convention for Item Names
+#### Convention for item names
 
 Item names should be title-case, with the exception of units in parentheses, which should be sentence-case. Items who's volume or amount is specified by container (e.g. `(vial)`) treat the container as a unit.
 
-### Mouse/Keyboard Events
+### Mouse/keyboard events
 
 Avoid binding ALT-modified events, as these are not available under MacOS or various Linux flavors. Binding SHIFT-/CTRL-modified events is preferred.
 
-### Dev Server
+### Dev server
 
 Make sure you have everything installed (`npm install`) and built (`npm run build`) to have a fully functional site.
 Run `npm run serve:dev` to launch a local dev server that serves the project files on [`http://localhost:8080/index.html`](http://localhost:8080/index.html).
 
-### JSON Schema
+### JSON schema
 
 The repository contains a JSON Schema for the data files in `test/schema-template/schema.json`. The schema is currently a work in progress.
 
@@ -123,17 +128,17 @@ To use the JSON Schema with Visual Studio Code, head to Settings and locate the
 
 Do `npm run version-bump -- [OPTION]`, where `[OPTION]` is one of the following:
 
-- `major` to increment the major version (`1.2.3` will become `2.0.0`)
-- `minor` to increment the minor version (`1.2.3` will become `1.3.0`)
-- `patch` to increment the patch version (`1.2.3` will become `1.2.4`)
-- a version number (like `1.2.3`)
+-   `major` to increment the major version (`1.2.3` will become `2.0.0`)
+-   `minor` to increment the minor version (`1.2.3` will become `1.3.0`)
+-   `patch` to increment the patch version (`1.2.3` will become `1.2.4`)
+-   a version number (like `1.2.3`)
 
 It will first run the tests and fail to increase the version if the tests fail.
 It will then automatically replace the version in the files where it needs to be replaced, create a commit with the message `chore(version): bump` and create a tag (in the form `v1.2.3`) at the commit.
 This feature can be easily disabled by doing `npm config set git-tag-version false`.
 
----
+</details>
 
 ## License
 
-This project is licensed under the terms of the MIT license.
+This project is licensed under the terms of the [MIT license](LICENSE).

RELEASE_NOTES.md

@@ -1,34 +1,15 @@
-v0.8.11, "The Books Start Coming and They Don't Stop Coming" edition
+v0.8.12
 
-- Lots of new content!
-  - @KierannS continues to be busy:
-    - *Blood Lords Player's Guide*
-    - *Lost Omens: Tian Xia World Guide*
-    - *Season of Ghosts #3: No Breath to Cry*
-    - *Season of Ghosts #4: To Bloom Below the Web*
-    - *Stolen Fate Player's Guide* (items by @Spappz 😏)
-    - *Wake the Dead #1*–*5*
-  - @Spappz likes kicking easy ones off the list:
-    - *A Few Flowers More*
-    - *Absalom: City of Lost Omens*
-    - *Dinner at Lionlodge*
-    - *Gatewalkers #2: They Watched the Stars*
-    - *Head-Shot the Rot* (technically no actual new content in this one lmao)
-    - *Malevolence*
-    - *Mark of the Mantis*
-    - *Quest for the Frozen Flame Player's Guide*
-    - *Shadows at Sundown*
-    - *The Enmity Cycle*
-  - A new challenger approaches: @kerbsy!
-   - *Rusthenge* (backgrounds by @Spappz 😏)
-- Added minor miscellaneous missing content (@miscoined, @Spappz)
-- Added divine sanctification filter to deities page (@Spappz)
-- @Spappz went on a crusade to slightly prettify the changelog
-  - Fix bullet-indentation (does anyone even read this?)
-  - Add a proper stagnation notice (please read this!)
-  - Fix the script that posts changelogs to [Discord](https://discord.gg/2hzNxErtVu) (reading this instead is acceptable 👍)
-- Fix minor formatting bugs in the Text Converter for backgrounds (@Spappz)
-- Fix *another* rare `text:` search-functionality bug (@Spappz)
-- *Many* typos/tags (@Spappz, @VytorCalixto, @miscoined)
+- The data-conversion train just doesn't stop. New sources added:
+  - *Curtain Call Player's Guide* (@KierannS)
+  - *Lost Omens: Highhelm* (@KierannS)
+  - *Wardens of Wildwood #1: Pactbreaker* (@Spappz)
+  - *Wardens of Wildwood #2: Severed at the Root* (@Spappz)
+  - Some more (but still not all) *Player Core* content (@Spappz)
+- Fix the halcyon and elemental spell-list filters being completely incorrect! (@Spappz)
+- Fixed a number of bugs with the text converter for items, and enable slightly better compatibility with remaster formatting (@Spappz)
+- Update dependencies (@Spappz)
+- Tighten linting/code-quality rules (@Spappz)
+- Typos/tags (@Spappz)
 
 **Note:** Pf2eTools is still stagnated as per [v0.8.5](https://github.com/Pf2eToolsOrg/Pf2eTools/releases/tag/v0.8.5). However, we are making good progress on the new site! An alpha is available to our [supporters](https://ko-fi.com/mrvauxs); you can also join our [Discord server](https://discord.gg/2hzNxErtVu) to receive more informal updates or just chat about things.