Yeoman generator for Drupal Themes - lets you quickly set up a Drupal 8 theme with sensible defaults and best practices.
While the theme generator can be run anywhere, it's happiest when it's run from an empty directory you'd like to become your theme.
- Create a new directory. Example:
themes/custom/my_awesome_theme
While not a requirement we like to use NVM to manage the version of Node per project. Here's a quick one liner that will install the latest stable version of Node using NVM and create a .nvmrc
file.
- Move into the new directory you created above, then run the following command:
nvm install node && node -v > .nvmrc
From now on, when working on this theme change into its directory and run nvm use
and NVM will switch to the specified version for you.
To run the theme generator type the command:
npm create yo mc-d8-theme
You should be taken through a series of questions that allow you to pick the best options for your theme.
More info if you're interested in how this stuff works:
npm create
is an alias of npm init
and uses npx under the hood. Find out more about npm init.
The following is supported by your new theme.
- Pattern Lab (Node)
- Component-Based Workflow
- ES6+ (With Source Maps)
- Sass
- Image Compression
- Live reloading
- Sass and JavaScript linting
The theme generator allows you to optionally add several example components.
- Button (with variations)
- Drupal Messages (Based off of the Classy base theme)
- Drupal Tabs
These can include both component and Drupal templates that are added to the appropriate place during theme generation. Your theme.libraries.yml is also updated to include the relevant libraries.
We're using the beta version of Pattern Lab (Node). As you can imagine there are a few issues that come up that haven't been resolved yet. For this project we use Patch Package to patch the following issues.
- Menu & View All list breaks if pattern name and folder name are identical
- Pseudo patterns not working with twig php engine
There's nothing special you have to do. patch package
will run after the npm install
.
TLDR: Don't do it if you can avoid it.
Every time Pattern Lab is rebuilt the cache busting strings will change on CSS and JS files. dependencyGraph.json
will also be updated every single time which makes reviewing pull requests rather difficult.
Optimally we want to gitignore all /.dist
files and run npm run build
as part of a continuous integration process.
Change what browsers your theme supports by updating browserslist within package.json
. For options take a look at browserslist.
This impacts CSS browser prefixes and JavaScript compiled files.
- Swap out
screenshot.png
with your own theme image. - Remove or replace the font files in
./src/patterns/global/fonts/
. - Change the colors in
./src/patterns/global/colors/
.
Provided by default are seven npm scripts that point to Gulp tasks. We run gulp through npm scripts so the build tools can change without the user ever knowing.
- Run the default build task (gulp in this instance) and everything in it.
This is the equivalent to running
gulp
on the command line with Gulp installed globally.
npm run build
- Compile Sass and JS.
npm run compile
- Watch files and run tasks when they change.
npm run watch
- Compress png and svg assets.
npm run compress
- Build Pattern Lab.
npm run styleguide
- Lint Sass and JS files.
npm run lint
- Delete compiled Sass, JS and style guide files from the /dist directory.
npm run clean
Would you like to contribute? Want to make a few changes or fix a bug? COME ON OVER!
Clone down this repo:
git clone [email protected]:mediacurrent/theme_generator_8.git
Remove generator-mc-d8-theme
if you have previously installed it:
Tip: use npm ls -g -depth=0
to see what global node modules are installed.
npm uninstall generator-mc-d8-theme -g
From the generator root directory link your local generator files to npm:
npm link
Now whenever you run yo mc-d8-theme
it'll use your locally cloned mc-d8-theme generator. Any updates done to the generator can be tested in real time.
Break off a feature branch dive right in. After you've got something you'd like to add, push back to the repo and pull request against develop.