Authentication
The customer must be signed in to the purchase-created account.
▤ OMEGA WEB PRO DOCUMENTATION • PRIVATE WEBSITE EDITOR
Edit the Licensed Source Code with Real-Time Preview and Validation.
Website Editor is the private source-editing environment for active purchased Website IDs. It loads authorized project files, provides editor tools, validates current changes, mirrors safe edits into a sandboxed responsive preview, creates versioned saves and can generate an updated signed licensed ZIP after whole-project validation.
Paid customers onlyLicensed Website IDs onlyDirect source editing2nd live preview14 validation responsibilitiesVersion historyUpdated licensed ZIP
LICENSED CODE EDITOR • LIVE PREVIEW • VALIDATE • VERSION • EXPORT
WEBSITE EDITOR● CURRENT PLATFORM REFERENCE
DocumentationAccessInterfaceLive PreviewLive ValidationSyntax + SafetySave + VersionsDomain ProtectionPHP BoundaryValidate + Export
✓ 14/14 validation responsibilities✓ Canonical host protected✓ Sandboxed preview
Access boundary
Website Editor opens from the purchased customer's licensed website record.
It is not a public arbitrary-upload IDE.
Website ownership
The selected Website ID must belong to that account and have an active licensed-domain relationship.
Project scope
Only the authorized licensed project workspace/file set is exposed through the editor.
Editor interface
The editor is designed for direct supported-file work, not just visual settings.
The current interface includes project/file selection, full-file editing and common text-editor controls.
Project + file navigation
Choose the purchased website, then choose an authorized file from that project's sidebar.
Line-aware editor
Loaded file content is shown with line/cursor awareness.
Undo + Redo
Reverse or restore local editing actions.
Find + Replace
Find Next, Replace and Replace All support controlled source editing.
Second preview workflow
Valid edits can appear in the sandboxed responsive preview beneath the editor.
This is distinct from Builder preview because it is driven by the currently edited licensed project source.
Desktop
Inspect full-width changes.
Tablet
Inspect intermediate responsive behavior.
Mobile
Inspect narrow-screen behavior.
Refresh / full screen
Refresh the preview and use larger inspection when needed.
14-responsibility gate
Newly introduced blocking issues can stop Preview and Save until corrected.
The live validator maps detected issues to the responsible production area and, where available, the exact line.
Website Specification
Checks project/specification consistency.
Brief Normalizer
Checks normalized project assumptions.
AI Planning
Checks planning-boundary expectations.
Plan Validation
Checks validated plan consistency.
Site Architecture
Checks document/page structural expectations.
Content Conversion
Checks transformed content data.
Design System
Checks styling/design structure.
Image Engine
Checks image-related project output.
SEO + Schema
Checks SEO data, JSON-LD and canonical rules.
Accessibility
Checks structural accessibility expectations.
Forms + Backend
Checks forms/server integration patterns.
Deployment
Checks deployable path/output expectations.
Quality / Metrics
Checks quality/readiness expectations.
Final Validation
Final combined gate before accepted operations.
Blocking examples
The editor checks more than one language family.
Validation can stop newly introduced invalid or unsafe content from moving into preview/save.
HTML structure
Malformed/invalid document structure can be detected.
CSS structure
Structural CSS issues are checked.
JavaScript
JavaScript structure is checked.
JSON + JSON-LD
Malformed JSON data and structured data can be rejected.
XML
Malformed XML can be rejected.
Data safety
Malformed UTF-8 and NUL-byte data are blocking conditions.
Security patterns
Detected unsafe executable/exfiltration-style patterns can be blocked.
Canonical host
Attempts to change the protected home-page canonical host to another domain are rejected.
Accepted changes
Save is revalidated server-side and accepted saves create version history.
Client-side live validation improves feedback; server-side checks remain authoritative.
Server-side revalidation
An edit that appears acceptable in the browser still passes authoritative backend checks before persistence.
Version history
Accepted saves create versioned revisions so the customer can inspect or restore prior states according to the editor controls.
Unsafe change rejected
A blocking issue does not become a saved project revision simply because a browser request was submitted.
Permanent licence identity
The root licensed domain is permanent; internal page paths can evolve.
This protects the commercial licence identity without freezing every filename forever.
Home canonical host locked
The home-page canonical host must remain the permanently licensed normalized domain.
Internal page changes allowed
A customer can legitimately rename an internal page and update its canonical path as long as it remains under the licensed host.
Export recheck
Canonical/licence identity is checked again before updated ZIP generation.
Sandbox behavior
Customer-edited PHP is not executed by the Website Editor preview.
The preview is intentionally not an arbitrary server-side code execution environment.
PHP editing vs execution
A supported project file may be edited where the project workflow permits it, but customer-edited PHP is not executed inside the live preview.
Sandboxed iframe
Preview script execution is constrained by the preview sandbox rather than receiving unrestricted application privileges.
Omega application protected
Customer editing is scoped to the licensed project and is not permission to edit Omega Web Pro's own application source.
Project-level delivery
Validate the whole licensed website before generating the updated ZIP.
The open file is only one part of the project.
Validate Licensed Website
Run broader project validation after completing edits.
Generate Updated Licensed ZIP
Package the current accepted project as a signed licensed export.
Regenerate instead
If the change is easier at specification level, return to Builder and regenerate the same licensed domain instead.
Omega Web Pro documentation
Use Website Editor when you want direct control of the licensed source.
Sign in to My Account, choose the licensed website and open Edit Website Code. Use Builder instead when the change is better expressed as a new website specification.