a825335673
Set to 'off' by default. This will replace our intuiting the need to bust out when a hero class is applied with the style classes dropdown. Someday, probably when we've moved beyond paragraphs, it would be so nice to have configurations of the art direction options themselves, so that regular usage is picking from a couple arranged options but there's an advanced option to get more granular. But for now, we'll live with the editor having to understand how things are supposed to work together. |
||
|---|---|---|
| box | ||
| config/sync | ||
| drush | ||
| provisioning | ||
| web | ||
| .gitignore | ||
| .gitmodules | ||
| composer.json | ||
| composer.lock | ||
| phpunit.xml | ||
| README.md | ||
| Vagrantfile | ||
Get submodules
This project includes the Agaric styleguide as a git submodule.
When cloning
git clone --recurse-submodules git@gitlab.com:agaric/sites/agaric-com.git
If you cloned without --recurse-submodules
If in your initial clone you didn't do as above, you can get the styleguide with:
git submodule init
git submodule update
Get started
To be able to import the configuration, you need to get the initializing database (where we will also be collaborating on content) from the test site pending resolution of drutopia#216.
vagrant ssh
composer install
drush -y sql-dump > /tmp/paranoia.sql && drush sql-drop && drush -y sql-sync @test @self && drush -y updb
Get updates
git submodule update --recursive --remote
Theming
See web/themes/custom/agarica/README.md and web/themes/custom/agarica/patternlibrary/README.md
Deployment
Agaric is currently using a Platform as a Service version of Drutopia with additional modules.
Set up drutopia_host and hosting_private, as documented in hosting private.
Then use ahoy, from within the hosting_private directory.
If Agaric's Drutopia PaaS base has changed (the composer.lock in this directory), produce and push a new build:
ahoy deploy-build agaric
To deploy everything else (config, templates, styles):
ahoy deploy-site agaric_live
If you need to overwrite live configuration (only after confirming you've committed any parts you want to keep) you can use ahoy for that too with deploy-site-force.