▤ OMEGA WEB PRO DOCUMENTATION • ZIP EXPORT & DEPLOYMENT

Move from Generated Project to Staging and Production with Omega Web Pro Hosting.

Omega generates and packages the website; the customer's hosting environment serves it publicly. This guide explains the handoff from licensed export to Pure HTML or WordPress deployment and the checks that should happen after the final URL is live.

Documentation Hub → Documentation Hub Customer Support

Authoritative project ZIPOmega Web Pro Hosting + portable lifetime exportPure HTML deploymentWordPress package installationDNS + HTTPSPost-deployment testingIndependent backups

EXPORT • UPLOAD / INSTALL • DNS • HTTPS • TEST • BACKUP

DEPLOYMENT CHECKLIST● CURRENT PLATFORM REFERENCE

DocumentationBefore DeployPure HTMLWordPressDNS + HTTPSFormsTest ProductionBackupsOwnership Boundary

✓ Package validated✓ Hosting configured✓ Production URL tested

Omega Hosting • two dedicated, protected website editors

Separate editing workspaces for Pure HTML and native WordPress websites.

Omega uses the verified website's hosting record, platform and authorised Website ID to select its editor. The Pure HTML and WordPress tools are separate OVHcloud pages, not two modes of the older combined website-editor.php. Sign in through My Account and select your purchased website; do not choose a platform by changing the URL.

Pure HTML Website Editor

dashboard.omegawebpro.com/website-editor.php

Work with the site's authorised HTML, CSS, JavaScript and supporting project files. Use the code editor with Save, Undo, Redo, Find and Replace, a desktop/tablet/mobile sandbox preview, validation, version history, updated licensed ZIP export, Builder-source adoption and guarded Deploy / Update Live Website.

The selected Pure HTML site can also access its eight applicable Omega hosted Website Plugin implementations and compatible third-party HTML add-ons through the editor's website-specific plugin panels. The embedded Omega AI Agent assists with code, validation explanations and reviewable proposed fixes; customers approve and save changes themselves.

Native WordPress Website Editor

dashboard.omegawebpro.com/website-editor-wordpress.php

Work with native WordPress Pages and Posts, their HTML/block content and responsive WordPress preview, plus the integrated WordPress Manager for supported site administration. WordPress engine dashboards, the installed-plugin repository and one-at-a-time plugin administration workspace operate within the authorised editor.

Builder-generated WordPress theme/content changes, validation and live publication follow the WordPress-specific staging and deployment process—not the Pure HTML static-file editor. Saved WordPress database content and a published WordPress theme are distinct operations. The Omega AI Agent is also embedded here for page/code guidance, validation help and controlled, reviewable repair suggestions.

Both editors retain customer/Website ID checks and protected workflows. Each paid Omega Hosting purchase covers one website; only the eight engines appropriate to that website's detected platform apply. Both pages include the floating bottom-right Omega AI Agent for public web research with sources, NativeAI knowledge and planning, six-stage Builder guidance, code explanations, error/log review, website-scoped validation help and staged repair proposals. Customer-specific account, hosting and source assistance require a verified session and authorised Editor context; suggested changes require explicit review, saving and validation before publication, never silent live edits. Lifetime licence editing and licensed ZIP rights are separate from the paid hosting entitlement required to deploy. Hosting, editing, staging and publication remain subject to the selected site's permissions, entitlements and validation checks.

New: lifetime-licensed WordPress editing without Omega Hosting

Private WordPress Website Editor — for WordPress lifetime licence holders without Omega Hosting

A customer who owns a lifetime licence for a WordPress website but does not have active Omega Hosting for that same Website ID uses the dedicated Private WordPress Website Editor. Sign in, select your authorised website in the customer Dashboard, and use its Edit Website action. This is a private project workspace, not a hosted WordPress installation.

The licence-only WordPress route provides private file and page/post editing, package preview, Builder re-generation hand-off, offline validation, version checkpoints, downloadable WordPress ZIPs and five private package diagnostic dashboards. It does not provision WordPress hosting or activate the hosted plugin services.

Three distinct editing paths: website-editor.php is the Pure HTML Editor; website-editor-wordpress.php is for an authorised WordPress website with eligible active, provisioned Omega Hosting (including lifetime-licensed customers who also have that hosting); website-editor-wordpress-private.php is for lifetime-licensed WordPress customers without active Omega Hosting for that website. The Dashboard determines the correct editor from the website's platform and entitlements.

Hosting boundary: a lifetime licence allows the private WordPress project to be edited and its ZIP exported without buying Omega Hosting. It does not include live hosting, public deployment, live WordPress administration, live plugin execution, visitor-traffic metrics or server-side WordPress PHP rendering. Publishing to Omega Hosting requires a separate, eligible hosting entitlement for that same website.

Open your customer Dashboard to select the licensed website. The authorised private workspace is Private WordPress Website Editor (website selection and sign-in required).

Before upload

Confirm you have the correct authoritative licensed package.

Do not deploy from a temporary preview cache or partial browser download.

ZIP

Correct licensed ZIP

Use the package generated by the completed Omega workflow.

🌐

Correct domain

Deploy the project to the domain covered by the licence.

BACKUP

Backup existing site

If replacing an existing production site, create a recoverable backup first.

HOST

Hosting compatibility

Confirm the host supports the selected platform and any optional server-side features.

Pure HTML deployment

Place generated files in the intended document root.

One of the most common deployment mistakes is leaving the actual website inside an extra wrapper directory.

ROOT

Document root

Place index.html and its related directories/files at the web root intended for the domain/subdomain.

644

File permissions

Typical public-site files use 644 and folders 755 unless the host requires otherwise.

PHP

Optional backend

If generated PHP form handling is used, confirm PHP availability and private configuration paths.

🔒

Private files

Private configuration/storage should remain outside public_html where the hosting setup permits and use tighter permissions such as 640 files / 750 directories where appropriate.

WordPress deployment

Use the generated WordPress theme, content and setup/import material together.

The WordPress deliverable is more than a skin.

WordPress environment

Start with a compatible WordPress installation and server runtime.

THEME

Theme package

Install/activate the uniquely generated Omega theme.

SETUP

Setup/import

Use the generated setup/installer material to create/update generated pages/content according to the package instructions.

WXR

Content package

Generated JSON/WXR/build-report/instruction files support installation and verification.

Public routing

Point the intended domain to the correct hosting and enforce HTTPS appropriately.

Domain registration and DNS are customer responsibilities unless separately supplied.

DNS

Configure A/AAAA/CNAME records according to the hosting provider.

SSL

TLS certificate

Issue/install a valid certificate for the production hostname.

↗

Redirects

Choose one canonical host/protocol and configure redirects consistently.

CAN

Canonicals

Confirm generated canonical URLs match the final licensed production host/path.

Server features

Configure operational services the static ZIP cannot supply by itself.

Examples include authenticated mail, analytics accounts, external checkout links and other third-party services.

SMTP

Pure HTML forms

Configure authenticated SMTP privately and test the deployed endpoint.

WordPress forms

Confirm WordPress mail and generated native form hooks operate in production.

Analytics

Add/configure the customer's chosen analytics provider if required.

Third-party links

Verify booking, checkout, maps, social and other external services use correct production URLs.

After deployment

Test the actual live URL—not only the local files.

Hosting, CDN, DNS and browser runtime can reveal issues that did not exist in the build workspace.

NAV

Navigation

Check menus, internal links, anchors, search and 404 behavior.

FORM

Forms

Submit every important form and confirm real delivery/validation.

▯

Responsive

Test multiple real viewport sizes and devices.

SEO

Search files

Check robots.txt, sitemap.xml, canonicals, JSON-LD and noindex rules.

CWV

Performance

Run Lighthouse/PageSpeed and observe Core Web Vitals with appropriate browser/field tools.

♿

Accessibility

Perform browser/tool/manual accessibility review.

◆

Security

Check HTTPS, headers, server configuration, dependencies and platform update posture.

LOG

Errors

Review browser/server logs for 404s, PHP errors, blocked assets and console issues.

Ongoing operations

Keep the generated ZIP and production backups independently.

A downloadable project package is not a substitute for operational backups of the deployed site/database.

ZIP

Keep Omega ZIP

Store the latest licensed export safely.

HOST

Hosting backup

Back up deployed files and configuration.

WordPress database

Back up the WordPress database separately where applicable.

↻

Before changes

Create a restore point before major plugin/theme/server/DNS changes.

What Omega does and does not host

Lifetime-licensed exported sites can run on compatible customer-selected hosting; recurring hosted plans use Omega Web Pro Hosting while active.

The customer controls the deployment environment after export.

OWN

Portable files

Lifetime-licensed Pure HTML remains portable and can run independently on compatible hosting; recurring plans can deploy through Omega Web Pro Hosting.

WordPress portability

WordPress packages can be installed/migrated within normal WordPress hosting constraints.

SUP

Support scope

Omega support can help with generated-project/licence issues; the customer's chosen host remains responsible for its infrastructure.

Omega Web Pro documentation

Deployment is where build-time readiness becomes real-world performance.

Use the checklist on the final URL and keep both the licensed Omega ZIP and independent production backups.

Documentation Hub →All Documentation

OMEGA WEB PRO HOSTING

Omega Web Pro Hosting deployment workflow

Recurring plans use the managed Omega Web Pro Hosting lifecycle: generated project → preview → hosting workspace → staging → production. The authenticated Omega Hosting Dashboard provides customer controls for project workspaces, deployments, backups, databases, SFTP and usage, while My Account reports the purchased website, entitlement and customer-facing DNS/SSL connection state.

Customer control plane

The US$999 lifetime licence remains portable. A lifetime customer may use Omega Web Pro Hosting separately or export the licensed project to compatible customer-selected hosting. Production DNS, HTTPS, forms, redirects and final testing still need verification on the live URL.

Managed hosting plans

Monthly US$9.99 · Annual US$99 · Two Years US$179. Managed Omega Web Pro Hosting remains available while the recurring plan is active.

∞

Lifetime software licence

US$999 one time for permanent supported build, edit and export rights for one licensed website domain. Production hosting is separate and can be added when required.

OMEGA HOSTING • PRODUCTION WORKFLOW

From Hosting Purchase to Live Website

Omega Hosting is an optional recurring service for one hosted website and is separate from the US$999 Lifetime Single Website Domain Licence. A hosting purchase is associated with the authenticated Omega customer account and the exact Website ID, domain, project and platform selected for that website.

Purchase + provision

After a Monthly, Annual or Two-Year Omega Hosting purchase is confirmed, Omega provisions the generated website into its assigned hosting environment. The hosted website then appears in the customer's authenticated My Account and Full Hosting Dashboard.

Hosting Setup Email + DNS

Omega supplies the required DNS instructions in the Hosting Setup Email and through authenticated hosting controls. The customer applies those records with the authoritative DNS/domain provider. Existing nameservers may remain in use unless the supplied instructions specifically require otherwise.

Verification + SSL

Provisioning or file upload alone does not make the public domain live. Omega verifies the public DNS connection; once the domain resolves correctly, SSL/TLS activation and certificate automation can proceed. The domain then resolves to the Omega-hosted production website.

Edit + update the live website

An active Omega Hosting customer can open the hosted project through My Account / Full Hosting Dashboard, work in Builder and/or Website Editor / Code Editor, save the project, then use Deploy / Update Live Website to update the existing production website.

Protected deployment

Before production activation, Omega verifies the authenticated account, Website ID, hosting entitlement, hosting allocation and permanent project source. Deployment uses validated project source, private staging, a pre-deployment restore point, production activation and post-deployment validation. If activation fails after the live site changes, Omega attempts automatic rollback.

Ongoing hosting controls

The Full Hosting Dashboard provides customer-facing access to deployments and deployment history, Domains & SSL, backups and restore points, databases, SFTP/access status, resources and usage, security status, billing and subscriptions, lifetime licences, activity/audit, support and account/privacy controls.

DNS responsibility: use the exact DNS records supplied for your website. Do not copy an IP address or DNS value from another customer's setup. Where available, My Account can resend the Hosting Setup Email. Domain registration is separate unless explicitly supplied, and correct DNS configuration and propagation are required before the public domain and SSL can become active.

WordPress • Omega-hosted updates

Save native WordPress content and deploy website source as separate protected actions.

For active, provisioned Omega-hosted WordPress sites, customers open Website Editor from My Account, select the verified WordPress Website ID and work inside a secured, site-scoped session. The separate WordPress account setup email provides optional direct WordPress administrator credentials; it is not a prerequisite for supported embedded WordPress operations.

WordPress server setup is not the same as WordPress website publishing. For eligible provisioned WordPress hosting, Omega’s background lifecycle prepares site-specific WordPress core, database and owner identity, preserving an already installed WordPress site. That foundation enables WordPress Management and the onboarding invitation. Your generated theme/content, live page/post saves, domain DNS/SSL connection and any protected theme deployment each have their own explicit completion and validation conditions. Do not assume that a successful WordPress installation has published a generated theme.

Live WordPress document save

Use WordPress Source Code — Pages & Posts to load a real WordPress document, edit its HTML/block markup and explicitly Save to WordPress. The change is saved to the live WordPress database under the guarded WordPress Manager service with revision history. Confirm the result using Live WordPress Preview.

Native website deployment

Deploy / Update Live Website stays within Website Editor but invokes a separate protected publication path with authenticated Website ID, hosting, platform, canonical domain and source checks. The Pure HTML code and sandbox workflow belongs to website-editor.php, not the separate native website-editor-wordpress.php page. WordPress source/content saves and guarded WordPress theme deployment remain distinct.

Good practice: verify the target website before making changes and maintain appropriate WordPress files/database backups before theme or production deployment. Live WordPress content saves and full-site rollouts should be checked independently.

CURRENT PRODUCTION WORKFLOW

Live-site update controls

Deploy / Update Live Website is for an existing active, provisioned Omega-hosted production website. The customer first saves the latest Builder and/or Website Editor project, then selects the eligible hosted website in the Full Hosting Dashboard. Omega verifies the authenticated account, full Website ID, hosting entitlement/allocation and permanent project source before production replacement.

The customer can also see deployment history for their own eligible websites, including successful or attempted deployments and associated restore points. Public documentation describes this protection model without exposing raw server paths, infrastructure identifiers or privileged deployment errors.