website: promote beta to stable

Author: SamWindell

website/versioned_docs/version-stable/about-the-project/beta-testing.mdx

@@ -55,3 +55,6 @@ Beta releases install just like stable releases and will overwrite any existing
 
 Version numbers indicate release order: for example, v1.0.0-beta.2 is newer than v1.0.0-beta.1, but both are preview versions that come before the final v1.0.0 release.
 
+## Always Stay Updated
+
+Always have the latest version of Floe - including beta features - by enabling _Include beta version when checking for updates_ in the preferences panel. This way, Floe will let you know when there's a new version available, whether it's stable or beta.

website/versioned_docs/version-stable/about-the-project/sponsorship.mdx

@@ -12,8 +12,9 @@ SPDX-License-Identifier: CC-BY-SA-4.0
 
 # Sponsorship
 
-Sponsoring Floe helps support its ongoing development and maintenance. As a sponsor, you can receive priority support and influence the direction of the project. Additionally, you can propose professional packages to the [Package Directory](/packages).
-e can also offer services to anyone interested in Floe library development.
+Sponsoring Floe helps support its ongoing development and maintenance. As a sponsor, you can receive priority support and influence the direction of the project. Additionally, you can submit professional high-quality packages to the [Package Directory](/packages).
+
+As another service, we can also help with converting or creating Floe sample libraries.
 
 Please contact [Sam](mailto:[email protected]) to discuss more details.
 

website/versioned_docs/version-stable/changelog.md

@@ -14,6 +14,14 @@ For instance: 0.0.1. Don't change the headings.
 -->
 
 # Changelog
+## 1.1.0
+- Fix pop sometimes possible at ping-pong loop boundary
+- Fix possible crash related to file paths on Windows.
+- Fix possible crash related to error reporting.
+- Fix possible package installation failure
+- Fix sometimes not correctly loading in Reaper or FL Studio, leaving UI looking correct but audio not reflective of the current state.
+- Major infrastructure improvements to how we build and release Floe.
+
 ## 1.1.0-beta.1
 - **Browser UI overhaul** (instruments, presets, IRs)
   - Filtering mode is now 'one' mode by default, and alternate modes for 'AND' or 'OR' filtering are selected in the 3-dots menu

website/versioned_docs/version-stable/develop/develop-libraries.mdx

@@ -19,6 +19,12 @@ Creating sample libraries for Floe **requires programming knowledge**. While Flo
 
 In the future, we're looking at tools that convert/generate Floe Lua scripts to allow non-programmers to create libraries.
 
+:::note
+
+We made these tools for our own use and are sharing them with the community. Consider contributing or [sponsorship](../about-the-project/sponsorship) if you'd like to see further investment in this area.
+
+:::
+
 ### What you'll need
 - Basic programming concepts (variables, functions, loops) or willingness to learn
 - Familiarity with text editors (Sublime Text, VS Code, etc.)
@@ -98,7 +104,7 @@ Here's a made-up example of a `floe.lua` file:
 
 ## How to get started
 
-1. Create a new folder in one of Floe's [sample library folders](../usage/sample-libraries). We recommend naming it 'Author Name - Library Name'.
+1. Create a new folder in one of Floe's [sample library folders](../key-concepts/folders). We recommend naming it 'Author Name - Library Name'.
 1. Create a file in that folder called `my-library.floe.lua`.
 1. Create a subfolder called `Samples` and put your audio files in there.
 1. Open the Lua file in your text editor. If you're not already familiar with an editor, then Sublime Text or Visual Studio Code are reasonable choices.

website/versioned_docs/version-stable/develop/develop-preset-banks.mdx

@@ -0,0 +1,57 @@
+---
+id: develop-preset-packs
+title: Develop Preset Banks
+hide_table_of_contents: true
+description: Best practices for developing preset banks for Floe
+---
+
+<!--
+SPDX-FileCopyrightText: 2025 Sam Windell
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+
+Floe's preset management is open; it's just based on the files and folders on your computer.
+
+Presets are saved as individual files using the <FAIcon icon="fa-solid fa-floppy-disk" /> save button at the top of Floe's UI. These files can be freely renamed and put into subfolders; this is how categories and hierarchies are created in the preset browser.
+
+## Preset Banks
+
+A _preset bank_ is small, optional, extension to this concept. By creating a `floe-preset-bank.ini` inside a folder of presets, it becomes a preset bank, where the entire tree of presets in the folder and all its subfolders become more easily identifiable and can feature metadata such as a subtitle and ID. 
+
+The preset bank file is a simple INI text file with the following fields - all are optional:
+
+```ini
+; A short and descriptive name for the preset bank.
+subtitle = My Preset Bank Name
+
+; Any kind of unique identifier. Typically you might use a reverse 
+; domain style string. Used so Floe can identify the bank uniquely.
+id = com.myname.mypresetbank
+
+; A version number - just a single integer. When installing a 
+; package, Floe can use this alongside the ID to determine if a bank 
+; can be updated rather than installed to a new location. Versioning
+; is only designed for simple additions/fixes. If you make major
+; changes, it's probably better to create a new preset bank, 
+; "My Bank 2", with a new ID.
+minor_version = 1
+```
+
+You can create this INI file with any text editor such as Notepad or TextEdit. You just need to type in the various `field = value` with new lines between them.
+
+A side note for the particularly discerning user: Floe automatically identifies some well-known factory preset folders as preset banks even without the metadata file present. This is because some banks were created before the preset bank feature was added. We chose to enrich them with metadata retroactively.
+
+## Packaging
+
+Once you've created your folder of presets and added a `floe-preset-bank.ini` file (optional but recommended), you can ZIP it up for distribution.
+
+Read about packaging on the [packaging](./packaging) page.
+
+Use the packager command-line tool, or alternatively package it manually. To manually package your bank first rename your bank folder to something like `My Preset Bank`. Next, put that into a folder called `Presets`. Next, put `Presets` into another folder `My Preset Bank - Floe Package`, then right-click and ZIP that folder. You should now have a ZIP called `My Preset Bank - Floe Package.zip` with a subfolder `Presets` and your bank folder inside that. The resulting ZIP file will contain the structure that _Floe packages_ require (Presets subfolder at the top level). Test your package by trying to install it using Floe's _Install package_ button. Refer to the packaging page for more details if needed.
+
+## Best Practices
+- Make presets all feel the same volume: the master peak meter on Floe's GUI should just be the yellow zone when the preset is played at its fullest.
+- Give each preset a unique, descriptive name suggesting its tone or usage. Don't use all capital letters. Don't include a 'type' prefix such as "PAD - " or "LD - ".
+- Add as many tags as is relevant to the preset. Read more about tags on the [tags and folders](./tags-and-folders) page.
+- Keep the description short and ending with a period.
+- Organise presets into folders using your file browser. You can rename presets and folders as you like. See the best practises for folders on the tags and folders page.

website/versioned_docs/version-stable/develop/develop-preset-packs.mdx

@@ -13,11 +13,11 @@ SPDX-License-Identifier: CC-BY-SA-4.0
 import data from "@site/static/generated-data.json";
 import CodeBlock from '@theme/CodeBlock';
 
-The easiest and most reliable way to distribute your Floe content is with [Floe Packages](../packages/about-packages).
+The easiest and most reliable way to distribute your Floe content is with [Floe Packages](../key-concepts/components#packages).
 
 Floe Packages are ZIP files containing **sample libraries** (which provide instruments and IRs) and/or **presets** (ready-to-use professional sounds). Packages are what users download and install into Floe.
 
-Floe offers an easy-to-use GUI for [installing packages](../packages/install-packages). This installation process carefully considers existing content, versions, installation preferences, and whether installed libraries have been modified. The result should 'just work' or provide clear instructions on what to do next.
+Floe offers an easy-to-use GUI for [installing packages](../installation/install-packages). This installation process carefully considers existing content, versions, installation preferences, and whether installed libraries have been modified. The result should 'just work' or provide clear instructions on what to do next.
 
 As with Floe's sample library format, openness is key. That's why Floe Packages are just normal ZIP files with a specific structure. Anyone can create them and anyone can open them. Additionally, it gives the user the option to extract them manually rather than use Floe's GUI if they wish.
 

website/versioned_docs/version-stable/develop/packaging.mdx

@@ -15,15 +15,15 @@ Get up and running with Floe in just a few simple steps.
 
 Floe is an **engine** — it's empty without sample libraries.
 
-If you already have packages (perhaps sent to your email), begin _Setting up Floe_. Otherwise, browse the [packages](/packages) page first to discover free and paid options.
+If you already have packages (perhaps sent to your email), jump below to _Setting up Floe_. Otherwise, browse the [packages](/packages) page first to discover free and paid options.
 
 ## Setting up Floe
 
 1. **[Download Floe](/download)** and install it on your computer.
 1. **Download your packages** of your choice. **No need to unzip/extract them**.
 1. **Open your DAW**.
-1. **Add the Floe plugin** - often found under 'Floe Audio' in your plugin list.
-1. **Install your packages** by opening the Floe's Preferences <FAIcon icon="fa-solid fa-cog" /> and clicking the **Install package** button.
+1. **Add the Floe plugin** - often found as a 'virtual instrument' under 'Floe Audio' in your plugin list.
+1. **[Install your packages](../installation/install-packages)** by opening the Floe's Preferences <FAIcon icon="fa-solid fa-cog" /> and clicking the **Install package** button.
 1. **Select your downloaded package** ZIP file(s). After a few moments, your libraries and presets will be available to use.
 
 ## Load a preset
@@ -47,4 +47,10 @@ Instruments are the building blocks in Floe. Sometimes an instrument is a single
 1. **Choose an instrument** by clicking on one from the list on the right.
 1. **Play some notes** on your MIDI keyboard or DAW piano roll and notice how the sound has changed.
 
+<div style={{marginBottom: '4em'}}></div>
 
+:::note
+
+Floe is continuously improving. Share your feedback or feature ideas on GitHub, forums or via email.
+
+:::