Hi,

Thank you for using or being interested in BTF!
I’ve put a lot of love into it over the years and I greatly appreciate all the reviews that keeps me motivated.

It’s been a while since I last provided any information on the status of the plugin so I wanted to be transparent about the current roadmap. Here it is. The order is roughly in order of priority, however it may be subject to change.
There is no time frame set for this roadmap, it’s only for transparency and allowing feedback from the plugins users.
Please remember that this is a free open source plugin without a Pro version, there are no financial gain to this plugin.

Here’s the functional changes/improvements I plan to implement:

1. A new Block
   • It’s time the plugin has a block for adding the filter widget inside the block editor for modern themes.
   • I won’t replace the shortcode feature with this, it will remain for the time being.
2. Updated styling
   • I think it’s time to add maybe one or two new styles, with a new default, that is a bit more modern.
   • I won’t replace or remove the existing style choices. If you use one of them, you can keep using them.
   • Will also look at the base styling and see if anything can be improved there. For example the layout should really use flexbox or CSS grid nowadays.
3. Multiple choices in a single taxonomy
   • This is a big one and also the most uncertain feature. I wrestled with this A LOT in the past without success. Hopefully we can make this happen now without compromising what makes BTF useful and unique.

Here’s the code related changes I plan to implement:

1. Refactoring of the codebase
   • The codebase, while not particularly bad, is also not reflecting of the change in skill and level of code quality that I try to uphold these days. It’s in need of a rewrite without removing any of the existing features you use.
   • It will adhere to the WPCS Extra PHPCS Ruleset
   • It will adhere to the WordPress stylelint and eslint rulesets
   • It will build the assets using modern build jobs to make sure you are serving minimized and optimised JS/CSS.
2. It will move away from jQuery (if possible) and only use vanilla JS for the javascript logic.
   • This may require swapping out select2 for a non jQuery alternative like Choices. Ideally I’ll try to make that a settings choice so that those that want to keep using select2 can do so.
3. It will have automatic documentation of all available actions and filters.
4. It will have automated testing
   • PHPStan for static code analysis
   • PHPCS, Eslint, Stylelint
   • Possibly Unit testing but we’ll see.
5. It will be properly hosted on Github with a composer file for those that want to pull it from there instead of wpackagist for any reason.
6. Extensibility – I will look at adding more hooks where it may be useful to further enable power users to modify the behaviour.

Have feedback on the roadmap? Things not on this list that you would like to see? Go ahead and respond to this thread 🙂