Custom code
Website maintenance for custom Next.js and Vercel sites
Hank works in your repo like a careful developer on your team. Every change is a branch, a pull request and a Vercel preview, and nothing merges until you approve.
What Hank does on custom code
- Changes made in your GitHub repo on a branch, with a pull request that says what changed and why.
- A Vercel preview link for every change, sent to you in the thread.
- Merges on your approval, then a check of the live site on desktop and mobile.
- Content in Sanity or another headless CMS, edited in the studio where it already lives.
- Dependency updates with a changelog, so you know what moved.
- Lighthouse and Core Web Vitals checks to catch slow pages before your visitors do.
How access works
Add Hank as a GitHub collaborator on the repo, a member of your Vercel team (preview access only, if you prefer) and an editor in your CMS.
Branch protection on your main branch stays on. He works through pull requests like anyone else, and you can remove him from each tool in one step.
Good to know
- He follows the conventions already in your repo: your formatting, your commit style and your review process.
- Big refactors and new features are projects, and they get a separate quote.
- Other stacks work the same way. If it lives in a repo and runs in a browser, Hank can work on it.
Custom code questions
All questionsCan he push to main?
No. He works on branches and opens pull requests. Merges happen on your approval.
Which frameworks does he work with?
Next.js on Vercel is the most common setup. Other frameworks in a GitHub repo work the same way: branch, pull request, preview, merge.
Does he run our tests?
Your CI runs on his pull requests like any other. He reads the results and fixes what fails before asking you to review.
What Hank handles on custom sites
Get your site off your to-do list
Hank is live within a week of signing up. You can go back to your actual job.