diff --git a/.github/ISSUE_TEMPLATE/launch-analytics.md b/.github/ISSUE_TEMPLATE/launch-analytics.md new file mode 100644 index 0000000..6cf10bd --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-analytics.md @@ -0,0 +1,17 @@ +--- +name: Launch - Analytics +about: Checklist of analytics related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Configure Google Tag Manager if applicable. +- [ ] Configure Google Analytics or your analytics tool of choice. +- [ ] Verify analytics tools are only reporting from the production environment or reporting separately depending on requirements. diff --git a/.github/ISSUE_TEMPLATE/launch-development.md b/.github/ISSUE_TEMPLATE/launch-development.md new file mode 100644 index 0000000..0f8bb37 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-development.md @@ -0,0 +1,47 @@ +--- +name: Launch - Development +about: Checklist of development related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Verify that the mapping in `sites.php` supports the production domain. +- [ ] Verify that PHP error messages are suppressed. +- [ ] Disable database logging for production. +- [ ] Enable syslog for production. +- [ ] Verify that config splits are enabled/disabled appropriately in all environments. +- [ ] Check logs for recurring PHP notices/warnings/errors. +- [ ] Fix recurring issues found in the site logs. +- [ ] Check the browser console for recurring errors. +- [ ] Fix recurring issues found in the browser console. +- [ ] Verify that Stage File Proxy is disabled on PROD. +- [ ] Enable and configure Stage File Proxy for non-production environments. +- [ ] Verify that config exports and imports cleanly. +- [ ] Verify that the config check tooling is enabled in Tugboat. +- [ ] Determine the necessary cron frequency. +- [ ] Validate that a cron trigger is configured and the frequency is acceptable. +- [ ] [Disable Drupal system cron](https://www.drupal.org/docs/administering-a-drupal-site/cron-automated-tasks/cron-automated-tasks-overview#s-disabledrupal-cron). +- [ ] Verify that the deployment process works. +- [ ] Verify that Drupal's status report page is clear of issues. +- [ ] Verify that migrations are complete. +- [ ] Configure field help/descriptive text. +- [ ] Optimize media creation/referencing experience. +- [ ] Verify that meta tags & JSON-LD are configured. +- [ ] Verify that images are being served in an efficient manner. +- [ ] Verify that no API keys or sensitive credentials are stored in code. +- [ ] Determine if "helper" node types and/or taxonomy term pages should appear and hide or block access as needed. +- [ ] Verify that alias patterns and updates/redirects are working correctly. +- [ ] Verify that `$settings['hash_salt']` is set. +- [ ] Verify that `$settings['update_free_access'] = FALSE;` is set. +- [ ] Verify that `$settings['omit_vary_cookie']` is configured correctly. +- [ ] Verify that `$settings['file_public_path']` and file_private_path are configured correctly. +- [ ] Confirm that the 404 page is working and styled as expected. +- [ ] Verify that `$settings['reverse_proxy_*']` configuration is set correctly if a CDN or reverse-proxy is being used. +- [ ] Run performance tests with a tool such as Calibre, Lighthouse, or PageSpeed Insights and fix the issues and/or log post launch tickets. diff --git a/.github/ISSUE_TEMPLATE/launch-final.md b/.github/ISSUE_TEMPLATE/launch-final.md new file mode 100644 index 0000000..a0fcabf --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-final.md @@ -0,0 +1,61 @@ +--- +name: Launch - Final +about: Final checklist of tasks to complete before a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +## Migration +- [ ] Confirm that the content migration is complete. + +## Account Management +- [ ] Set expectations for post-launch support. +- [ ] Determine what our next engagement will look like. +- [ ] How long will the team continue working under the current engagement after launch? +- [ ] What bugs will we fix after launch without incurring cost? +- [ ] What PTO or resourcing shifts does the client need to be aware of? + +## General +- [ ] Validate that initial QA is complete. +- [ ] Validate that all content has been entered/updated. +- [ ] Set expectations with the client about what will happen on launch day. +- [ ] Determine if the launch date is still feasible given the results of QA. + +## Project Management +- [ ] Validate that all development work is complete and notify the client. +- [ ] Determine and communicate the expectations we have of the client prior to launch. +- [ ] Validate that all parties are clear on what will and will not be going live at launch. +- [ ] Plan project close actions. +- [ ] Document process for denoting launch blocker bugs. + +## Launch Prep +- [ ] Create a roll-back plan. +- [ ] Notify the devops team and confirm they understand what needs to occur. +- [ ] Create an ordered checklist and timeline. +- [ ] Determine who will make the go/no-go call for launch. +- [ ] Determine who will decide if a roll-back is needed. +- [ ] Determine who manages DNS and confirm they will be available to update the entries for launch. +- [ ] Lower DNS TTL to ensure quick propagation on launch day. +- [ ] Verify that `robots.txt` is configured to allow traffic to the production site (i.e. remove any changes that were made for development). +- [ ] Verify that users of the site are aware of the cut-over time/plan. +- [ ] Create a calendar invite with a video call link that can be shared with everyone who is involved with the launch. +- [ ] Verify that user accounts have been migrated or recreated, and that users have access they need. +- [ ] Validate that bug fixes are complete or will be completed on time. +- [ ] Confirm that the final QA is complete. +- [ ] Confirm that we have launch approval from the needed stakeholders. +- [ ] Implement a code freeze state and communicate this with the team. + +## Launch Day +- [ ] Let the client know when the launch process begins. +- [ ] Disable HTTP Authorization if applicable. +- [ ] Update DNS entries. +- [ ] Update SSL certs as needed. +- [ ] Test the site manually for large obvious issues. +- [ ] Run through the previously created test plan. diff --git a/.github/ISSUE_TEMPLATE/launch-hosting.md b/.github/ISSUE_TEMPLATE/launch-hosting.md new file mode 100644 index 0000000..dee90f0 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-hosting.md @@ -0,0 +1,26 @@ +--- +name: Launch - Hosting +about: Checklist of hosting related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Determine who will provide the SSL certificate. +- [ ] Setup HTTPS and test the SSL certificate. +- [ ] Setup SSL certificate reminders. +- [ ] Verify that the web server instance size is large enough. +- [ ] Verify that HTTP/2 is enabled. +- [ ] Configure redirects from www to the base URL (or vice-versa). +- [ ] Create and test redirect rules. +- [ ] Create and test reverse-proxy rules. +- [ ] Verify that asset compression is enabled. +- [ ] Determine who is responsible for the DNS and what needs to happen and when. +- [ ] Determine who is responsible from the hosting provider. What do they need from us to deliver when and how we want them to? +- [ ] Determine who is responsible from the client’s IT team. Security team? What do they need from us to deliver when and how we want them to? diff --git a/.github/ISSUE_TEMPLATE/launch-performance.md b/.github/ISSUE_TEMPLATE/launch-performance.md new file mode 100644 index 0000000..b944e12 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-performance.md @@ -0,0 +1,25 @@ +--- +name: Launch - Performance +about: Checklist of performance related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Enable Drupal Page caching if applicable. +- [ ] Enable Drupal Big Pipe caching if needed. +- [ ] Verify that custom render array cache metadata is set and tested. +- [ ] Determine if CSS/JavaScript aggregation should be enabled. +- [ ] Verify that development related services are disabled (e.g. development.services.yml) +- [ ] Verify Redis connectivity and Redis is used for caching. +- [ ] Verify that Redis is using the correct cache prefix if applicable. +- [ ] Configure and test the CDN if applicable. +- [ ] Verify the CDN is serving HITs if applicable. +- [ ] Verify Varnish is serving HITs if applicable. +- [ ] Configure and test the load balancer if applicable. diff --git a/.github/ISSUE_TEMPLATE/launch-planning.md b/.github/ISSUE_TEMPLATE/launch-planning.md new file mode 100644 index 0000000..6b14cde --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-planning.md @@ -0,0 +1,31 @@ +--- +name: Launch - Planning +about: Checklist of initial planning related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Determine when/if a content freeze should occur. +- [ ] Determine who is responsible for entering/updating content and when that will occur. +- [ ] Determine launch date and time. +- [ ] Determine production domain. +- [ ] Determine if any existing traffic needs to be proxied or redirected. +- [ ] Determine how redirects will be handled if they are needed. +- [ ] Determine where the starting database will come from. +- [ ] Determine who manages DNS. +- [ ] Determine the caching strategy. +- [ ] Take screenshots of "before" site. +- [ ] Add site to [web.archive.org](http://web.archive.org/). + +## QA Process +- [ ] Determine if a QA site is needed. +- [ ] Confirm that `robots.txt` or the corresponding HTTP header is configured to block traffic to the QA site. +- [ ] Implement password protection with HTTP Authorization if required. +- [ ] Verify that proper testing API keys are configured if needed. diff --git a/.github/ISSUE_TEMPLATE/launch-post.md b/.github/ISSUE_TEMPLATE/launch-post.md new file mode 100644 index 0000000..59bd3ee --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-post.md @@ -0,0 +1,30 @@ +--- +name: Launch - Post Launch +about: Checklist of tasks to complete after a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +## Development +- [ ] Monitor site log for errors. +- [ ] Verify caching is working as intended. +- [ ] Verify analytics is reporting as expected. +- [ ] Run performance tests with a tool such as Calibre, Lighthouse, or PageSpeed Insights to confirm the site performs as expected. +- [ ] Update Stage File Proxy origin URL configuration to point to the production domain (e.g. $config['stage_file_proxy.settings']['origin']). +- [ ] Confirm that third party integrations are working as expected. +- [ ] Add site to [updown.io](https://updown.io) uptime monitoring. +- [ ] Disable migration related modules and source database connectivity as applicable. +- [ ] Configure Sentry if applicable. + +## Ongoing Process +- [ ] Update automated or manual tests to point to the new production domain. +- [ ] Determine if the git branching strategy, merging rules, or any development workflows should be adjusted. +- [ ] Update QA environments to pull databases from the new production site. +- [ ] Update or create database backup scripts to backup the production site. diff --git a/.github/ISSUE_TEMPLATE/launch-qa.md b/.github/ISSUE_TEMPLATE/launch-qa.md new file mode 100644 index 0000000..c935b6d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-qa.md @@ -0,0 +1,23 @@ +--- +name: Launch - QA +about: Checklist of QA related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Create a testing plan with milestones, impacts of missing key dates, how unknowns will be handled, etc and share it with all stakeholders. +- [ ] Determine who is testing and what they are testing. +- [ ] Determine how testing results are tracked. +- [ ] Determine how the impacts of QA bugs will affect the launch date. +- [ ] Reference the [Chromatic testing plan](https://docs.google.com/document/d/1l0TA64OII2yu8DICWu-sFvE_MgBPoW3zXQn9VUQQKVY/edit#). +- [ ] Document supported browsers. +- [ ] Include expected functionality. +- [ ] Document A11y requirements. +- [ ] Communicate that the QA phase has officially begun. diff --git a/.github/ISSUE_TEMPLATE/launch-security.md b/.github/ISSUE_TEMPLATE/launch-security.md new file mode 100644 index 0000000..96945ca --- /dev/null +++ b/.github/ISSUE_TEMPLATE/launch-security.md @@ -0,0 +1,20 @@ +--- +name: Launch - Security +about: Checklist of security related tasks to complete for a site launch. +title: '' +labels: '' +assignees: '' + +--- + +Please check off line-items as they are completed and leave notes if necessary. +If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) +(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for +any line-item, please update this description to include references to them. + +- [ ] Consider installing & configuring the [SecKit module](https://www.drupal.org/project/seckit). +- [ ] Verify that development related accounts/passwords have been reset or removed. +- [ ] Verify that proper permissions are set on `settings.php` and `services.yml` files. +- [ ] Confirm that development modules are disabled on production (e.g. `kint`, `devel_generate`, `devel`, etc). +- [ ] Verify that `$settings['trusted_host_patterns']` is configured. +- [ ] Verify that database updates via the UI are disabled (`$settings['update_free_access'] = FALSE;`). diff --git a/.github/ISSUE_TEMPLATE/launch.md b/.github/ISSUE_TEMPLATE/launch.md deleted file mode 100644 index 5ede34b..0000000 --- a/.github/ISSUE_TEMPLATE/launch.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -name: Launch -about: Prepare for a site launch with a checklist of common steps. -title: '' -labels: '' -assignees: '' - ---- - -Please check off line-items as they are completed and leave notes if necessary. -If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) -(e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for -any line-item, please update this ticket description to include references to -those tickets. - -## Preparation -- [ ] Determine production domain. -- [ ] Determine if any existing traffic needs to be proxied or redirected. -- [ ] Determine how redirects will be handled if they are needed. -- [ ] Determine where the starting database will come from. -- [ ] Determine who manages DNS. -- [ ] Determine the caching strategy. -- [ ] Take screenshots of "before" site. -- [ ] Add site to [web.archive.org](http://web.archive.org/). - -## Security -- [ ] Consider installing & configuring the [SecKit module](https://www.drupal.org/project/seckit). -- [ ] Verify that development related accounts/passwords have been reset or removed. -- [ ] Verify that proper permissions are set on `settings.php` and - `services.yml` files. -- [ ] Confirm that development modules are disabled on production - (e.g. `kint`, `devel_generate`, `devel`, etc). -- [ ] Verify that `$settings['trusted_host_patterns']` is configured. - -## Analytics -- [ ] Configure Google Tag Manager if applicable. -- [ ] Configure Google Analytics or your analytics tool of choice. -- [ ] Configure New Relic if applicable. -- [ ] Verify analytics tools are only reporting from the production environment - or reporting separately depending on requirements. - -## QA Site -- [ ] Determine if a QA site is needed. -- [ ] Confirm that `robots.txt` or the corresponding HTTP header is configured - to block traffic to the QA site. -- [ ] Implement password protection with HTTP Authorization if required. -- [ ] Verify that proper testing API keys are configured if needed. - -## Performance -- [ ] Enable Drupal Page caching. -- [ ] Enable Drupal Big Pipe caching if needed. -- [ ] Verify that custom render array cache metadata is set and tested. -- [ ] Determine if CSS/JavaScript aggregation should be enabled. -- [ ] Verify that development related services are disabled (e.g. - `development.services.yml`) -- [ ] Verify Redis connectivity and Redis is used for caching. -- [ ] Verify that Redis is using the correct cache prefix if applicable. -- [ ] Configure and test the CDN if applicable. -- [ ] Verify the CDN is serving HITs if applicable. -- [ ] Verify Varnish is serving HITs if applicable. -- [ ] Configure and test the load balancer if applicable. -- [ ] Verify that cron runs from pages requests are disabled. - -## Development -- [ ] Verify that the mapping in `sites.php` supports the production domain. -- [ ] Verify automatic deployments are working. -- [ ] Verify that PHP error messages are suppressed. -- [ ] Disable database logging. -- [ ] Enable syslog. -- [ ] Verify that config splits are enabled/disabled appropriately in all - environments. -- [ ] Check logs for recurring PHP notices/warnings/errors. -- [ ] Fix recurring issues found in the site logs. -- [ ] Check the browser console for recurring errors. -- [ ] Fix recurring issues found in the browser console. -- [ ] Verify that Stage File Proxy is disabled on PROD. -- [ ] Enable and configure Stage File Proxy for non-production environments. -- [ ] Verify that config exports and imports cleanly. -- [ ] Determine the necessary cron frequency. -- [ ] Configure external cron trigger (Jenkins/Crontab/etc). -- [ ] Verify that the deployment process works. -- [ ] Check site error logs and fix persistent issues. -- [ ] Verify that Drupal's status report page is clear of issues. -- [ ] Verify that migrations are complete. -- [ ] Determine if git branching strategy or merge rules should be adjusted post - launch. -- [ ] Verify that no API keys or sensitive credentials are stored in code. -- [ ] Verify if "helper" node types and/or taxonomy term pages should appear and - hide or block access as needed. -- [ ] Verify that alias patterns and updates/redirects are working correctly. -- [ ] Verify that `$settings['hash_salt']` is set. -- [ ] Verify that `$settings['update_free_access'] = FALSE;` is set. -- [ ] Verify that `$settings['omit_vary_cookie']` is configured correctly. -- [ ] Verify that `$settings['file_public_path']` and `file_private_path` are - configured correctly. -- [ ] Confirm that the 404 page is working and styled as expected. -- [ ] Verify that `$settings['reverse_proxy_*']` configuration is set correctly - if a CDN or reverse-proxy is being used. -- [ ] Run performance tests with a tool such as Calibre, Lighthouse, or - PageSpeed Insights and fix the issues and/or log post launch tickets. -- [ ] Configure field help/descriptive text. -- [ ] Optimize media creation/referencing experience. -- [ ] Verify that meta tags & JSON-LD are configured. -- [ ] Verify that images are being served in a efficient manner. - -## Hosting -- [ ] Determine who will provide the SSL certificate. -- [ ] Setup HTTPS and test the SSL certificate. -- [ ] Setup SSL certificate reminders. -- [ ] Verify that the web server instance size is large enough. -- [ ] Verify that HTTP/2 is enabled. -- [ ] Configure redirects from `www` to the base URL (or vice-versa). -- [ ] Create and test redirect rules. -- [ ] Create and test reverse-proxy rules. -- [ ] Verify that asset compression is enabled. - -## Infrastructure -- [ ] Setup database backups in consultation with the devops team. -- [ ] Create Jenkins production cache clear job if applicable. -- [ ] Verify that Drupal's `settings.php` and `services.yml` files have the - correct read-only permissions. -- [ ] Confirm syslog visibility and connectivity with external tools. -- [ ] Verify that errors are configured to be suppressed. -- [ ] Setup Jenkins jobs for QA (and check that PROD jenkins jobs all running) -- [ ] Verify that Ansible playbooks follow the latest best practices. -- [ ] Verify file uploads work. -- [ ] Verify image styles work. -- [ ] Run load tests to validate infrastructure. -- [ ] Consult with the hosting provider for any platform specific launch steps - or advice. - -## Launch Prep -- [ ] Create a roll-back plan. -- [ ] Notify the devops team and confirm they understands what they need to do. -- [ ] Create ordered checklist and timeline. -- [ ] Determine who will make the go/no-go call for launch. -- [ ] Determine who will decide if a roll-back is needed. -- [ ] Determine who manages DNS and will update the entries for launch. -- [ ] Lower DNS TTL to ensure quick propagation on launch day. -- [ ] Verify that `robots.txt` is configured to allow traffic to the production - site (i.e. remove any changes that were made for development). -- [ ] Verify that users of the site are aware of the cutover time/plan. -- [ ] Create a calendar invite with a video call link that can be shared with - everyone who is involved with the launch. -- [ ] Verify that user accounts have been migrated or recreated, and that users - have access they need. - -## Site Launch -- [ ] Disable HTTP Authorization if applicable. -- [ ] Update DNS entries. -- [ ] Test the site manually for large obvious issues. - -## Post Launch -- [ ] Monitor site log for errors. -- [ ] Verify caching is working as intended. -- [ ] Verify analytics is reporting as expected. -- [ ] Run performance tests with a tool such as Calibre, Lighthouse, or - PageSpeed Insights to confirm the site performs as expected. -- [ ] Update QA environments to pull databases from the new production site. -- [ ] Update Stage File Proxy origin URL configuration to point to the - production domain (e.g. `$config['stage_file_proxy.settings']['origin']`). -- [ ] Update automated or manual tests to point to the new production domain. -- [ ] Confirm that third party integrations are working as expected. -- [ ] Add site to Updown.io uptime monitoring. -- [ ] Disable migration related modules and source database connectivity as - applicable. diff --git a/.github/ISSUE_TEMPLATE/setup.md b/.github/ISSUE_TEMPLATE/setup.md index 1aea196..36e1bdb 100644 --- a/.github/ISSUE_TEMPLATE/setup.md +++ b/.github/ISSUE_TEMPLATE/setup.md @@ -10,21 +10,18 @@ assignees: '' Please check off line-items as they are completed and leave notes if necessary. If an item is not relevant to this project, [strike it out](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#styling-text) (e.g. `~~Not relevant item~~`) or remove it. If child tickets are created for -any line-item, please update this ticket description to include references to -those tickets. +any line-item, please update this description to include references to them. - [ ] Create a README. - [ ] Set up [Tugboat](https://dashboard.tugboat.qa/). - [ ] Create an AWS user and S3 bucket with an access policy and bucket lifecycle rule for database backups ([documentation](https://github.com/ChromaticHQ/Chromatic-Handbook/blob/main/technical/database-backup-aws-s3.md)). - [ ] Set up Dependabot ([example](https://github.com/ChromaticHQ/chromatichq.com/blob/master/.github/dependabot.yml)). - [ ] Set up PHP code style checks. -- [ ] Set up GitHub Actions (example)[https://github.com/ChromaticHQ/chromatichq.com/tree/master/.github/workflows] - to run code style checks on YML, shell scripts, and execute PHP - checks/front-end linting tools. +- [ ] Set up GitHub Actions (example)[https://github.com/ChromaticHQ/chromatichq.com/tree/master/.github/workflows] to run code style checks on YML, shell scripts, and execute PHP checks/front-end linting tools. - [ ] Set up `settings.php` file infrastructure. - [ ] Set up a `composer.json` file. - [ ] Create a theme at `web/themes/custom/THEME_NAME`. -- [ ] Set up front-end tooling. +- [ ] Set up front-end tooling with [Calliope](https://github.com/ChromaticHQ/calliope). - [ ] A task to build the theme’s static assets. - [ ] Development workflow tasks to build assets automatically, watch for changes, refresh the browser automatically, etc. - [ ] CSS and JS linting tasks, as well as any other testing tasks that relevant to the project. diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..485dee6 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +.idea