Download the PHP package localgovdrupal/localgov_microsites without Composer
On this page you can find all versions of the php package localgovdrupal/localgov_microsites. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download localgovdrupal/localgov_microsites
More information about localgovdrupal/localgov_microsites
Files in localgovdrupal/localgov_microsites
Package localgov_microsites
Short Description LocalGov Drupal Microsites distribution
License GPL-2.0-or-later
Homepage https://github.com/localgovdrupal/localgov_microsites
Informations about the package localgov_microsites
LocalGov Drupal Microsites
Drupal distribution and install profile to help UK councils collaborate and share Drupal code for publishing website content across a number of microsites from a single Drupal installation.
This repository is the Drupal installation profile that is best installed using composer to require a project template, localgov_microsites_project, to scaffold and build the codebase which includes this profile.
Please see https://github.com/localgovdrupal/localgov_microsites_project
Funding
This work was initially funded by the Local Digital Fund (https://www.localdigital.gov.uk/fund/) from the Department for Levelling Up, Housing and Communities (DLUCH).
Supported branches
We are actively supporting and developing the 4.x branch for Drupal 10.
The 1.x, 2.x and 3.x branches are no longer actively supported and not recommended for new sites.
If you are still using the 1.x, 2.x or 3.x branches on your site, please create an issue on Github to let us know.
Documentation
Further documentation for developers, content designers and other audiences can be found at https://docs.localgovdrupal.org/microsites/.
Installation
For installation steps, see: https://github.com/localgovdrupal/localgov_microsites_project
Requirements for installing LocalGov Drupal locally for testing and development
To install LocalGov Drupal locally you will need an appropriate versions of:
- PHP (see https://www.drupal.org/docs/system-requirements/php-requirements)
- A database server like MySQL (see https://www.drupal.org/docs/system-requirements/database-server-requirements)
- A web server like APache2 (see https://www.drupal.org/docs/system-requirements/web-server-requirements)
Many of us use the Lando file included to run a local docker environmnent for testing and development, but seom people prefer to run the web servers natively on their host machine.
PHP requirements
We folllow Drupal's PHP recomendations: https://www.drupal.org/docs/system-requirements/php-requirements#versions
We currently recomend and test against PHP 8.1 and 8.2.
You will also need to have certain PHP extensions enabled (see https://www.drupal.org/docs/system-requirements/php-requirements#extensions) including:
- PHP mbstring
- PHP cURL
- GD library
- XML
If you see errors when running composer require, double check your PHP extensions.
Developer notes for default content
This profile creates a single node of demo content using the https://www.drupal.org/project/default_content module.
This node includes layout paragraphs and paragraph content to demonstrate some of the content components available for a new microsite. When a new microsite is created, it attempts to clone this node into the new microsite.
As developers, we often want to update the default content, using drush.
To export an item of content and all references:
So for node/1:
Composer and Lando
To install locally, you will need Composer and we recommend using Lando for a consistent developer environment.
Please also see the Lando requirements section for details of Docker requirements for different operating systems.
https://docs.lando.dev/basics/installation.html#system-requirements
Installing LocalGov Drupal locally with composer
To install LocalGov Drupal locally for testing or development, use the Composer-based project template.
Change MY_PROJECT
to whatever you'd like your project directory to be called.
Change directory into the MY_PROJECT directory and run lando start.
Once lando has finished building, use lando to run composer install and the site installer.
Note: As you might be running a different version of PHP on your host machine from the version that Lando runs, it is advisable to run composer install from within Lando. This ensures dependencies reflect the PHP version that the webserver is actually running.
Composer notes
If developing locally and you want to force composer to clone again
from source rather than use composer cache, you can add the --no-cache
flag.
If you just want to pull in the latest changes to LocalGov Drupal run composer
update with the --no-cache
flag.
If you want to be sure you are getting the latest commits when developing, clearing composer cache, deleting the folders and re-running composer update seems to be a solid approach:
If you run into memory limit errors
when running Composer commands, prefix the commands with COMPOSER_MEMORY_LIMIT=-1
.
For example, to install the project run:
Contributing
See CONTRIBUTING.md for current contribution guidelines.
Issue tracking
Most issues will be tracked in this repository https://github.com/localgovdrupal/localgov_microsites/issues.
Development issues relating to specific projects or module should be tracked in the project repository.
Development setup
The main development environment in use is currently Lando – a Docker based development environment that works on Linux, MacOS and Windows.
@todo Document Lando setup.
Coding standards
PHP CodeSniffer is installed as a dev dependency by Composer and configured to use Drupal coding standards and best practices. It is a good idea to run these before committing any code. All code in pull requests should pass all CodeSniffer tests.
To check code using Lando run:
To attempt to automatically fix coding errors in Lando run:
Coding standards resources
Running tests
The included phpunit.xml.dist
file contains configuration for automatically
running the LocalGov Drupal test suite.
To run all LocalGov Drupal tests with Lando use:
To run all the tests for a specific module use:
Tests can be filtered using the --filter
option. To only run a specific test
use:
Testing resources
- PHPUnit documentation
- Drupal 8 PHPUnit documentation
- Drupal 8 testing documentation
- Workshop: Automated Testing and Test Driven Development in Drupal 8
Maintainers
This project is currently maintained by:
- Ekes: https://www.drupal.org/u/ekes
- Finn Lewis: https://www.drupal.org/u/finn-lewis
- Maria Young: https://www.drupal.org/u/mariay-0
- Mark Conroy: https://www.drupal.org/u/markconroy
- Stephen Cox: https://www.drupal.org/u/stephen-cox
All versions of localgov_microsites with dependencies
drupal/admin_toolbar Version ^3.1
drupal/autosave_form Version ^1.3
drupal/core Version ^10.0
drupal/default_content Version ^2.0@alpha
drupal/domain_path Version ^1.2
drupal/gin Version ^3.0@RC
drupal/gin_login Version ^2.0
drupal/gin_toolbar Version ^1.0@RC
drupal/metatag Version ^2.0.2
drupal/redirect Version ^1.9
drupal/responsive_preview Version ^2.1
localgovdrupal/localgov_blogs Version ^1.0.0-beta3
localgovdrupal/localgov_core Version ^2.12
localgovdrupal/localgov_directories Version ^3.1
localgovdrupal/localgov_events Version ^3.0
localgovdrupal/localgov_microsites_group Version ^4.0
localgovdrupal/localgov_microsites_base Version ^2.0
localgovdrupal/localgov_microsites_colour_picker_fields Version ^1.0.0-beta1
localgovdrupal/localgov_news Version ^2.3
localgovdrupal/localgov_page Version ^1.0.0-beta2
localgovdrupal/localgov_claro Version ^2.1.0
localgovdrupal/localgov_sa11y Version ^1.0.0-beta1
drupal/require_login Version ^3.0