This repository is a Drupal project that can be setup locally using docker.

Based on wodby/docker4drupal, with some tweaks to speed-up your development. The stack is configured as follows:

There is a docker-compose.override.yml.dist file including some container definitions like adminer and mkdocs. This is done with the purpose of differencing the local environment stack from the CI environment stack. The docker-compose.override.yml is git-ignored so your stack gets clean.

The folder structure skafold is based on drupal-composer/drupal-project so all your dependencies are managed by composer, drupal is required as drupal/core package and web-root files are automatically generated via drupal-scaffold composer plugin.

Drush is a command line shell for Drupal, and a swiss army knife letting developers to do mostly everything they can do by user interface, and much more. Drush is delivered with an excellent code generator to speed-up the development process.

Get more information about drush:

• Drush marketing site
• Drush official documentation
• Drush commands

The simplest way to manage your project documentation, written in markdown format, and displayed in a comfortable and styled html autogenerated site. The text-plain markdown format have the following advantages over other systems:

• It's quick to maintain.
• It's supported by version control systems.
• It's reviewable via merge requests.
• It's standard.
• It's free.

Mkdocs official site.

Because quality matters, the metadrop/drupal-boilerplate is delivered with Grumphp, a tool to ensure developers follow the Drupal coding standards and best practices. To make your projects fit the highest quality assurance, a git-hook is automatically installed so is not possible to commit any change without accomplishing those quality requirements. Grumphp is already configured (so you don't need to worry about that) making the following quality checks:

• Git commit message:

  • Ensures that the commit message subject line doesn't have a trailing period.
  • Ensures that the commit message subject match with Issue #[0-9]: Subject format.
  • Max subject width 130.

• phplint: Detects PHP files syntax errors.

• yamllint: Detects YAML files syntax errors.

• composer: Perform composer.json and composer.lock validation.

• jsonlint: Detects json files syntax errors.

• drupalcheck: Check Drupal code for deprecations and discover bugs via static analysis.

• phpcpd: Copy/Paste detector to avoid duplicated code.

• phpcs: Check if your code accomplish the following standards:

  • Drupal: The Drupal coding standards.
  • DrupalPractice: Drupal best practices.

If you want use the static analysis tools manually, or you need to add it to your continuous integration system, there is a phpqa configuration for it.

To run it, just run:

docker-compose exec php phpqa

Behavior Driven Development is supported on a natural language thanks to Behat. The boilerplate is delivered with Behat preconfigured, so you just need to start writing your tests. Some example tests are also provided. Aditionally to behat, some libraries are included improving the drupal support, adding several behat testing steps for the most common use cases such as logging as a user with a particular role, creating testing content, finding expressions within content regions, etc.

Here are the bundled libraries:

• drupal-extension
• nuvoleweb/drupal-behat
• metadrop/behat-contexts

If you want to execute every behat tests just run:

docker-compose exec php behat

Test Driven Development focus on testing your code to ensure it does what is expected across refactors. This kind of tests are known as Unit tests, and in PHP can be implemented with phpunit.

PHPUnit is a framework to perform unit tests on your php projects. The boilerplate is bundled with phpunit preconfigured so you can focus on write your unit tests.

Scripthor is our set of scripts for our daily routine, to speed up the development workflow.

Til today, we provide the following scripts:

• reload-local.sh: Reload your local environment setting everything up for a new developer, a new branch, or just to ensure your changes won't break production during the deployment.
• frontend-build.sh: Compile your sass and js-es6 files inside docker so you don't need to have node or gulp installed on your machine. Forget about version issues.
• copy-content-config-entity-to-module.sh: For a given content entity (content type, paragraph, custom block type...) it will take the entity definition, all its fields, form configuration and view modes and will copy them to the module of your choice.

BackstopJS automates visual regression testing of your responsive web UI by comparing DOM screenshots over time.

• Documentation

• Generate references:

  make backstopjs-reference
  

• Run regressions tests:

  make backstopjs-test
  

We are updating or selection of required modules to ensure you won't forget anything. The modules bundled will solve the needs of different areas such as SEO, security, content editing, themming or deployments across different environments.

Stylelint A mighty, modern linter that helps you avoid errors and enforce conventions in your styles.

• Install stylelint as dependency on your custom theme folder

  npm i stylelint --save-dev
  

• Install stylelint scss plugin

  npm i stylelint-scss --save-dev
  

• Create .stylelintrc.yml file with your stylelint rules

  # @TODO: Needs to be defined a standard base
  # Base on stylelint-config-recommended
  plugins:
    - stylelint-scss
  rules:
    # Rules references https://stylelint.io/user-guide/rules/list
    color-no-invalid-hex: true
    font-family-no-duplicate-names : true
    font-family-no-missing-generic-family-keyword: true
    function-calc-no-invalid: true
    # function-calc-no-unspaced-operator: true,
    function-linear-gradient-no-nonstandard-direction: true
    string-no-newline: true
    unit-no-unknown: true
    property-no-unknown: true
    keyframe-declaration-no-important: true
    # declaration-block-no-duplicate-properties: [
    #   true,
    #   {
    #     ignore: [consecutive-duplicates-with-different-values]
    #   }
    # ],
    # declaration-block-no-shorthand-property-overrides: true,
    block-no-empty: true
    selector-pseudo-class-no-unknown: true
    selector-pseudo-element-no-unknown: true
    selector-type-no-unknown: true
    media-feature-name-no-unknown: true
    comment-no-empty: true
    # Uncommenting this is hell
    # no-descending-specificity: true,
    no-duplicate-at-import-rules: true
    no-duplicate-selectors: true
    no-empty-source: true
    no-extra-semicolons: true
    no-invalid-double-slash-comments: true
    
    # SCSS-specific
    scss/at-rule-no-unknown: true
    scss/at-each-key-value-single-line: true
    scss/at-extend-no-missing-placeholder: true
    scss/at-function-parentheses-space-before: 'never'
    # scss/comment-no-empty: true
    # scss/dimension-no-non-numeric-values: true
    # scss/no-duplicate-mixins: true
  

• Run stylelint checker

  npx stylelint 'src/**/*.scss'
  

• You can run stylelint from npm
  Add to the package.json the following script:

  "scripts": {
...
    "css:lint": "npx stylelint 'src/**/*.scss'"
...

Then execute the following command

npm run css:lint

• If you use webpack you can add stylelint to your webpack.mix.js
  Install webpack stylelint plugin:

npm i stylelint-webpack-plugin --save-dev

Then add the following lines to the webpack file.

const stylelint = require('laravel-mix-stylelint');

...

mix
  .stylelint({
    configFile: path.join(__dirname, '.stylelintrc.yml'),
    context: './src',
    failOnError: false,
    files: ['**/*.scss'],
    fix: true,
  })

To create a new project based on this boilerplate, the recommended method is using composer create-project:

composer create-project  --ignore-platform-reqs metadrop/drupal-boilerplate my-project

Then, complete the setup following these steps:

1. Copy the .env.example file to .env and edit it to fit your needs.
2. Copy the docker-compose.override.yml.dist file to docker-compose.override.yml. Look for the services.traefik.ports value. There you have the port mapping in the form <your local machine port>:<container port>. Note that WEB_SERVER_PORT is the local machine port which is mapped to point the web server port inside the container.
3. Start containers running docker-compose up -d in repository root.
4. To access the site go to URL: http://<PROJECT_BASE_URL>:<WEBSERVER_PORT>/
5. To access the project's documentation go to URL: http://docs.\<PROJECT_BASE_URL>:<WEBSERVER_PORT>/