The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
At handover, check that the source files and assets actually landed on your side. And get short notes on where everything lives.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
I just published a new FREE @Framer template: Cabvia, for private transfers. I built the pages around the questions travelers ask before requesting a ride: where they are going, who is coming and how much luggage needs to fit.
Building the pages around what a traveler asks before booking, where, who, how much luggage, is a smart structure. The warm beige on dark navy feels trustworthy for transfers. Is the luggage question its own step in the form?
10 checks before you launch
Launching a site this week? Run through these first:
Every form sends, and you receive the email
Favicon and social share image are set
Page titles and meta descriptions are written
The sitemap is submitted in Google Search Console
Analytics is recording visits
A 404 page exists and links back home
Old URLs redirect to their new pages
HTTPS everywhere, with no mixed-content warnings
Tested on a real phone, not just a narrow browser window
Backups are running
Save this for your next launch. Which one gets forgotten most? My vote: number 7.
#WebsiteLaunch #LaunchChecklist #WebDevelopment #Startup #WebsiteTips
Such a handy launch checklist.
• 1d
Things that broke in production (and the checks they became)
Backups that backed up nothing. The script dumped an empty Postgres database while n8n was actually running on SQLite, and the restore test didn't catch it. Now there are online SQLite snapshots, counts read before every dump, a 35-check restore test and a corruption drill that must fail.
A webhook down for five minutes. Recreating a container dropped n8n's manual attachment to the stack network. The network is now declared in compose.
Mail going to spam. After a network change, DKIM signing silently stopped. Lesson: test a mail fix on the path real mail takes, not from the host.
Every incident becomes a check in the static suite, which now stands at 1,400+ automated checks.