1.0.0 release (#244)

* initial commit

* More updates

* More updates

* More updates

* Add news entyr

* Update image

* Update gallery images

* Refactor blog post

* Breaking change for notification methods

* Fix notification plugin docs

* Add more breaking changeas

* Feature updates

* Add donation links

* blog post - machine registry updates

* Add note on docker image change

* Add note on changelog file

* Update _posts/2025-08-25-1.0.0.md

Co-authored-by: Matthias Mair <code@mjmair.com>

* Update _posts/2025-08-25-1.0.0.md

Co-authored-by: Matthias Mair <code@mjmair.com>

* Update _posts/2025-08-25-1.0.0.md

Co-authored-by: Matthias Mair <code@mjmair.com>

* Update _posts/2025-08-25-1.0.0.md

Co-authored-by: Matthias Mair <code@mjmair.com>

* Add note on user experience survey

* Add final note about survey

* Fix stats file

* Update blog post

* Ignore polar.sh links

* Fix links

* More link fixes

* Further fixes

* Fix python link

---------

Co-authored-by: Matthias Mair <code@mjmair.com>

.github/workflows/deploy.yml

@@ -21,7 +21,7 @@ jobs:
         uses: limjh16/jekyll-action-ts@v2
         with:
           enable_cache: true
-      - run: bundle exec htmlproofer ./_site --no-check-external-hash --no-enforce-https --ignore-urls "/localhost/,/www.linkedin.com/,/cloud.digitalocean.com/,marketplace.digitalocean.com/,/reddit.com/r/inventree/,/twitter.com/inventreedb/,/github.com/,/developer.digikey.com/,/patreon.com/,/partkeepr.org/,/download.dymo.com/"
+      - run: bundle exec htmlproofer ./_site --no-check-external-hash --no-enforce-https --ignore-urls "/localhost/,/www.linkedin.com/,digitalocean.com,/cloud.digitalocean.com/,marketplace.digitalocean.com/,polar.sh,/reddit.com/r/inventree/,/twitter.com/inventreedb/,/github.com/,/developer.digikey.com/,/patreon.com/,/partkeepr.org/,/download.dymo.com/,brother.com.au"
         name: Check links
       - name: Deploy
         if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main'}}

_data/functions/extras.yml

@@ -1,10 +1,10 @@
 functions:
   - title: Build Parts
     text: Inventree features a build management system to help you track the progress of your builds. Builds consume stock items to make new parts, you can decide to automatically or manually allocate parts from your current inventory.
-    link: https://docs.inventree.org/en/stable/part/part/
+    link: https://docs.inventree.org/en/stable/part
   - title: Report
     text: Generate a wide range of reports using custom templates.
-    link: https://docs.inventree.org/en/stable/report/report/
+    link: https://docs.inventree.org/en/stable/report
   - title: Extend and Customize
     text: InvenTree is designed to be highly extensible. If the core InvenTree functionality does not meet your particular need, InvenTree provides a RESTful API, a native Python library, and a powerful plugin system.
-    link: https://docs.inventree.org/en/stable/api/api/
+    link: https://docs.inventree.org/en/stable/api/

_data/functions/general.yml

@@ -5,15 +5,15 @@ text:
 functions:
   - title: Organize Parts
     text: Parts are the fundamental element of any inventory. InvenTree groups parts into structured categories which allow you to arrange parts to meet your particular needs. 
-    link: https://docs.inventree.org/en/stable/part/part/
+    link: https://docs.inventree.org/en/stable/part
   - title: Manage Suppliers
     text: InvenTree allows you to easily create, modify or delete suppliers and supplier items linked to any part in your inventory.
-    link: https://docs.inventree.org/en/stable/order/company/#suppliers
+    link: https://docs.inventree.org/en/stable/concepts/company/#suppliers
   - title: Instant Stock Knowledge
     text: Instantly view current stock for a certain part, in a particular location, or required for an individual build.
     extend: Stock items are organized in cascading locations and sub-locations, allowing flexible inspection of stock under any location. Stock items can be serialized for tracking of individual items, and test results can be stored against a serialized stock item for the purpose of acceptance testing and commissioning.
-    link: https://docs.inventree.org/en/stable/stock/stock/
+    link: https://docs.inventree.org/en/stable/stock
   - title: BOM Management
     text: Intelligent <strong>B</strong>ill <strong>o</strong>f <strong>M</strong>aterial management provides a clear understanding of the sub-parts required to make a new part.
     extend: InvenTree allows you to upload simple BOM files in multiple formats, and download a detailed BOM with all the information stored in its database.
-    link: https://docs.inventree.org/en/stable/build/bom/
+    link: https://docs.inventree.org/en/stable/manufacturing/bom/

_news/2022-12-12-0.9.0.md

@@ -18,4 +18,4 @@ A new version of the [python library](https://github.com/inventree/inventree-pyt
 
 ### Mobile App
 
-We've also released an updated version of the [mobile app](https://docs.inventree.org/en/stable/app/app/) - available for Android and iOS devices.
+We've also released an updated version of the [mobile app](https://docs.inventree.org/en/stable/app/) - available for Android and iOS devices.

_news/2025-09-15-1.0.0.md

@@ -0,0 +1,10 @@
+---
+author: SchrodingersGat
+title: 1.0.0 Release
+---
+
+### 1.0.0 Release
+
+We are pleased to announce the 1.0.0 stable release, which represents a significant milestone in the development of InvenTree.
+
+- View the [release notes](https://github.com/inventree/InvenTree/releases/tag/1.0.0)

_posts/2021-10-25-starting.md

@@ -2,6 +2,6 @@
 author: matmair
 title: Starting with templates
 ---
-A good starting-point for developing your own plugin is taking a look at the [documentation](https://docs.inventree.org/en/stable/extend/plugins/).
+A good starting-point for developing your own plugin is taking a look at the [documentation](https://docs.inventree.org/en/stable/plugins/).
 
 You could also use one of the current plugins as a sample.

_posts/2022-12-12-0.9.0.md

@@ -39,17 +39,17 @@ Barcode support has been significantly improved, allowing custom barcode functio
 - Custom barcodes can now be assigned to *Stock Location* instances
 - Custom barcodes can now be assigned to *Supplier Part* instances
 
-Read more about the updated barcode support in [the InvenTree documentation](https://docs.inventree.org/en/stable/barcodes/barcodes/).
+Read more about the updated barcode support in [the InvenTree documentation](https://docs.inventree.org/en/stable/barcodes/).
 
 ### Builtin Plugins
 
 As part of the ongoing improvements to the plugin system, InvenTree now features a number of "builtin" plugins. These plugins are always active (even if custom plugin support is disabled for the server) and provide core InvenTree functionality in a way which aligns with the operation of the plugin system. This is intended to streamline the way in which plugins are implemented, as core components of the code are now offloaded to the plugin with a simpler interface.
 
-We have also made some significant improvements to the [plugin system documentation](https://docs.inventree.org/en/stable/extend/plugins/).
+We have also made some significant improvements to the [plugin system documentation](https://docs.inventree.org/en/stable/plugins/).
 
 ### Validation Plugins
 
-A completely new type of plugin introduced in this release is the [validation plugin mixin](https://docs.inventree.org/en/stable/extend/plugins/validation/). This plugin allows users to implement custom validation methods for various database fields. In addition to allowing validation of field values against complex custom rules, this plugin allows automated generation of the "next value" for certain fields, such as serial numbers and batch codes.
+A completely new type of plugin introduced in this release is the [validation plugin mixin](https://docs.inventree.org/en/stable/plugins/mixins/validation/). This plugin allows users to implement custom validation methods for various database fields. In addition to allowing validation of field values against complex custom rules, this plugin allows automated generation of the "next value" for certain fields, such as serial numbers and batch codes.
 
 ### News Reader
 
@@ -61,7 +61,7 @@ Now that the new website is live, a [news feed](/news) is available. If enabled,
 
 ### Part Scheduling
 
-The [Part Scheduling](https://docs.inventree.org/en/stable/part/scheduling/) functionality has received some updates in this release. If enabled, the *Part Scheduling* tab shows predicted future stock levels, based on incoming and outgoing orders.
+The Part Scheduling functionality has received some updates in this release. If enabled, the *Part Scheduling* tab shows predicted future stock levels, based on incoming and outgoing orders.
 
 ### Supplier Part Pack Size
 

_posts/2023-02-06-0.10.0.md

@@ -15,7 +15,7 @@ A lot of work has gone into improving [Single Sign On (SSO)](https://docs.invent
 
 ### Currency Conversion
 
-In a major improvement for currency support, conversion between different currencies is now performed "client side". This means that data tables which contain money values with different currencies can now be added together - and in a computationally efficient manner. Currency exchange rate data is now made available via [the API](https://docs.inventree.org/en/stable/api/api/) - paving the way for future feature development in this area.
+In a major improvement for currency support, conversion between different currencies is now performed "client side". This means that data tables which contain money values with different currencies can now be added together - and in a computationally efficient manner. Currency exchange rate data is now made available via [the API](https://docs.inventree.org/en/stable/api/) - paving the way for future feature development in this area.
 
 ### Pricing Features
 

_posts/2023-04-17-0.11.0.md

@@ -11,7 +11,7 @@ We are thrilled to announce the latest stable release of Inventree, version 0.11
 
 ### Return Orders
 
-The addition of [Return Orders](https://docs.inventree.org/en/stable/order/return_order/) is a significant new feature, which allows users to easily process and manage returned items, whether they are due to customer refunds or defective products. With the ability to track the status of return orders and the associated inventory movements, businesses can better manage their inventory levels, reduce waste, and improve their customer service.
+The addition of [Return Orders](https://docs.inventree.org/en/stable/sales/return_order/) is a significant new feature, which allows users to easily process and manage returned items, whether they are due to customer refunds or defective products. With the ability to track the status of return orders and the associated inventory movements, businesses can better manage their inventory levels, reduce waste, and improve their customer service.
 
 ### Stocktake Reports
 
@@ -25,7 +25,7 @@ The latest release provides improved barcode support, with the ability to genera
 
 InvenTree's latest release includes improved report template functionality with better currency rendering support, enabling businesses to create professional and accurate reports. This feature allows for more detailed and customizable reports, including the ability to display currency symbols and automatically convert currency values to the appropriate format based on the user's settings, saving time and effort.
 
-Refer to the [reporting documentation](https://docs.inventree.org/en/stable/report/report/) for further details.
+Refer to the [reporting documentation](https://docs.inventree.org/en/stable/report) for further details.
 
 ### Search Results
 

_posts/2023-06-26-0.12.0.md

@@ -23,14 +23,14 @@ Additionally, part parameters can now also specify real world units!
 
 For more information on this new feature, refer to the documentation:
 
-- [Part units](https://docs.inventree.org/en/stable/part/part/#units-of-measure)
+- [Part units](https://docs.inventree.org/en/stable/part#units-of-measure)
 - [Part parameter units](https://docs.inventree.org/en/stable/part/parameter/#parameter-units)
 
 ### Project Codes
 
 To streamline project management and order tracking, InvenTree now offers configurable project codes. These codes can be created and assigned to orders, providing a convenient way to organize and categorize your inventory based on specific projects. This enhancement enhances overall visibility and enables efficient project-based inventory management.
 
-Read more about project code support [in the documentation](https://docs.inventree.org/en/stable/order/project_codes/)
+Read more about project code support [in the documentation](https://docs.inventree.org/en/stable/concepts/project_codes/)
 
 ### Parameter Types
 
@@ -44,7 +44,7 @@ To enhance the usability and efficiency of InvenTree's part parameters, the late
 
 ### Report Plugins
 
-InvenTree introduces a new [plugin mixin class](https://docs.inventree.org/en/stable/extend/plugins/report/) that allows for custom context variables to be injected into reports. This enhancement provides extensive customization options when generating reports, enabling you to include additional information relevant to your business processes. With improved report functionality, you can present inventory data in a more comprehensive and meaningful way.
+InvenTree introduces a new [plugin mixin class](https://docs.inventree.org/en/stable/plugins/mixins/report/) that allows for custom context variables to be injected into reports. This enhancement provides extensive customization options when generating reports, enabling you to include additional information relevant to your business processes. With improved report functionality, you can present inventory data in a more comprehensive and meaningful way.
 
 ### Build Orders Consume Stock
 
@@ -52,7 +52,7 @@ The build order interface in InvenTree has received a major overhaul, resulting
 
 ### Scrap Build Order Outputs
 
-InvenTree's latest release introduces a valuable feature that allows users to [scrap partially completed or failed build outputs](https://docs.inventree.org/en/stable/build/output/#scrap-build-output) while retaining traceability. In real-world manufacturing scenarios, it is common for builds to encounter challenges or errors, resulting in the need to discard certain outputs. With the new scrap build outputs functionality, you can easily identify and remove faulty or incomplete build outputs from your inventory. This feature ensures accurate stock tracking and maintains a clear audit trail, improving reliability and efficiency in your manufacturing processes.
+InvenTree's latest release introduces a valuable feature that allows users to [scrap partially completed or failed build outputs](https://docs.inventree.org/en/stable/manufacturing/output/#scrap-build-output) while retaining traceability. In real-world manufacturing scenarios, it is common for builds to encounter challenges or errors, resulting in the need to discard certain outputs. With the new scrap build outputs functionality, you can easily identify and remove faulty or incomplete build outputs from your inventory. This feature ensures accurate stock tracking and maintains a clear audit trail, improving reliability and efficiency in your manufacturing processes.
 
 ### Image Uploads
 
@@ -60,7 +60,7 @@ To enrich documentation and enhance visual representation, InvenTree now support
 
 ### Address Management
 
-InvenTree now offers [increased support for address management](https://docs.inventree.org/en/stable/order/company/#addresses) with a more complex address database model. This enhancement enables businesses to manage addresses more effectively, accommodating various scenarios such as multiple shipping locations, customer addresses, and supplier information. With improved address management, you can maintain accurate records and ensure smooth logistics operations.
+InvenTree now offers [increased support for address management](https://docs.inventree.org/en/stable/concepts/company/#addresses) with a more complex address database model. This enhancement enables businesses to manage addresses more effectively, accommodating various scenarios such as multiple shipping locations, customer addresses, and supplier information. With improved address management, you can maintain accurate records and ensure smooth logistics operations.
 
 ### SVG Support
 

_posts/2024-03-02-0.14.0.md

@@ -79,7 +79,7 @@ A significant number of new features have been added to InvenTree in this releas
 
 ### Enhanced Validation
 
-Enhanced custom validation is implemented in [PR 6410](https://github.com/inventree/InvenTree/pull/6410). This addition allows for more comprehensive validation of models by integrated plugins. Refer to the [updated validation plugin docs](https://docs.inventree.org/en/stable/extend/plugins/validation/) for more information.
+Enhanced custom validation is implemented in [PR 6410](https://github.com/inventree/InvenTree/pull/6410). This addition allows for more comprehensive validation of models by integrated plugins. Refer to the [updated validation plugin docs](https://docs.inventree.org/en/stable/plugins/mixins/validation/) for more information.
 
 ### API Documentation
 

_posts/2024-03-13-docker.md

@@ -242,7 +242,7 @@ Caddy, the proxy server used in the InvenTree Docker setup, automatically config
 
 #### Further Reading
 
-This tutorial is a simple guide to getting InvenTree up and running in a Docker container. For more advanced usage, you should read the [InvenTree Setup Guide](https://docs.inventree.org/en/stable/start/intro/) guide, which provides a lot more detail about the InvenTree Docker setup.
+This tutorial is a simple guide to getting InvenTree up and running in a Docker container. For more advanced usage, you should read the [InvenTree Setup Guide](https://docs.inventree.org/en/stable/start/) guide, which provides a lot more detail about the InvenTree Docker setup.
 
 #### Project Sponsorship
 

_posts/2025-09-15-1.0.0.md

@@ -0,0 +1,317 @@
+---
+author: SchrodingersGat
+title: 1.0.0 Release
+---
+
+## 1.0.0 Release
+
+The 1.0.0 release marks a major milestone for the InvenTree project. Not only does it represent an important step in the evolution of the software, but it also introduces a host of new features and improvements that enhance the user experience.
+
+This release includes significant updates to the user interface, performance optimizations, and a range of new functionalities that have been requested by our community.
+
+With [over 600 closed issues](https://github.com/inventree/InvenTree/pulls?q=is%3Apr+milestone%3A1.0.0+), this release is a testament to the hard work and dedication of our contributors. We are excited to see how these changes will benefit users and help them manage their inventories more effectively.
+
+### Changelog
+
+For a full list of changes made in this release, please see the [release notes on GitHub](https://github.com/inventree/InvenTree/releases/tag/1.0.0). The major changes are documented below, but there are many other improvements and bug fixes that have been implemented as well.
+
+You can also view a [full changelog between 0.17.0 and 1.0.0](https://github.com/inventree/InvenTree/compare/0.17.0...1.0.0)
+
+Going forward, we will be tracking major project changes in an internal [CHANGELOG file](https://github.com/inventree/InvenTree/blob/master/CHANGELOG.md) - this file will be updated with each release, and will provide an overview of the major changes made in each version. This file is in addition to the release notes which are provided by GitHub.
+
+### Update Procedure
+
+To update to the latest version of InvenTree, please follow the updating instructions provided in the [InvenTree documentation](https://docs.inventree.org). Note that the particular update procedure may vary depending on your installation method.
+
+## User Experience Survey
+
+In conjunction with the 1.0.0 release, we have launched a [user experience survey](https://forms.gle/a7mFzqZj57FeS7ds9) to gather feedback from our community. This survey is designed to help us understand how users are utilizing InvenTree, what features they find most valuable, and where we can improve.
+
+The survey is anonymous and should take no more than 10 minutes to complete. We encourage all users to participate, as your feedback is invaluable in shaping the future of InvenTree. Please consider taking the survey and sharing it with others who use InvenTree.
+
+## Breaking Changes
+
+As with any major release, there are some breaking changes that users should be aware of. These changes may require adjustments to existing installations, plugins, or customizations.
+
+The most significant breaking changes are documented below, but users should also refer to the [full list of breaking changes](https://github.com/inventree/InvenTree/pulls?q=is%3Apr+milestone%3A1.0.0+label%3Abreaking).
+
+### User Interface Overhaul
+
+By far the largest change introduced in this release is the new user interface. The UI has been completely refactored to use a modern javascript / React framework, which allows for a more responsive and dynamic user experience. This change not only improves the performance of the application but also makes it easier to maintain and extend in the future.
+
+The new UI is now available at the `/web/` endpoint - and the old UI has been removed entirely.
+
+Note that old URLs have been remapped to the new UI, so users should not experience any issues with bookmarks or links that point to the old interface.
+
+The general "look and feel" of the InvenTree UI remains consistent with previous versions, but the underlying technology has been updated to provide a more robust and flexible foundation for future development.
+
+While we have made every effort to ensure that the new UI is compatible with existing data and functionality, there may be some edge cases where users encounter issues. We encourage users to report any problems they encounter so that we can address them promptly. In particular, if there are any features that are missing or not functioning as expected, please let us know [via GitHub issues](https://github.com/inventree/InvenTree/issues).
+
+### Plugin System Enhancements
+
+The plugin system has received significat attention in this release. In particular, the plugin system now provides a mechanism for plugins to render their own user interface componenents within the new UI framework.
+
+To this end, we have released an [npm package](https://www.npmjs.com/package/@inventreedb/ui) that provides an interface layer for plugins looking to render custom components within the InvenTree UI.
+
+Additionally, we now have a [plugin creation tool](https://github.com/inventree/plugin-creator/) which allows users to quickly scaffold InvenTree plugins.
+
+### Machine Registry Enhancements
+
+The machine registry has [received an overhaul](https://github.com/inventree/InvenTree/pull/10150) which introduces a breaking change for any plugins which implement custom machine registry functionality.
+
+If you have implemented a custom machine registry plugin, you will need to update your plugin to work with the new machine registry system. In particular, the plugin must now implement a new `MachineDriverMixin` class, which provides a consistent interface for interacting with the machine registry.
+
+### User Interface Plugins
+
+This change may require some adjustments for users who have customized their InvenTree installation, particularly if they have created custom templates or plugins that rely on the old UI structure.
+
+Any plugins which have not been updated to work with the new UI will not function correctly, and will need to be adjusted to work with the new interface. This is after we [removed the old PanelMixin class](https://github.com/inventree/InvenTree/pull/8828). This means that any plugins which inherit from the PanelMixin class will now throw an error when loaded.
+
+The new UI plugin system provides a significant amount of *context* information to the plugins at render time. This means that plugins can now access information about the current user, the current page, and other relevant data when rendering their components.
+
+Additionally, the plugins can access the API directly from the UI, allowing for more dynamic interactions and data retrieval, without the plugin needing to authenticate separately.
+
+This plugin context system was introduced in [#9439](https://github.com/inventree/InvenTree/pull/9439), but further additions and improvements have been made in subsequent pull requests.
+
+The [@inventreedb/ui](https://www.npmjs.com/package/@inventreedb/ui) npm package provides full type definitions for the plugin context, making it easier for developers to create plugins that integrate seamlessly with the new UI.
+
+Further, the npm package provieds a set of pre-defined react components which can be reused by plugins.
+
+Scaffolding a UI plugin from scratch represents a significant amount of work, so we have created a [plugin creation tool](https://github.com/inventree/plugin-creator/) which generates all of the necessary boilerplate code to get started quickly. This tool can be used to create a new plugin that is ready to be extended with custom functionality.
+
+To integrate seamlessly with the UI, plugin developers should be aware that some *core* libraries (such as *react* / *mantine* / *lingui*) must be externalized, as they are already provided by the InvenTree UI. This means that plugins should not include their own versions of these libraries, as this can lead to conflicts and unexpected behavior.
+
+Note that this is all handled automatically by the plugin creation tool, so developers should not need to worry about this unless they are creating plugins manually.
+
+### Notification Plugins
+
+We have changed the way that notification methods can be [implented via plugins](https://github.com/inventree/InvenTree/pull/9735). This change was made to ensure that custom notification methods were able to be loaded and unloaded correctly, and to provide a more consistent approach for implementing notification methods across different plugins.
+
+*However* - this change is *not* backwards compatible with existing plugins that implement notification methods. Plugin developers will need to update their plugins to use the new notification system in order to continue providing custom notification methods.
+
+### Builtin Plugins
+
+The InvenTree project now includes a number of builtin plugins that provide additional functionality and features. These plugins are designed to work seamlessly with the new UI and provide a range of enhancements to the core InvenTree functionality.
+
+Some of these plugins are *mandatory* - as they are required for the core functionality of InvenTree. These mandatory plugins are installed automatically when InvenTree is installed, and cannot be disabled.
+
+### Docker Changes
+
+Our [official docker image](https://hub.docker.com/r/inventree/inventree) is now based on a Debian image, rather than Alpine. [This change](https://github.com/inventree/InvenTree/pull/10227) was made due to a number of limitations with the Alpine image. The move to a Debian image also brings the docker image closer to the other installation methods, and the devcontainer setup.
+
+Functionally, the new docker image should behave identically to the old image, and users should not experience any issues when updating.
+
+Additionally, we have updated the [supported postgres version](https://github.com/inventree/InvenTree/pull/9041) in our docker image from version 13 to version 17.
+
+For new installations, this should not cause any issues, as the docker image will automatically pull the latest version of postgres.
+
+For existing installations, this will only make a difference if you wish to update your existing database. Note that our docker image will still support connection to older versions of postgres, so users can continue to use their existing database without any issues.
+
+### API Changes
+
+There have been a significant number of changes to the InvenTree API in this release, although the majority of these changes are backwards compatible.
+
+All API changes are [documented in the source code](https://github.com/inventree/InvenTree/blob/master/src/backend/InvenTree/InvenTree/api_version.py), and users can refer to this file to see the specific changes that have been made.
+
+Additionally, the [API schema is documented](https://docs.inventree.org/en/stable/api/schema/) and provides a comprehensive overview of the available endpoints and their parameters.
+
+### Stock Item Creation
+
+Creation of stock items via the API has been adjusted, to ensure that the return type is consistent. Now, the return type is always an array of items, even if only a single item is created. Refer to [PR #9969](https://github.com/inventree/InvenTree/pull/9969) for more information on this change.
+
+### Auth Changes
+
+We have refactored our authentication framework significantly, both to support the new UI and also to align with modern best practices.
+
+These changes should not affect most users, as we have endeavored to maintain compatibility with existing authentication methods. However, users who have implemented custom authentication mechanisms may need to review their code to ensure compatibility with the new framework.
+
+In particular we have updated our [django-allauth framework](https://github.com/inventree/InvenTree/pull/6293) to align with changes to that library.
+
+### Bulk Update Mixin
+
+In [PR #9313](https://github.com/inventree/InvenTree/pull/9313) we introduced a "BulkUpdateMixin" class which allows some API endpoints to support bulk updates. This mixin can be used to extend existing API endpoints to allow for bulk updates of objects, which can significantly improve performance when updating large datasets.
+
+### Part Scheduling
+
+The existing "Part Scheduling" feature has been removed in this release, and replaced with a plugin-based solution. This change was made to allow for greater flexibility and customization of the scheduling functionality, as well as to improve performance and maintainability.
+
+Refer to the [InvenTree Stock Forecasting plugin](https://github.com/inventree/inventree-stock-forecasting) to replace the old part scheduling functionality. 
+
+### Part Stocktake
+
+The "Part Stocktake" feature has been refactored to make use of the new import/export framework. Prior to `1.0.0`, the concept of "stocktake" referred to two separate concepts:
+
+1. The ability to provide a snapshot of the current stock levels for a part
+2. Record historical stock levels for a part
+
+These are now split into two separate features:
+
+#### Stocktake Export
+
+Exporting stocktake data is now handled by a provided export plugin, which integrates into the refactored data export framework. This means that the "stocktake" feature is no longer a separate exporter pathway. Refer to the InvenTree documentation for details on how to use the new stocktake export functionality.
+
+#### Stock History
+
+The "Stock History" feature remains in place, and allows users to view the historical stock levels for a part. This feature provides a detailed view of how stock levels have changed over time, and can be useful for tracking inventory trends and identifying potential issues.
+
+Refer to [PR #10124](https://github.com/inventree/InvenTree/pull/10124) for further information on this change.
+
+### Auto-Create Child Builds
+
+The "auto-creation of child builds" feature has been removed from the core functionality, as it was not configurable and too narrowly scoped to be useful for most users. This feature has been replaced with a more flexible plugin-based solution, which allows users to create custom logic for automatically creating child builds based on their specific requirements.
+
+Refer to [PR #9574](https://github.com/inventree/InvenTree/pull/9574) for more information.
+
+### Remove django-import-export
+
+In [#8685](https://github.com/inventree/InvenTree/pull/8685) we removed the [django-import-export](https://django-import-export.readthedocs.io/en/latest/) framework, which is what was previously used for data import and export. This has been replaced with a [custom API driven solution](https://github.com/inventree/InvenTree/issues/8686) which is more flexible and easier to use. Our new framework runs in the background worker, allowing for processing of large datasets without blocking the user interface (or causing the web server to timeout).
+
+Our data import and export framework has been completely rewritten, and replaced with a custom API driven solution.
+
+### Stock Return
+
+The "Stock Return" functionality has been expanded to allow for stock to be returned after having been consumed by a build order. To facilitate this, the API has been refactored to allow for stock returns to be processed more efficiently, and the user interface has been updated to reflect these changes.
+
+However this does represent a breaking change to the API, and users who have implemented custom logic for handling stock returns will need to update their code to accommodate the new API structure.
+
+Refer to [PR #10132](https://github.com/inventree/InvenTree/pull/10132) for more information on this change.
+
+## New Features / Improvements
+
+There are a number of new features and improvements in this release, many of which have been requested by our community. Some of the most notable changes include:
+
+### Performance Improvements
+
+We have made significant performance improvements across the board, particularly in areas such as data loading and rendering. The new UI framework is designed to be more efficient, which should result in a smoother experience for users, especially when dealing with large datasets.
+
+The API has also been optimized to reduce response times and improve overall performance.
+
+### Dashboard
+
+The new user interface now includes a customizable dashboard that allows users to add, remove, and rearrange widgets according to their preferences. This feature provides a more personalized experience and enables users to focus on the information that is most relevant to them.
+
+This dashboard can be extended with custom widgets provided by plugins, allowing for even greater flexibility and customization.
+
+### Order Calendar Views
+
+We have [reimplemented calendar views](https://github.com/inventree/InvenTree/pull/8933) for purchase orders, sales orders, and build orders. These calendar views allow users to see their orders in a calendar format, making it easier to visualize and manage their order schedules.
+
+### Email Enhancements
+
+[PR #9608](https://github.com/inventree/InvenTree/pull/9608) enhances email support capabilities, including plugin support for sending and receiving emails.
+
+### Order Start Dates
+
+In [#PR 8966](https://github.com/inventree/InvenTree/pull/8966) we introduced a new "start date" field for purchase orders and sales orders. This field allows users to specify the date when the order is expected to start processing, which can be useful for planning and scheduling purposes. In [#8915](https://github.com/inventree/InvenTree/pull/8915) the "start date" field was also added for build orders.
+
+### Reporting Printing
+
+Printing of reports and labels is now [offloaded to the background worker](https://github.com/inventree/InvenTree/pull/9199), allowing for more efficient processing of large reports without blocking the user interface. This change also introduces progress tracking for report generation, so users can see the status of their report as it is being generated.
+
+Additionally, reports and labels can now be generated programatically from plugins, allowing for greater flexibility and customization of report generation.
+
+### Report Merging
+
+[PR #9532](https://github.com/inventree/InvenTree/pull/9532) introduces a new feature that allows users to merge multiple items into a single report. When generating reports against multiple items, users can now select to render the report as a single document, rather than generating separate reports for each item.
+
+This is selected as an option against a particular report template. Note that it requires the report template to be designed to support merging, as not all templates will be suitable for this feature.
+
+### Part Parameter Tracking
+
+[PR #10023](https://github.com/inventree/InvenTree/pull/10023) tracks the user who last modified a part parameter, and when it was last modified. This change provides greater visibility into changes made to part parameters.
+
+### External Build Orders
+
+In [PR #9312](https://github.com/inventree/InvenTree/pull/9312) we introduced support for external build orders, allowing users to manage build orders that are fulfilled by external suppliers. This feature is particularly useful for users who need to manage builds that are outsourced to third-party manufacturers or suppliers.
+
+Refer to the [InvenTree documentation](https://docs.inventree.org/en/latest/manufacturing/external/) for further information.
+
+### BOM Enhancements
+
+Added support for greater flexibility in managing Bills of Materials (BOMs) - refer to [#10042](https://github.com/inventree/InvenTree/pull/10042) for details.
+
+### Build Order Consume
+
+[PR #8191](https://github.com/inventree/InvenTree/pull/8191) adds the ability to partially consume stock against a build order, even if the build order is not yet complete. This feature allows users to consume stock as it allocated, rather than waiting for the entire build order to be completed. This provides users greater flexibility in managing their inventory and build orders, and can help to reduce delays in production.
+
+### Serial Number Navigation
+
+[PR #9505](https://github.com/inventree/InvenTree/pull/9505) adds the ability to navigate between serial numbers in the user interface.
+
+### Override Global Settings
+
+[PR #9718](https://github.com/inventree/InvenTree/pull/9718) introduces the ability to override global settings via system-level configuration. This allows system administrators to "lock down" certain settings, preventing users from changing them in the user interface. This is particularly useful for ensuring consistency across installations and preventing accidental changes to critical settings.
+
+### Override Plugins
+
+In [PR #10094](https://github.com/inventree/InvenTree/pull/9718) we introduced the ability for system adminstrators to mark certain plugins as "mandatory" at the system configuration level. This means that these plugins cannot be disabled or uninstalled by users, ensuring that critical functionality remains available.
+
+## Bug Fixes
+
+There have been a *significant* number of bug fixes in this release, with over [150 tagged PRs](https://github.com/inventree/InvenTree/pulls?q=is%3Apr+milestone%3A1.0.0+label%3Abug+).
+
+Note that many of these bug fixes are related to implementation of the new interface, and may not represent issues present in previous versions of the InvenTree software.
+
+## Contributing
+
+As always, we would like to extend our heartfelt thanks to all of the contributors who have worked tirelessly to make this release possible. The InvenTree project is a community-driven effort, and it is only through the contributions of our users that we are able to continue improving and evolving the software.
+
+There are now [over 100 contributors](https://github.com/inventree/InvenTree/graphs/contributors) to the InvenTree project, and we are grateful for each and every one of you. Whether you have contributed code, reported bugs, provided feedback, or simply used the software, your support is invaluable to us.
+
+### New Contributors
+
+The following developers made their first contributions to the InvenTree project in this release:
+
+* @gunstr made their first contribution in https://github.com/inventree/InvenTree/pull/9274
+* @reilly-callaway made their first contribution in https://github.com/inventree/InvenTree/pull/9575
+* @aluminum-ice made their first contribution in https://github.com/inventree/InvenTree/pull/9638
+* @cbenhagen made their first contribution in https://github.com/inventree/InvenTree/pull/9641
+* @GoryMoon made their first contribution in https://github.com/inventree/InvenTree/pull/9704
+* @willbicks made their first contribution in https://github.com/inventree/InvenTree/pull/9655
+* @gitbock made their first contribution in https://github.com/inventree/InvenTree/pull/9775
+* @RedEchidnaUK made their first contribution in https://github.com/inventree/InvenTree/pull/9400
+* @tristanle22 made their first contribution in https://github.com/inventree/InvenTree/pull/9532
+* @sufyan-mukadam made their first contribution in https://github.com/inventree/InvenTree/pull/9673
+* @the78mole made their first contribution in https://github.com/inventree/InvenTree/pull/10107
+* @daniil4udo made their first contribution in https://github.com/inventree/InvenTree/pull/10179
+
+### Translation
+
+Our [translation efforts](https://crowdin.com/project/inventree) continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.
+
+If you are interested in contributing to the translation efforts, please visit our [Crowdin project](https://crowdin.com/project/inventree) and join the community of translators.
+
+### Code Contributions
+
+Check out our GitHub page for a list of outstanding issues and feature requests. If you are a developer, you can help to contribute to the project by submitting a pull request.
+
+In particular, we are looking for assistance with frontend development, as we work to complete the new user interface and improve the overall UI/UX of the project.
+
+### Report Bugs
+
+If you encounter a bug in InvenTree, please report it on our [GitHub issues page](https://github.com/inventree/inventree/issues). Please ensure that you provide as much information as possible to help us diagnose and fix the issue.
+
+### Documentation / Technical Writing
+
+If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.
+
+### Financial Support
+
+Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!
+
+The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!
+
+- [Polar.sh](https://polar.sh/inventree)
+- [GitHub](https://github.com/sponsors/inventree)
+
+If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.
+
+If your company benefits from InvenTree, please consider a [one time sponsorship](https://buy.polar.sh/polar_cl_d7lPAgS9jnW8NDOSWATqdz2gs3wUD1x5M5o7C2rPoAL) or a [recurring sponsorship](https://buy.polar.sh/polar_cl_UlGc3bUjwB7Vx89dhAY2iF3kUIVFBJC5mJyow4NlJa6) to help support the project.
+
+## Future Plans
+
+Our focus over the last year has been on the new user interface, and we are excited to see it finally come to fruition in this release. However, there is still much work to be done, and we have a number of plans for future development.
+
+Check out our [GitHub issues page](https://github.com/inventree/inventree/issues/) for a list of outstanding issues and feature requests. We are always looking for help to improve the project, and we welcome contributions from the community.
+
+You can also help by [completing the user survey](https://forms.gle/a7mFzqZj57FeS7ds9) to provide feedback on your experience with InvenTree, and help us to prioritize future development efforts.

deploy.md

@@ -19,7 +19,7 @@ InvenTree can be installed on FreeBSD using AppJail. An [AppJail Makejail](https
 
 ### Manual Bare Metal Install
 
-A [bare metal installation guide](https://docs.inventree.org/en/stable/start/intro/) is provided for users who are looking for a low-level or custom installation. 
+A [bare metal installation guide](https://docs.inventree.org/en/stable/start/) is provided for users who are looking for a low-level or custom installation. 
 
 ### Cloud
 

extend/api.md

@@ -9,4 +9,4 @@ InvenTree ships with an extensive REST API that is used by several native applic
 - InvenTree App (Android/iOS)
 - python module
 
-The API is self-documenting. More information is provided in the [documentation](https://docs.inventree.org/en/stable/api/api/).
+The API is self-documenting. More information is provided in the [documentation](https://docs.inventree.org/en/stable/api/).

extend/app.md

@@ -37,7 +37,7 @@ We provide direct downloads for Android users - view our [download page via pola
 
 ### Documentation
 
-Mobile app documentation can be found on the [InvenTree documentation site](https://docs.inventree.org/en/stable/app/app/).
+Mobile app documentation can be found on the [InvenTree documentation site](https://docs.inventree.org/en/stable/app/).
 
 ### Code
 

extend/index.md

@@ -8,4 +8,4 @@ InvenTree is designed to be part of a larger system of tools to support both hob
 - [API](api)
 - [Integrate](integrate) into other tools
 - PK2InvenTree for [migrating from PartKeepr to InvenTree](https://github.com/rgilham/PK2InvenTree)
-- Python [package](https://docs.inventree.org/en/stable/api/python/python/) 
+- Python [package](https://docs.inventree.org/en/stable/api/python/) 

extend/plugin/index.md

@@ -5,7 +5,7 @@ We supply core-dev and community built plugins to get you started with extending
 
 We expose some internal Python APIs to speed up your development and keep the instance running while you discover the possibilities.
 
-You can read more about the plugin architecture, including information on developing new plugins, on our [documentation](https://docs.inventree.org/en/stable/extend/plugins/)
+You can read more about the plugin architecture, including information on developing new plugins, on our [documentation](https://docs.inventree.org/en/stable/plugins/)
 
 ### Highlights