Project template for a Drupal static site generated by Quick. It pre-wires Drupal core, Quick (+ the starterkit theme), Drush, and
the recipe unpacker — including the Composer repositories, allow-plugins, and
stability settings — so going from empty folder to static site is just a handful
of commands.
# create + start the DDEV environment
ddev config --project-type=drupal --docroot=web --nodejs-version=20 && ddev start
# Drupal + Quick, fully pre-wired by this template
ddev composer create-project drupal-quick/site .
# (create-project just delivered config.dq.yml — the annotated template from
# the installed Quick package. Edit it to change the preset, layout, recipes
# + their options, or homepage blocks; or regenerate it interactively)
ddev composer exec -- dq-init --interactive # optional
# fetch the recipe packages named in config.dq.yml; also writes each recipe's
# available options into it as commented blocks (uncomment to override —
# pass --exclude-options to just list them instead)
ddev composer exec -- dq-install
# install Drupal, generate + build the theme, apply recipes
ddev drush dq:scaffold
# --- add content / configure as desired ---
# generate the static export → html/, then publish it
ddev drush dq:static
ddev drush dq:deploydrupal/core-recommended+ the relocatedweb/docroot scaffold.drupal-quick/drupal-quickanddrupal-quick/dq_starterkitvia their VCS repositories (not yet on Packagist), withminimum-stability: dev.drupal/core-recipe-unpackand itsallow-pluginsentry, so recipes unpack without prompting.- A
post-create-project-cmdhook that runsdq-init, delivering the annotatedconfig.dq.ymlfrom the installed Quick package — a single source of truth that always matches the Quick version consuming it. Editing it is optional (defaults: presetminimal, thestandard+blogrecipes). If you create the project with--no-scripts, runcomposer exec dq-inityourself.
Once Quick and its packages are published to Packagist with stable tags,
the repositories and minimum-stability settings here become unnecessary.