PHPackages                             az-digital/az-quickstart-scaffolding - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. az-digital/az-quickstart-scaffolding

ActiveProject

az-digital/az-quickstart-scaffolding
====================================

Arizona Quickstart Scaffolding for Composer

3.3.x-dev(2mo ago)3954↓100%2[8 issues](https://github.com/az-digital/az-quickstart-scaffolding/issues)[6 PRs](https://github.com/az-digital/az-quickstart-scaffolding/pulls)GPL-2.0-onlyPHPPHP &gt;=8.3CI passing

Since Oct 18Pushed 1mo ago15 watchersCompare

[ Source](https://github.com/az-digital/az-quickstart-scaffolding)[ Packagist](https://packagist.org/packages/az-digital/az-quickstart-scaffolding)[ RSS](/packages/az-digital-az-quickstart-scaffolding/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependencies (10)Versions (61)Used By (0)

Arizona Quickstart Scaffolding
==============================

[](#arizona-quickstart-scaffolding)

Notes
-----

[](#notes)

If you are planning on pushing this site to Pantheon, you should use the [Pantheon upstream repository](https://github.com/az-digital/az-quickstart-pantheon) as your scaffolding repo, which has separate instructions.

[![Security workflow](https://github.com/az-digital/az-quickstart-scaffolding/workflows/Security%20workflow/badge.svg)](https://github.com/az-digital/az-quickstart-scaffolding/workflows/Security%20workflow/badge.svg)

- Designed to build a Quickstart website/project codebase
- Includes [Quickstart](https://github.com/az-digital/az_quickstart) as dependency
- Installs Drupal in a `web` subdirectory
- Utilizes [composer-installers](https://github.com/composer/installers) and [Drupal Composer Scaffold](https://github.com/drupal/core-composer-scaffold) plugins
- Can be used as a project template for the composer [create-project command](https://getcomposer.org/doc/03-cli.md#create-project)

Choosing the Right Branch for Your Quickstart Project
-----------------------------------------------------

[](#choosing-the-right-branch-for-your-quickstart-project)

In the Arizona Quickstart Scaffolding project, different branches serve various purposes. Here's a guide to understanding which branch you should choose:

### Main Branch (`dev-main`)

[](#main-branch-dev-main)

- **Purpose**: The main branch contains all the latest features and changes. It represents the cutting-edge development and may be less stable than specific release branches. You can use it with `dev-main` or an alias for the latest unreleased version (e.g., `2.8.x`).
- **When to Use**: Choose this branch if you want access to the very latest features, and you are willing to work with potentially less-tested code. Ideal for development, experimentation, or testing unreleased functionality.

### Release Branches (e.g., `2.5.x`, `2.6.x`, `2.7.x`)

[](#release-branches-eg-25x-26x-27x)

- **Purpose**: Release branches, named in the format of `2.x.x-dev`, are created for specific versions of the project and are considered stable and production-ready. They contain well-tested features suitable for live environments.
- **When to Use**: Select one of the latest two supported release branches (e.g., `2.7.x-dev`, `2.6.x-dev`) if you need a stable version of the project for production use, have specific environment constraints, or want to maintain compatibility with particular third-party modules or a specific release.
- **Note**: Only the latest two release branches are actively supported. Using one of these ensures that you receive updates, security patches, and support aligned with your system's requirements, avoiding potential conflicts and achieving a robust and reliable implementation.
- **Version Constraints in Supported Release Branches**: Each supported release branch in this repository specifies a version constraint for az\_quickstart in composer.json. This constraint ensures that the release branch will work with compatible versions of Quickstart that correspond to the compatible minor release branch, providing flexibility while maintaining alignment with the intended versions.

### Feature or Issue Branches

[](#feature-or-issue-branches)

Feature or issue branches in this repository are typically created to make updates to the scaffolding to work with specific branches of `az-digital/az_quickstart`. When creating such a branch, it is customary to pin this repository's composer.json reference for `az-digital/az_quickstart` to a specific issue/feature branch that the changes are intended to work with. This ensures that the branch's changes align precisely with a particular state of the Quickstart project.

These branches are useful for isolated development, testing of changes, or adding new features to the scaffolding that correspond to developments in the Quickstart project.

**Notes**

- If developing a feature for `az-digital/az_quickstart`, use the provided build tools (DDev or Lando) instead of running `composer create-project` directly.
- These branches are not as stable as the main or release branches, so use them for development, experimentation, or testing rather than in production environments.
- The use of feature or issue branches in this repository is tightly aligned with developments in the az-digital/az\_quickstart project, and they should be used in conjunction with the corresponding Quickstart branches.

### Using the `composer create-project` command:

[](#using-the-composer-create-project-command)

With Composer's `create-project` command, you can quickly scaffold a new project using the Arizona Quickstart Scaffolding. Each `az-quickstart-scaffolding`branch coincides with an `az_quickstart` branch, ensuring compatibility and alignment between the scaffolding and the core project.

Here are some examples of how you might use this command with different branch specifications:

If using any of the following commands, adjust `my_project_name` to your desired project directory name.

- **Using the Main Branch (`main`) with dev dependencies**:

    ```
    composer create-project az-digital/az-quickstart-scaffolding:dev-main my_project_name --no-interaction
    ```
- **Using the Latest Unreleased Version Alias (`2.8.x`):**

    ```
    composer create-project az-digital/az-quickstart-scaffolding:2.8.x-dev my_project_name --no-interaction --no-dev
    ```
- **Using a Specific Release Branch (e.g., `2.7.x`):**

    ```
    composer create-project az-digital/az-quickstart-scaffolding:2.7.x-dev my_project_name --no-interaction --no-dev
    ```
- **Using an Issue or Feature Branch (e.g., `issue-45`)**

    ```
    composer create-project az-digital/az-quickstart-scaffolding:dev-issue/45 my_project_name --no-interaction
    ```

Migration setup in Lando
------------------------

[](#migration-setup-in-lando)

Arizona Digital has added a [README for migrating into Quickstart 2](https://github.com/az-digital/az_quickstart/blob/main/modules/custom/az_migration/README.md).

Updating Quickstart
-------------------

[](#updating-quickstart)

Currently, Arizona Digital supports the two most recent [minor releases of Arizona Quickstart](https://github.com/az-digital/az_quickstart/blob/main/RELEASES.md).

- `composer install` will install updates and pull in dev dependencies, and also apply patches if they exist.
- `composer install  --no-dev` will install updates, and will remove dev dependencies, and also apply patches if they exist.
- `composer update` is supposed to get the latest available based on the [version constraints](https://getcomposer.org/doc/articles/versions.md#summary) in your composer.json file, and also apply patches if they exist.
- `composer require "az-digital/az_quickstart:2.7.0" --update-no-dev` Will pin to a specific version of Quickstart without dev dependencies. You can update your site, incrementing the version number whenever you want to update, or use version constraints with `composer update --no-dev` to only update to a tagged version.

Once your site's codebase is up to date, it is important to run database updates and distribution updates.

**Important** Always create a backup before running database updates or importing distribution updates.

Updating the database can be done via the command line:

```
drush updatedb

```

**Important** Always ensure your site is set on the correct strategy for importing distribution updates. For Quickstart, it is recommended to use the merge strategy when importing distribution updates, which can be set via drush, or within the Admin UI.

It is advisable that you familiarize yourself with the functionality of the [Config Distro](https://www.drupal.org/project/config_distro) module to get the most out of Quickstart.

```
drush -y state:set config_sync.update_mode 1 --input-format=integer

```

Importing distribution updates can be done via the command line:

```
drush config-distro-update

```

Launching your site
===================

[](#launching-your-site)

When you are ready to launch your site, you can remove dev dependencies included with Quickstart and this scaffolding repository with composer, but first you will want to make sure the development modules are not enabled in Drupal.

Example

```
drush pm:uninstall -y devel migrate_devel config_inspector

```

Once uninstalled, dev dependencies can safely be removed with composer.

```
composer remove --dev

```

###  Health Score

49

—

FairBetter than 95% of packages

Maintenance68

Regular maintenance activity

Popularity23

Limited adoption so far

Community24

Small or concentrated contributor base

Maturity73

Established project with proven stability

 Bus Factor2

2 contributors hold 50%+ of commits

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~88 days

Recently: every ~46 days

Total

20

Last Release

68d ago

Major Versions

2.14.x-dev → 3.0.x-dev2025-08-28

2.x-dev → 3.1.x-dev2025-11-04

PHP version history (3 changes)2.0.x-devPHP &gt;=7.3

2.8.x-devPHP &gt;=8.1

3.0.x-devPHP &gt;=8.3

### Community

Maintainers

![](https://www.gravatar.com/avatar/bdb65b02f70bac56433fce0cfd18b9fa52bc0eef5adf733739f07a041a1b7d3d?d=identicon)[tadean](/maintainers/tadean)

![](https://www.gravatar.com/avatar/78ed17b981916d97c95e226b20f8f468b6533fa57cd3568abb317715039fc5ec?d=identicon)[joeparsons](/maintainers/joeparsons)

![](https://www.gravatar.com/avatar/0948a52b8b5181ae424b64cbe8b48f3331775ffa86888b3b21089edf5243a222?d=identicon)[az-digital](/maintainers/az-digital)

![](https://www.gravatar.com/avatar/aa6639f4b4794e70dd218311167b46671287911f534b07bf8f4577669b74d54e?d=identicon)[mmunro](/maintainers/mmunro)

---

Top Contributors

[![joeparsons](https://avatars.githubusercontent.com/u/471936?v=4)](https://github.com/joeparsons "joeparsons (57 commits)")[![trackleft](https://avatars.githubusercontent.com/u/1023167?v=4)](https://github.com/trackleft "trackleft (15 commits)")[![tadean](https://avatars.githubusercontent.com/u/51835841?v=4)](https://github.com/tadean "tadean (12 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (12 commits)")[![az-digital-bot](https://avatars.githubusercontent.com/u/102191613?v=4)](https://github.com/az-digital-bot "az-digital-bot (10 commits)")[![joshuasosa](https://avatars.githubusercontent.com/u/4400438?v=4)](https://github.com/joshuasosa "joshuasosa (5 commits)")[![uaz-web-readonly-bot](https://avatars.githubusercontent.com/u/101821238?v=4)](https://github.com/uaz-web-readonly-bot "uaz-web-readonly-bot (4 commits)")[![danahertzberg](https://avatars.githubusercontent.com/u/59745109?v=4)](https://github.com/danahertzberg "danahertzberg (1 commits)")[![kevcooper](https://avatars.githubusercontent.com/u/6468064?v=4)](https://github.com/kevcooper "kevcooper (1 commits)")[![camikazegreen](https://avatars.githubusercontent.com/u/1509771?v=4)](https://github.com/camikazegreen "camikazegreen (1 commits)")[![bberndt-uaz](https://avatars.githubusercontent.com/u/74572157?v=4)](https://github.com/bberndt-uaz "bberndt-uaz (1 commits)")[![aslaymoore](https://avatars.githubusercontent.com/u/52931751?v=4)](https://github.com/aslaymoore "aslaymoore (1 commits)")

---

Tags

hacktoberfest

### Embed Badge

![Health badge](/badges/az-digital-az-quickstart-scaffolding/health.svg)

```
[![Health](https://phpackages.com/badges/az-digital-az-quickstart-scaffolding/health.svg)](https://phpackages.com/packages/az-digital-az-quickstart-scaffolding)
```

###  Alternatives

[drupal-composer/drupal-project

Project template for Drupal 10 projects with Composer

1.6k829.0k](/packages/drupal-composer-drupal-project)[fourkitchens/sous-drupal-project

Starter project for Sous a Drupal distribution featuring a theme based on Emulsify Design System.

151.0k](/packages/fourkitchens-sous-drupal-project)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
