Handing a site to a client
把站点交付给客户
The last step of a client project is a manual and a boundary: what the client's staff do alone, what needs the developer, what the developer supplies per client, and the one recurring duty the owner keeps.
Handover
The last step of a client project is a manual and a boundary.
The manual tells the client's staff how to add and edit pages. The boundary says what they do alone and what they call the developer for. The package ships a manual template, written in Chinese first with an English summary, because that is what the first clients read.
What the manual covers
- signing in to the admin on a desktop browser
- the composer: choose a family, paste text, upload photos, generate, ask for changes in plain language, publish
- editing a live page in place: click a text or a photo region, change it, save and publish or save as draft
- the pages list: publish, unpublish, archive, rename an address with old links redirecting, restore any earlier version
- the photo library and its captions
- costs and the usage page
Three promises the manual makes
- The site cannot be edited into inconsistency, because layout is locked in code and staff only ever edit content.
- The composer never invents dates, numbers or names; missing details appear as visible placeholders and every turn lists what it changed and what it could not find in the source.
- Every save is a revision, so any mistake can be undone.
What the client does alone
- add, edit, publish and unpublish pages
- change any wording, swap photos, reorder them, edit captions
- rename addresses and restore earlier versions
- read the usage page
What needs the developer
- a new page family, a design change or a structural page such as the home page
- restoring an archived page
- domains, keys, servers and other technical settings
- raising the question-box limits if real visitors reach them
What the developer supplies per client
A configuration file naming the families and the voice, one stylesheet, a header and a footer, credentials, and the manual with its placeholders filled. The template site generated by the starter script already composes pages before any of that is written, so a client site goes from nothing to authoring in well under a day of the developer's time.
The owner's one recurring duty
Set a monthly spend limit in each model vendor's console for the client's project. The site's own counters bound daily spend on the public question box, but the limit that holds if those counters fail is the one the vendor enforces.