All the power of Pug, Sass, Coffeescript and WebPack in your WordPress theme. Stop writing themes like it's 1998.
new_post_type
helper to correctly support latest WP versions. Fix #243Pug
class to render both in dev and prodFull diff from previous version @ https://github.com/welaika/wordless/compare/2.7.0...3.0.0
If you are interested in updating a project you have to study the new scaffold and update it by hand. This will be a hard work and we cannot provide an automagic upgrade for such a big change.
The main shipped feature is a new filter wordpress_pug_configuration
that let developer overwrite pug configurations inside the theme. Documentation added at https://wordless.readthedocs.io/en/latest/_pages/usage/filters.html.
Thanks to @juankk for his contibution.
Commits highlights
pretty
from pug config since deprecationwordpress_pug_configuration
filterWordless 2.5 deprecates the old ruby preprocessors support. It is disabled by
default. If you need to develop an old theme you need to explicitly activate
them by setting the following in your wp-config.php
define('WORDLESS_LEGACY', true);
Wordless 3 is planned to completely remove this support.
Seems that vendor/symfony/var-dumper/Caster/ArgsStub.php
has a bug and seems wordpress.org is doing some sort of static code analysis and thus breaking our deployment. Hope the hotfix will unlock this release.
This is a performance related update.
From now on if Wordless will find ENVIRONMENT
set up as a constant (in wp-config.php
) or as an environment variable and its value is staging
or production
, then the rendering optimizer will be automatically used.
Updated the following vendors through composer:
if lt IE 9
comment from vanilla theme's head ( fix #219 )Thanks @Youdaman for issue reporting
Previous locked dependencies no more worked with latests versions of node due to compilation errors
Themes were created w/o tmp directory - throwing the right warning, but tedious anyway :)
From version 2.2.0 to version 2.2.13 I've only had problem - and now fixed - with deployment to the wordpress plugin svn directory.
I'm sorry for the dirty repo history, but now I managed to get it back to work, in a more robust way and integrated Travis' Continuous Delivery.