Separate source files from a content-editing interface
Source code consists of the files used to build a website. A content management system, or CMS, is a tool for editing information through an interface. Receiving the first does not mean the second is included, and editing capabilities depend on what has been agreed.
Both main website packages include website files and source code under the handover terms, but exclude a CMS. Before starting, explain how often you want to edit text yourself and who will look after the site in the longer term.
A domain name and website hosting have different roles
A domain is the name visitors use to access a website, while hosting is the system that serves its files and functions. Paying for a domain does not mean hosting or website maintenance is included. Check the period covered by each expense.
Record which account owns the domain, who manages hosting and who has permission to publish new versions. This reduces confusion when changing maintainers without requiring passwords to be shared with many people.
Ask for an update process that can be repeated
Know which files to edit, how to check a preview and how to publish to the live website, including how to restore an earlier version if there is a problem. If external tools or services are required, identify the requirements and responsible person before handover.
Do not assume that every package includes instructions, an automatic update system or ongoing maintenance. If you need these, agree the scope clearly and use accounts the business owner can control where appropriate.
- Files to be delivered and the type of website
- Domain-owner account, hosting and publishing permissions
- Steps for editing, previewing and going live
- Backups, rollback and maintenance requiring additional agreement
Keep a copy that can be brought back into operation
A folder of files alone may not be enough if it contains no instructions for building the website or you cannot tell which files are the latest version. Separate files intended for publication from internal documents, and keep instructions the next maintainer can understand.
Never store passwords or secret keys in website files visitors can download. If you use a code repository, set appropriate access permissions. Images and content published on a public website remain accessible to visitors in the usual way.
Match maintenance to how often information changes
A website with frequent price and article updates may need a different process from a service-introduction site that rarely changes. List what will be updated, who will do it and whether a preview is needed before publishing, so you can choose a sustainable way of working.
Before discussing the project on Fastwork, explain your later editing needs from the outset. We will confirm the handover inclusions, external services and additional maintenance according to the package. Receiving source code should not be taken to mean free maintenance forever.
Your next step
Before accepting a website handover, answer: “Where are the files, who controls the accounts, where do I edit, how do I publish a new version and how do I roll back?” Record any additional maintenance in the agreement so everyone understands the same scope.
