A base theme for a Drupal sites. Learn more about the theme in the wiki.
A style guide is available at /styleguide. The ts_styleguide package has the module available to create the
route. The template is editable and found in templates/_includes/_styleguide.html.twig
- Run
npm installto install dependencies.
Install will check the node version against the .nvmrc file, install all dependencies, and populate a prod build.
For most development tasks, simply run npm start to start Parcel's watch, which will compile the projects CSS and
JavaScript as well as Tailwind in JIT mode.
Additionally, there are a number of scripts to aid in theme development:
npm run buildto compile css, js, and print css for production.npm run format: Formats assets, tokens, and SVG files.npm run lint: to check styling errors in js/css files. Ran automatically if you commit while inside the theme directory.npm run print.bundleBundle the print stylesheet for production.npm run theme.bundle.prodCreate the production build.npm run theme.bundle.devCreate the development build.npm run startStart the watch of the project in development mode.
- Install Plugin phpstorm
- Install Plugin. Save and exit preferences.
- Reopen preferences. Go to Languages & Frameworks / Style Sheets / Dialects
- Add PostCSS as the dialect for the theme directory
This project is set up with Husky to lint code and commit messages using eslint and conventional commits and commitlint. See .husky directory to configure. The short version:
git commit -m "type: description"
- build: Changes that affect the build system or external dependencies.
- ci: Changes to our CI configuration files and scripts.
- docs: Documentation only changes.
- feat: A new feature.
- fix: A bug fix.
- perf: A code change that improves performance.
- refactor: A code change that neither fixes a bug nor adds a feature.
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.).
- test: Adding missing tests or correcting existing tests.