Web Framework Assistant

The Web Framework Assistant is a Slack bot used to perform devops tasks for Mercury Web Framework websites. This includes DX Engine, Profile Management Hub, Campaign Sites, Edge, HealthAdvisor, HealthHub, and HealthPrints.

Access

The Assistant is available to users in the Mercury Healthcare Slack domain who have been granted access. Users may be given one of two access levels: Administrator or Editor. Administrators may use any command, while editors are restricted from using more sensitive commands. If you would like to gain access or increase your level of access, please direct your request to the #web-framework-assistant support channel on Slack.

Usage

You can access the Assistant by opening Slack and sending a direct message to the Web Framework Assistant. If you start the message with "/wf", you will see a list of available commands. Entering any of these will launch a dialog where you will be presented with the options for executing the command.

All Web Framework sites have a dev environment. Many also have a test and live environment. If you're unsure which environment to use when executing a command, select "Default". The command will execute on the live environment if it exists and back up to the dev environment if not.

Note: When selecting a site from within a dialog, you can type all or part of the site's name or domain to filter the list.

Commands

Create a new Web Framework site.

Command:: /wfcreate
Access:: Editors and administrators

This command will create a new Web Framework site using the options you provide. The new site will have all the content and settings of the selected template site, as well as brand settings from the selected brand site (see /wfbrand below for details). Certain site-specific settings (phone number placeholder, GTM container ID, form integrations) will automatically be scrubbed from the new site to keep it from inadvertently passing data into existing campaigns.

Please be sure to select the purpose that best fits the site's intended use.

Client demos* are meant for internal use in client meetings and sales opportunities.
Contract* sites are being paid for as part of an ongoing campaign or contract.
Mercury resources* are sites for internal use by Mercury Healthcare.
Templates are meant to be starting points when creating other Web Framework sites.
Test sites are temporary sites created to try out Web Framework functionality. Note: Test sites are retired at the end of each month.
Training sites are temporary sites created for training purposes.
Other should only be used as a purpose if no other purpose fits.

* - Client demos, contract sites, and Mercury Healthcare resources automatically receive live environments and randomized passwords. Sites with other purposes receive a dev environment and a default password, but can be pushed live using /wfutility (see below). Whenever a live environment is created, that site's dev and test environments will be locked to prevent editors from building in the wrong environment.

Log into a Web Framework site.

Command:: /wflogin
Access:: Editors and administrators

This command will create a link to log you into the selected site and environment as the Mercury Healthcare user. Note that the login link only works once; if you need it again, you will have to run the command again.

Update a Web Framework site.

Command:: /wfupdate
Access:: Editors and administrators

This command will push the latest development changes to the selected site and environment(s). Note that all sites are updated at least monthly, so this command is unnecessary unless you know a specific change has been added recently.

Run a utility script on a Web Framework site.

Command:: /wfutility
Access:: Editors and administrators (except "Lock or unlock a site environment")

This command executes a utility scripts on the selected site and environment.

Add a payment plan - Add a basic payment plan to the site in Pantheon. This is required before adding a domain.
Back up - Generate a one-off backup of the site files and database.
Clear cache - Clear the site's Drupal cache.
Configure security headers - Configure the Permissions Policy and SecKit modules to achieve good scores on automated security header audits.
Fix "failed login attempts" error - Remove the error that prevents further attempts after several failed login attempts.
Fix styles - Forcibly regenerate the site's stylesheets.
Link me to the Pantheon dashboard - Generate a link to the site's Pantheon dashboard. This can be useful for identifying the Pantheon site attached to a particular domain.
Link me to the site - Generate a link to the site. This will generate a link to the primary domain if one is set in Pantheon. Otherwise, it will generate a link to the platform domain (ending in .pantheonsite.io).
Lock or unlock a site environment - Apply or remove an htaccess login prompt from the site.
Protect all webforms with Honeypot - Enable Honeypot module protection on all webforms. This can be useful for reducing spam submissions, but may rarely block legitimate submissions.
Push live - Add a test and live environment to a site that only has a dev environment. The site's dev and test environments will be locked to prevent editors from building in the wrong environment.
Remove a payment plan - Remove an existing payment plan and set a site to sandbox mode.

Backup and delete a Web Framework site.

Command:: /wfretire
Access:: Administrators only

This command will back up the files and database of the selected site before deleting it. File sizes and checksums are compared at each stage to ensure data integrity, with the deletion firing if and only if all checks pass. Backups are stored on a dedicated Amazon S3 bucket accessible by Stephen Ward (@sward), Andy Waldrop (@andywaldrop), Adam Poulsen (@apoulsen), and Rusty Cage (@Rusty Cage).

Add a domain to a site.

Command:: /wfdomain
Access:: Editors and administrators

This command will add a carefinder.io or healthprints.io subdomain to a site. If the site has no test or live environment, those will be created first. If the site has no payment plan, one will be added. The necessary A and AAAA records will then be added to Godaddy. SSL will be added automatically, as well, but may take up to an hour to propagate.

Apply a brand to a DX Engine site.

Command:: /wfbrand
Access:: Editors and administrators

This command will copy the DX Engine brand from one DX Engine site to another. Optionally, you can choose to import the DX Engine theme settings at the same time. Note that this command no longer functions on Campaign Sites using the older Branded theme.

Support

The Web Framework Assistant is built and maintained by Stephen Ward on behalf of Mercury Healthcare. Please refer any issues or feature requests to the #web-framework-assistant support channel on Slack.