This functionality requires Wagon v3
One of the nice things about Sprockets is its super easy installation. Nothing to setup, it just works out of the box. Assets were gzipped without any weird configuration.
However, in top of that, frontend developers must use a tool to compile all the package assets required by their sites. To achieve this, developers came up with tools.
One of the most popular is Webpack. This is an incredible tool which, unfortunately, can be a burden to set up correctly.
Since the philosophy behind LocomotiveCMS is to remove the painful tasks involved in creating websites, we decided to integrate Webpack inside Wagon so that spinning up a new project takes as little time as possible.
Webpack requires the installation of NodeJS and YARN (or NPM)
There is almost nothing to do. Creating a new site will automatically generate all the files we need to start using Webpack. Those files will go under the
app/assets folder of your Wagon site.
package.json file is located at the root of the Wagon site.
Avoid build error
In this file you will need to edit the node_sass dependency version according to your node version following this chart in order to avoid a build error.
Want to add Webpack to a site built with Wagon v3?
At the root of your site, type the following command:
bundle exec wagon generate webpackthen modify the "name" value in the generated package.json file to match your site's root folder name.
You just have to download and install the packages which can be done in one statement in the console.
All you have to do is to run the following statement.
Note: You will probably need 2 terminals. One for
wagon serve and the other one for Webpack.
Once launched, the command outputs logs about the compilation of 2 files:
By default, we included the live reload functionality thanks to the webpack-livereload-plugin package. So, if you try to modify one of your JS/CSS assets in
app/assets, the browser will automatically reload the
bundle.css or the
If you want your browser to reload on any file change follow the instructions in this discussion.
Assets generated through the
yarn start command are not optimized for production. For instance, they're not minified.
So, before you deploy your theme assets to your production environment, you'll have to generate optimized assets. This can be achieved with the following command:
In your terminal, run this statement:
yarn add bulma
Note: Don't forget to stop and re-start,
Next, let's modify the
app/assets/stylesheets/app.scss file by adding the following code:
// Bulma @import '~bulma/bulma.sass'; @import './bulma_variables';
Then, create a file overriding the Bulma default configuration. This file is named
bulma_variables.scss and it has to be located in the
Here is a sample:
$family-sans-serif: 'Roboto Condensed', sans-serif; // Colors $lighter-blue: #bdd1e4; $light-blue: #8aacd4; $dark-blue: #224261; $dark-grey: #636466; $light-grey: #a7a9ac; $brown-orange: #E3A346; $primary: $dark-blue; $warning: $brown-orange; // Navbar $navbar-height: 7.25rem !default;
Updated 11 months ago