Next Theme version will be 02.00.01 as discusses with David

[Timo-Breumelhof]

@david-poindexter I still had 02.00.02 as the version, changed that to 02.00.01 as discussed previously

[david-poindexter]

Thanks @Timo-Breumelhof - just let me know when you are ready for a release.

[Timo-Breumelhof]

@david-poindexter The Theme is on staging for testing ATM. I'll let you know when that's done

[Timo-Breumelhof]

@david-poindexter tested on staging and now installed on live, we can release 02.00.01

[david-poindexter]

@Timo-Breumelhof the release is HERE. You can edit the release, upload the theme install package, and save.

In the future, I recommend a few small tweaks to the workflow.

1. Use the install package from latest develop branch or pull request build (ideally this should be automated using GitHub Actions) to test locally and/or on "staging".
2. If good, release on GitHub and upload the install package to the new release.
3. Use the install package from the new release to deploy to "production".

Following this, or a similar workflow, will ensure no manual file manipulation occurs on "staging" or "production". If manual file manipulation occurs but isn't accounted for in the GitHub source code and/or build process to generate the theme, then essentially problems with ongoing maintenance will occur (especially if it is someone else needed to do said maintenance).

Thanks for all the great work!

[Timo-Breumelhof]

Package uploaded

[david-poindexter]

Great - thanks @Timo-Breumelhof