Client Information - commotioncreativeltd/octobercms-deployment GitHub Wiki

Client Information

I like to standardise on the 3rd party tools and software I use across my client websites. I find this helps with consistency and management. Now, not all solutions are the right fit so use this as a guide and be aware you may need to find the right tool / solution for the specific requirements.

However, below are the tools / solutions I use and the information required to setup the client with an account.

Amazon Web Services (AWS)

  • full name
  • email
  • address
  • card details

NOTE: This will also require you to verify you are a human by calling you asking to enter a pin. This number does not need to be the same as the client information and can be your own office number. This helps with creating and setting up the account.

CloudFlare

CloudFlare has some great optimisations out of the box and has a FREE tier! The only downside to this is it requires changing a client's nameservers, which we've had some troubles getting in the past. However, CloudFlare copies the existing DNS setup as much as possible to reduce the chance of any downtime.

  • full name
  • email
  • domain management (or your client to update their nameservers)

Mailgun

  • full name
  • email

Stripe

  • full name
  • email
  • address
  • bank details (account number, sort code etc)

NOTE: Bank details are not needed until you need to go live with the Stripe account, but are required as Stripe needs 1 bank account on record to transfer funds to.

MailChimp

  • full name
  • email
  • address

Google Apps for Work

This is great for small businesses as it can provide a full IT infrastructure for as little as £3-4 per month / per user. Other solutions like Office 365 are also good solutions, however we preference Google Apps for Work.

  • full name
  • existing work account (this must NOT already be a Google Account in anyway)
  • recovery email (for the master Admin password recovery)
  • access to client DNS records

Google Analytics

If the client does not already have a Google Analytics account for their existing website I usually create an account for them, setup the defaults then grant access to Google Account to give to the client. If the client already has a Google Account, or they use Google Apps for Work then you can use one of thee accounts.

If they do have an existing Google Analytics account then you will need them to grant you access to the account.

Search Console

The easiest way to verify a website in Search Console is having permissions to the Google Analytics property for the Google Analytics script in the <head> of a web page. Their are other methods, but I will not go into detail about these here.

⚠️ **GitHub.com Fallback** ⚠️