Start with the next ordinary edit
The designer knows where everything lives on launch day. The client may return three months later to replace a portrait and add a project. Write the handover around that small task. Name the source folder, explain how a new page becomes public and show which image sizes the layout expects. Include the actual project title used in the demonstration. Instructions become easier to follow when they refer to something the client can recognise on screen.
Separate ownership from access
List who controls the domain registration, the hosting account and any service that receives a contact message. Record renewal owners and the route for requesting access. Store passwords and recovery codes in an appropriate private system rather than in the public website or a widely shared PDF. A portfolio can have beautiful pages and still be difficult to maintain if its domain is tied to an account nobody on the client team can recover.
Check the page as a visitor sees it
Open the preferred address and its common alternate hostname. Follow a project link directly, then load an image and a deliberately missing page. Check that the secure version also loads its resources securely: GitHub’s HTTPS documentation explains how HTTP resource references can create mixed-content problems. The hosting platform may differ, but the visitor’s experience is still the thing to verify. A successful upload alone does not tell you whether the public address behaves correctly.
Give hosting a place in the brief
Before choosing a host, decide who will upload releases, renew certificates and help with an unavailable site. If comparing KoDDoS hosting options, put those responsibilities alongside storage and transfer requirements, then ask which are included in the proposed service. A static portfolio can simplify publishing, but it still needs an operating arrangement. Keep the choice tied to the client’s ability to maintain the site rather than to a feature list they will never use.
Rehearse the handover together
Ask the recipient to make the sample edit using the written instructions while the designer observes. Note every missing step and revise the document. Keep a dated previous release and describe how to recover it without overwriting the only good copy. Finish by recording which person now owns each recurring task. The useful handover is the one a real recipient can follow, not the one with the longest inventory of software and settings.
Put it into practice
Next likely edit: __________
Publishing owner: __________
Domain renewal owner: __________
Private access record: __________
Previous release and recovery steps: __________
Acceptance exercise: replace one sample image, publish it, check its project page, then identify the release that could be restored.
Sources & further reading
Examples and worksheets on this page are illustrative. Documentation links were checked in November 2026; follow the relevant product’s current instructions.
