I’ve just merged quite a large branch into master on the Storefront repo at GitHub which symbolises the beginning of the development of version 2.0.0.

Storefront 2.0 aims

The aims for Storefront 2.0 are fairly simple and outlined below;

Refactor all the things

First of all we’ll be refactoring a lot of the organisational structure. We currently include a bundle of php files that are required for the theme to run. But they lack context and some have similar names which leads to confusion. In addition to this some even share names with core template files which has lead folks to believe they can overwrite these files via child themes, which is not possible (nor should it be).

To remedy this we’ll be moving a lot of the logic to php classes where appropriate. We’ll also rename and re-organise other files/folders to make it much clearer what everything is doing. We’ll likely model this on WooCommerce core for consistency and familiarity.

As a part of this refactor we’ll also re-organise all of the Storefront assets (css, js, fonts, etc) into a single directory which will make them all much easier to work with.

Some of the logic in our template files is a little outdated and could use some love, and some functions will be deprecated.

All of this should have a positive impact on overall performance and make Storefront even more intuitive for developers to work with.

This is will make up the ‘meat’ of the release and will be a large rewrite of a lot of the core code which is why this release will be version 2.

Design refresh

Storefront is officially 14 months old but the design is even older and starting to look a little dated. Obviously we need to be very conscious of child themes, and customisations our users might have made, but I’d like to make some tweaks to the design. Most will be quality-of-life fixes but we will also look at things like the Typography and the default color scheme to bring Storefront core up to date.

A more dynamic welcome screen

Our welcome screen saw improvements recently and now pulls in relevant blog posts / documentation. To make it more useful for users and to increase engagement we’d like to dynamically pull in the latest extension / child theme releases as well.

Get involved

If you’d like to get involved with the development of 2.0 please head over to GitHub. With Storefront we’re following the same approach as WooCommerce IE the master branch is the latest development branch, so please send all pull requests there.

Close to release we’ll be looking for beta testers, so please express your interest in that here if you’re keen to be involved.