What I need from you

#1 Access to your code repository

The first is access to your site's code repository. That's where the code is stored and tracked. I work in GitHub.

Ask your developer to give me read access first, so I can see how your site is built and what it connects to. Once the plan starts, I'll need write access to commit updates. I'll send my details when you get in touch.

If your code is on another service, such as Bitbucket, I can move it to a GitHub account in your name, with its full history. If your developer still works on the site, I'll work wherever they do, so the code stays in one place.

#2 Access to Ploi or Laravel Forge

The second is access to the tool that manages your server. I work with two, Ploi and Laravel Forge. They're how I set up SSH access to your server, deploy updates and keep it patched. Ask your developer to add me to whichever one your site uses.

If your server isn't managed by either, a Statamic migration comes first. You set up a Ploi or Laravel Forge account in your name, and I arrange the server installation, either with your current hosting provider or a new one.

I'll also need your site's .env files for local, staging and production environments. They hold the settings your site needs to run, so they aren't kept in the code repository. Ask your developer to share them through a secure link, such as 1Password or Onetime Secret, rather than by email.

#3 Check your version and licences

While you're talking to your developer, ask which version of Statamic your site runs. It needs to be on the current major version. If it's on an older one, a Statamic upgrade comes first.

If your site runs Statamic Pro, it also needs a licence with an active update subscription, along with any paid add-ons it uses. You renew and pay for these each year. They aren't part of the plan, and updates pause while a licence has lapsed.

If anything else is needed, I can liaise with your in-house team, web developer or hosting provider to get it.