porchBEFORE THE FIRST PAGE
What is the difference between website design, deployment and maintenance?
Website design shapes the pages and how people use them. Deployment publishes the agreed website to a hosting service and connects the domain where included. Maintenance is the ongoing work after launch. Agree on each part separately so responsibilities, access and costs are clear.
Design: agree what will be made
Design starts with the business information and the actions visitors need to take. A written scope turns an idea into a reviewable set of pages and deliverables.
- List the pages, content, languages and mobile layouts included in the project.
- Clarify who supplies and approves text, menus, photos and other materials.
- Distinguish links to existing services from embedded tools, integrations and custom software.
- Record the review process, revision rounds, fees, timing and final deliverables.
Deployment: agree how it will become a live website
A domain is the website address. Hosting serves the website files or application. Deployment puts the agreed build onto that hosting setup; it can also include connecting the domain and checking the live result.
- Decide whether deployment is included or whether you will use another provider.
- Identify the domain registrar, hosting provider and the accounts needed for the agreed setup.
- Agree who handles domain settings, HTTPS and live checks, and what access is required.
- Clarify recurring charges and renewal responsibilities. Domain email is a separate item to discuss, not an automatic part of publishing a website.
Maintenance: agree what happens after launch
A published website still needs accurate information. Ongoing work varies with how it is built and which outside services it uses.
- Identify who changes menus, prices, hours, photos and contact information.
- For software-based sites, clarify who handles relevant software updates and security maintenance.
- Discuss backups, recovery, broken links and checks on external ordering or booking tools where needed.
- Agree what support covers, how requests are made, any response expectations and separate charges.
- Confirm who watches hosting and domain renewals, and what happens if the maintenance arrangement ends.
Before signing: make the handover concrete
An existing domain or platform may be usable, but compatibility and access need checking before a migration or replacement is promised.
- List the existing domain, website, email and ordering or booking services that must keep working.
- Write down account ownership, permissions, renewal responsibility and the agreed method for granting access.
- Specify the source files, published files, content and documentation to be delivered; do not assume every project includes the same handover.
- Agree how the live site will be reviewed, how issues will be handled and what counts as completion.
- Record any ongoing arrangement separately, including how to move to another provider. Do not send passwords in a project inquiry.
A few practical questions.
Is deployment included with Porch & Paige website design?
Monthly plans include hosting, HTTPS and launch checks. One-time projects confirm deployment and recurring costs separately in writing. Existing accounts and any migration need review first.
Can I keep my current domain and hosting?
Share the current setup so it can be reviewed. Keeping or moving services depends on compatibility, access and the agreed scope; a migration is not promised before that review.
Does launching a website include ongoing maintenance?
Ongoing maintenance is not automatic. Content updates, technical care, support expectations and fees need an explicit written agreement.
Put the plan into practice.
Websites for restaurants, cafés and other small businesses in North America. Choose a monthly plan with hosting or a clearly scoped one-time project.
What should a small restaurant website include?