What the roadmap is for
The Cookie Law Info roadmap is here to gather feedback and requests from plugin users and developers and to communicate which features will be built and which won’t.
How it is organised
The idea is to keep it simple:
- Submitted ideas – selected ideas that you can vote on
- Rejected ideas – this isn’t a complete list but it does explain why certain features won’t be built
- In Planning (usually released within a month)
- Future (usually released within 1-4 months)
How to submit an idea
Simple: just send me a message using the contact form below and explain the idea and how you think it should work.
What happens to those submissions?
You should receive a response within a few days. I might suggest building it slightly differently or incorporate other ideas into the feature. If it’s an idea that works for the product then I’ll update the roadmap.
How to vote on an idea
Send me a message using the contact form below giving a +1 to the idea, and any changes/enhancements you think should be made.
Updated: 13 August 2015
Ideas from users. Contact me to vote for them!
- The [cookie_audit] shortcode can link to different URL per translation
- ARIA Landmark Flags (submitted here)
These features are currently being worked on. Expected time frame: usually within a month.
- Cookie Law Info 2.0.0 “Beta” – this is the next “free” version and is currently my main priority
- Cookie Bar should “push” header content down (i.e. should not overlay content in the header)
- Any major bug fixes to Cookie Law Info 1.X.X
These features are on the backlog but are not being actively worked on right now. Expected time frame: usually in the next 1-4 months.
- Extra support for older browsers that don’t support JSON.parse
- Currently none
- Build for the masses, not the few
- Keep to the spirit of the EU ePrivacy Directive (AKA the Cookie Law)!
- Test thoroughly before releasing
- Release little and often
- Offer excellent support – especially just after a release
Just like WordPress, the guiding principle behind Cookie Law Info is to “build for the masses”. What that means is that the features should be useful to the majority, not just built for a few. This is a mass-market product and not a custom-built solution tailored to just one website.
Testing. Writing a plugin is challenging because it has to work on hundreds of thousands of very different websites- if you’re writing custom code it only has to run on one website, and that is generally a lot easier. That means a lot of testing takes place on different themes, plugins, browsers, new WP features, and so on.
Release cycles. it’s better to release little than often than fewer but bigger releases. Version numbers reflect the size and scope of the release e.g. version 1.5.3 means plugin architecture version 1, feature set 5 and bug fix set 3. Sometimes a “hot fix” is needed before a planned feature, which is why indicative timings are given rather than specific version numbers and release dates.
Support. There’s no point making a release if nobody is around to support it. Circumstances change, unexpected events happen. Each release is fully supported so if something will get in the way of offering excellent support, it’s better to wait and release slightly later.