A starter theme for Drupal, but not depending on it, could be used as standalone

First make sure docker compose is installed correctly

• download the docker4drupal container from docker4drupal
• customize the docker settings in the .env file (url, database connection, services to use,.. are set here)
• windows : to allow file uploads from drupal, make sure to execute php as root, change the docker-compose.yml according to docker4drupal root
• remove file docker-compose.override.yml, this will fire up a vanilla Drupal but we want to install Drupal with composer
• start docker for first time or when changes to config are made (within project folder)

  $ docker-compose up

• to start an existing docker you can use

  $ docker-compose start

• if you get an error like ...not a valid windows path, run this command first in powershell

  $ $Env:COMPOSE_CONVERT_WINDOWS_PATHS=1

• you can then access your url (e.g. http://drupal2.docker.localhost:8000)
• to execute php inside the container (e.g. drupal cr, composer) (doesn't work from within WSL, does work from within powershell)

  $ docker-compose exec php drupal cr

Use drupal project as starter setup:

• create a new project with composer in a temporary web2 folder, files will need to go into the root of your project folder, but if you install into ./ you will get a "folder not empty" error:

  $ docker-compose exec php composer create-project drupal-composer/drupal-project:8.x-dev    web2 --stability dev --no-interaction

• copy files from web2 to the root of your project

  $ cp -a web2/. ./
  $ rm web2 -Rf

• install drupal modules

  $ docker-compose exec php composer require drupal/browsersync

  • install drupal from your url (database settings are in the .env file)

turn off caching and turn on theming help for local development:

• uncomment loading local settings file in web/default/settings.php

  # if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
  #   include $app_root . '/' . $site_path . '/settings.local.php';
  # }

• add local settings.local.php and development.services.yml files
  • https://gist.github.com/Greg-Boggs/ff70345b7f3590228fc09be1f38d0688
  • https://gist.githubusercontent.com/jszwedko/ac203de56bd9ee5c5fa5d841b971915e/raw/bbbd9c60c91c6dc0076283fff77127af0255c03b/development.services.yml

• download the starter theme to web/themes/custom folder
• rename folder to the
• rename starter.libraries.yml to .libraries.yml
• rename starter.info.yml to .info.yml
• replace all accurancies of starter with
• install npm dependencies

  $ npm install
  or
  $ yarn install

• gulp start uses browsersync to automatically update the browser on sass,js changes this requires the drupal/browsersync module (enabled for the theme) You also need to change the server url in gulp-config.json
• gulp build compiles and minifies the source files
• gulp test runs (parker) statistics on css

There is a guide build from comments in the source files in KSS syntax. It is available at: http:///themes/custom//docs/index.html You can regenerate the documentation (e.g. when sass variables are changed) with a gulp command

$ cd web/themes/custom/<theme name>
$ gulp docs

the theme follows the itcss file structure.

Most work will be done in the component folder, the classes here don't NEED to be prefixed (objects and utils should though), When not prefixed we'll assume it's a component.

Try to keep each component in its own file (filename should align with component name).

Whenever possible use the BEM naming convention for classnames. object (o-) and utilities (u-) should be prefixed.

Colors, breakpoints, Grid settings, fonts and (responsive) font-sizes are set in settings folder.

Extra Vendor assets are preferably installed with npm (yarn) and then added with @import. You can add the vendor folder name to gulp-config.json css > paths . This way you can simply use @import with the filename without the complete folder name.

main file is app.js, here all "modules" are created, fonts are loaded, navigation is initialized, Barba is initialized. All modules are instanciated here and they react on the initModules event to execute when needed.

Extra Vendor assets are preferably installed with npm (yarn) and then added with import or require. You can add the vendor folder name to gulp-config.json js > paths.

gulp

• add a lint for testing code standards (scss, js, html?)
• visual diffing would be nice : https://meowni.ca/posts/2017-puppeteer-tests/

sass

• can we lose some of the default css files loaded or is this not worth it (very minimal filesize)
• look into critical path css (can this be automated, manual?) + how to load in drupal

js

• popup/overlay (e.g. https://sachinchoolur.github.io/lightgallery.js/)
• embedding (iframe scale, fitvid.js)
• alternative form mmenu? with smaller file size?
• instead of importing from gsap (which points to the tweenMax file) try importing from gsap/TweenLite, gsap/EasePack. or load it trough CDN and remove it from the build package with browserify-shim in package.json