0:00
30:11
Mike and Amanda share practical tips for handing off a website smoothly, whether you’re the developer or the client.
Overview
Mike and Amanda share practical tips for handing off a website smoothly, whether you’re the developer or the client. They cover who should own accounts, how to store and share credentials, documentation people will actually use, and how to hand off code and train the right people.
Key Topics
- Accounts and ownership
- Have the client create a shared admin or webmaster email address for service signups
- Domain, hosting, and payments should be in the client’s name, so renewal notices go to them
- Invite the developer as an additional user on services like Mailchimp, Google, and Stripe, so they have their own login and two-factor authentication
- A CMS license tied to a former employee’s email caused a registration mess for one project
- Credentials and recovery
- Use a password manager like 1Password or Bitwarden instead of shared docs or emails
- Shared vaults and notes, including links that expire
- Recovery emails and phone numbers tied to someone who leaves
- Question for listeners: which password manager do you use?
- Documentation
- Short screencast videos for managing content, sometimes kept in a documentation section inside the CMS
- A one-page document listing where the domain, hosting, and accounts live, with no passwords in it
- Content guides and brand guidelines, and why developers remove options like text color and underline from editors
- Handing off a Git repo
- Creating the repo under the client’s organization, or transferring ownership at the end
- Staying on as a collaborator or administrator
- People and training
- Choosing one point of contact for the project
- Training only the handful of people who will manage the site
Key Takeaways
- A shared admin email means accounts don’t depend on one person staying at the company
- Clients should own and pay for their domain, hosting, and CMS licenses
- Developers should be added as users on each service, not log in with the client’s credentials
- Store credentials in a password manager, and never put them in an email or shared document
- Check that recovery emails and phone numbers won’t disappear when someone leaves
- Short screencasts are faster to make than written documentation, and clients like them
- Limiting editor options protects both the brand and accessibility, such as text contrast
- Transferring a Git repo gives the next developer a place to start
- One contact on the client side keeps the project smooth, and training only the people who need it keeps the handoff simple
Show Links
More Website 101 Podcast
Więcej odcinków z kanału "Website 101 Podcast"
Nie przegap odcinka z kanału “Website 101 Podcast”! Subskrybuj bezpłatnie w aplikacji GetPodcast.
