Jump to content
thirty bees forum

Theme building toolkit(s)


Recommended Posts

One of the best things about PS 1.7 is IMHO its new "Classic" theme. Not only because it's cleaner on the user-visible surface, but also because it's cleaner code.

  • It uses libsass instead of compass, which is said to be faster.
  • It uses the NPM packaging system for libraries instead of copying them into subfolders.
  • It uses webpack for automatic building and also building all sources into a single pair of .css and .js files. Downloading one bigger file is obviously faster than requesting each file separately.
  • Webpack also allows optimization, like dead/duplicate code removal (gives me some 30% smaller files on PS 1.7).

The unfortunate thing about this Classic theme is, it's incompatible with thirty bees. I looked a bit into getting it running, but creating kind of an adapter appears to be several months of work.

... which doesn't mean that thirty bees can't use similar strategies for just building the theme, without breaking backwards compatibility. Sass is still Sass, JavaScript is still JavaScript, Smarty is still Smarty.

The question: is it a good idea to use libsass, NPM and webpack for building the thirty bees theme, too? Is NPM better than composer, which is already in use for modules? Are there even better tools?

I'm about to get into theme building, so I could improve the thirty bees infrastructure a bit along the way.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...