Project Overview
1. Overview
This project involves migrating the existing WordPress website to a new hosting environment on DigitalOcean, while ensuring minimal risk and no disruption to the current live site.
The approach prioritises stability, controlled cutover, and clear separation between development and production environments.
2. Project Scope
2.1 In Scope
-
Access and analysis of the existing WordPress site
-
Full backup of the current site (files and database)
-
New server setup on DigitalOcean
-
New WordPress installation and configuration
-
Content migration and restoration
-
Restoration of missing homepage background image
-
Addition and update of confirmed website content
-
Internal QA and review
-
DNS update and go-live once domain panel access is available
2.2 Out of Scope (unless later confirmed)
-
Major custom feature development
-
Content creation beyond agreed pages
3. Project Approach & Planning
The project follows a waterfall approach, with clear phases, dependencies, and approval points.
Phase 1: Discovery & Preparation
-
Obtain access to the current WordPress site
-
Analyse theme, plugins, and content structure
-
Perform a full site backup
Phase 2: New Environment Setup
-
Create a new hosting server on DigitalOcean
-
Install and configure a new WordPress instance
-
Access the site via server IP address prior to DNS cutover
Phase 3: Migration & Development
-
Restore or migrate content from the existing site
-
Re-add missing homepage background image
-
Apply required updates and fixes
-
Develop additional confirmed pages and content
Phase 4: QA & Internal Review
-
Functional testing
-
Content verification
-
Responsive and cross-device testing
-
Internal readiness confirmation
Phase 5: Go-Live (DNS Cutover)
-
Obtain domain panel (DNS) access from the client
-
Update DNS records to point the domain to the new server
-
Perform final live-site verification
4. Functional Specification
This section defines the expected website functionality from a non-technical perspective.
4.1 Language Support
-
The website will support:
-
English
-
Traditional Chinese
-
-
Language switching will be available across applicable pages.
4.2 Website Pages
Home Page
-
Display company introduction and key messaging
-
Restore and display the missing background image
-
Provide navigation to other pages
Products Page
-
Display product listings with specification descriptions
-
Content to be provided in both English and Chinese
-
Static display only, no purchasing functionality
Services Page
-
Display a list of services with descriptive text
-
Static informational content only
Projects Page (New)
-
A new “Projects” page will be added
-
Page structure, layout, and content are pending client confirmation
-
Language support assumed to be English and Traditional Chinese unless otherwise confirmed
About / Contact Page
-
Display company background and contact information
-
No advanced contact form or automation included unless later agreed
4.3 General Behaviour
-
The website will be responsive across desktop, tablet, and mobile devices
-
Content will be managed via WordPress CMS
-
Only confirmed content will be implemented to avoid rework
5. Technical Approach
5.1 Platform & Hosting
-
CMS: WordPress
-
Hosting Provider: DigitalOcean
-
A new, clean server environment will be used
5.2 Migration Strategy
-
Development and testing will be conducted using server IP access
-
The existing live site will remain unaffected during development
-
DNS changes will only occur after internal QA and client confirmation
5.3 Theme & Plugins
-
A selected WordPress theme will be installed and configured
-
Required plugins will be installed for:
-
Language support
-
Basic security
-
Performance and content management
-
-
No custom plugin development is included unless later agreed
5.4 Quality Assurance
-
Functional validation
-
Content accuracy checks
-
Cross-browser and cross-device testing
-
Sign-off prior to go-live
6. Dependencies & Client Responsibilities
The following items are required from the client and may impact the overall timeline:
-
Provision of domain panel (DNS) access (estimated 2–3 weeks)
-
Product specification descriptions in both English and Traditional Chinese
-
Confirmation of content and requirements for the new “Projects” page
Development and QA can proceed without these items; however, final go-live is dependent on domain access.
7. Assumptions & Constraints
7.1 Assumptions
-
The client will provide accurate and finalised content before go-live
-
Product descriptions will be provided in both required languages
-
Projects page requirements will be confirmed prior to implementation
-
Domain panel access will be provided once available
7.2 Constraints
-
DNS access is currently unavailable and outside project control
-
Go-live timing depends on DNS availability, not development progress
-
Budget and scope limit the level of customisation
-
Late content changes may impact timeline
7.3 Out-of-Control Factors
-
Delays caused by third-party domain providers or internal approval processes
-
Scope changes after confirmation
8. Acceptance Criteria
The project will be considered complete when:
-
All agreed pages are available and functional on the new server
-
Missing assets: the homepage background image, are restored
-
Internal QA is completed with no critical issues
-
Domain successfully points to the new server
-
Live-site verification is completed
No comments to display
No comments to display