WordPress should feel like a dedicated product lane with tailored flows, not a thin skin over generic VPS content.
Current product direction
Techservice currently treats WordPress as two backend modes:
- A legacy server-backed path that still follows the older managed server model
- A dedicated 20i package-backed path for managed WordPress hosting
The production direction is the 20i lane, where a managed hosting package is provisioned through the reseller API instead of through a VPS bootstrap sequence.
What the WordPress lane should expose
| Surface | What users should understand |
|---|---|
| Plan selection | Which managed WordPress package fits the site workload |
| Provisioning state | Whether package creation, access verification, or follow-up review is pending |
| Site overview | Domain, package, hosting type, WordPress state, and support path |
| Support and migration | How to request help for launch, migration, or access problems |
Status expectations
The WordPress lane follows its own product-specific statuses, such as:
- creating_package
- package_created
- wordpress_detected
- access_pending
- pending_approval
- active
The dashboard should not show a WordPress site as fully active until the managed delivery steps are actually complete.
Product rule
WordPress content should speak like a managed website product.
Avoid collapsing it back into raw server terminology when the customer is really buying a managed hosting package, onboarding support, and ongoing care.