aten / drupal-project
Aten Drupal Project
Installs: 15
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 2
Forks: 0
Open Issues: 2
Type:project
Requires
- aten/aten_standard: 10.x-dev
- composer/installers: ^2.2
- cweagans/composer-patches: ^1.7
- drupal/admin_toolbar: ^3.4
- drupal/config_ignore: ^3.3
- drupal/core-composer-scaffold: ^10.0
- drupal/core-project-message: ^10.0
- drupal/core-recommended: ^10.0
- drupal/editoria11y: ^2.1
- drupal/entity_usage: ^2.0@beta
- drupal/environment_indicator: ^4.0
- drupal/field_config_cardinality: ^3.0
- drupal/field_group: ^3.4
- drupal/flood_control: ^2.3
- drupal/gin: ^3.0@RC
- drupal/gin_toolbar: ^1.0@RC
- drupal/google_tag: ^2.0
- drupal/metatag: ^2.0
- drupal/multiple_selects: ^1.1
- drupal/pathauto: ^1.11
- drupal/rabbit_hole: ^1.0@alpha
- drupal/redirect: ^1.9
- drupal/replicate: ^1.2
- drupal/replicate_ui: ^1.1
- drupal/tab_toolbar: ^1.0
- drupal/toolbar_manager: ^2.0
- drupal/twig_field_value: ^2.0
- drupal/twig_tweak: ^3.4
- drupal/ultimate_cron: ^2.0@alpha
- drupal/view_unpublished: ^1.2
- drupal/views_argument_token: ^2.0
- drupal/webp: ^1.0@RC
- drush/drush: ^12.1
- oomphinc/composer-installers-extender: ^2.0
Requires (Dev)
- aten/robo-package-plugin: dev-main
- dealerdirect/phpcodesniffer-composer-installer: ^1.0
- drupal/coder: ^8.3
- drupal/core-dev: ^10.0
- drupal/devel: ^5.1
- drupal/devel_a11y: *
- drupal/devel_entity_updates: ^4.1
- drupal/stage_file_proxy: ^2.1
- friendsofphp/php-cs-fixer: ^3.57
- phpmd/phpmd: ^2.13
- phpro/grumphp-shim: ^2.5
- roave/security-advisories: dev-latest
- robo-package/drupal: ^1.1
- squizlabs/php_codesniffer: ^3.7
- vincentlanglet/twig-cs-fixer: ^2.10
Conflicts
This package is auto-updated.
Last update: 2024-11-14 16:24:20 UTC
README
Starter repo for a Drupal website.
Getting Started
To start a new Drupal project, run the following command:
composer create-project aten/drupal-project:latest
Development Workflow
Projects built using this starter project make a number of assumptions. First that the project codebase is hosted on Github. This allows leveraging of Github Actions for deployments to various remote hosting environments.
For all projects in active development, Pantheon hosting is assumed at least to start. This allows developers to leverage Pantheon's free sandbox and multidev environments. Additional hosting providers can be configured by updating Github Actions deployment scripts.
Branches prefixed with feature/
will get a new multidev environment created
when a new PR is opened against the main
branch. Sequential pushes to that
branch will update the multidev environment. Closing the PR will destroy the
multidev environment.
Patches
Composer based websites should use the composer-patches
plugin. This allows for patches to be applied every time composer install
is
ran. To keep things clean, all patches should live in an external
composer.patches.json
file and not within the main composer.json
file.
Best practice should be that patches are contributed back to their associated Drupal project and referenced by with the issue number. For example:
"drupal/core": {
"#12345: Short description...": "https://www.drupal.org/path/to/file.patch",
}
In rare cases where a local patch is needed, keep the .patch
or .diff
file
in the repo's /patches
folder.
Scaffold Development Instructions
To add or update packages to this base install, pass the --no-update
flag into
the composer require
or composer update
commands. This will ensure no
package.json
file is created and dependencies are not installed.
There a series of scripts for testing updates to the installer:
composer test:ak-installer
: Runs a test install. Places files on the Desktop.composer cleanup:ak-installer
: Removes the installed directory. Gets ran before new installs.