Normalize
Resolve one authoritative project brief.
▤ OMEGA WEB PRO DOCUMENTATION • GENERATION PIPELINE
From Website Specification to Validated Preview and Licensed ZIP.
Omega uses a staged production pipeline so larger websites do not depend on one oversized request. This guide documents how the authoritative specification moves through planning, media processing, page generation, platform rendering, quality validation, preview publication and export.
Checkpointed stagesChunked page generationResponsive media processingPlatform-specific renderersQuality gatesPreview health gateRecovery + retry
SPECIFICATION • PIPELINE • VALIDATION • PREVIEW • EXPORT
OMEGA GENERATION PIPELINE● CURRENT PLATFORM REFERENCE
DocumentationStagesWorkspaceMediaPage BatchesRenderersQuality GatesPreview GateExport
✓ Checkpointed workflow✓ Platform isolated✓ Preview health verified
Pipeline overview
Generation is a sequence of controlled stages.
Exact internal implementation can evolve, but the architectural responsibilities remain separated.
Plan
Run optional AI-assisted planning and validate the plan.
Initialize
Create temporary private workspace and shared build state.
Media
Validate/upload media and generate responsive assets.
Pages
Generate requested pages in controlled batches.
Finalize
Create site-wide assets/support files and resolve links/placeholders.
Validate + Preview
Run quality/platform checks and publish the isolated temporary preview.
Licence + Export
After purchase/licence checks, package the authoritative project for download.
Private build workspace
Temporary generation files belong outside the ordinary public website directory.
The build workspace is infrastructure, not the finished public site.
Private workspace
Generated working files and internal state are kept away from ordinary public browsing where the hosting environment permits.
Temporary by design
Workspaces and previews are temporary; the durable deliverable is the downloaded licensed website ZIP.
Project identity
Build/session/project identifiers keep concurrent project state isolated.
Image stage
Images are processed before they are integrated into generated pages.
The current image architecture prioritizes responsive production output and avoids unnecessary enlargement of smaller source images.
Production formats
AVIF, WebP, JPEG and PNG responsive families are used where supported/appropriate.
No-upscale behavior
Requested derivative widths are capped when the original source is smaller.
Favicons
Logo processing can create favicon and multi-resolution ICO/icon families.
Integration
Generated pages use responsive picture/srcset-style delivery rather than one oversized image everywhere.
Page generation
Large architectures are generated progressively.
The current build limit is 120 generated pages, including repeated individual pages created from structured lists.
Page types
Built-in and custom architecture feeds the page generator.
Repeated systems
Services, locations, products, case studies, team members and articles can add individual pages.
Chunking
Page batches reduce long single-request pressure.
Continuation recovery
Temporary continuation failures can be retried instead of automatically discarding the whole project.
Platform fork
Pure HTML and WordPress branch into separate production logic.
Omega does not generate one package and simply rename files to simulate another platform.
Pure HTML
Semantic HTML, CSS, vanilla JavaScript, responsive media and supporting crawl/deployment files.
WordPress
Dedicated renderer/validator, native theme architecture, generated content and setup/import mechanisms.
Validation
Generated output passes specialist readiness and platform checks.
Build-time checks are designed to detect structural problems before delivery, not to impersonate deployed runtime measurements.
SEO + schema
Metadata, canonical, H1, Open Graph, JSON-LD, sitemap/robots/llms and indexing behavior.
Accessibility
Landmarks, headings, image alternatives, skip links and accessible names.
Performance
Asset locality, payload discipline, image dimensions, CSS integrity and responsive media.
Security
Unsafe patterns, external script/target concerns, required hardening and project boundaries.
WordPress validation
Required directories/files, theme.json, generated content, slugs, placeholder/link conversion, installer/setup and WordPress-native behavior.
Preview publication
The generated project is published to an isolated temporary preview and must load its real assets.
The preview is not a screenshot. It is a delivery layer for the generated site.
CSS health
Required generated stylesheet must load.
JavaScript health
Required generated site JavaScript must load.
Image health
Generated images must be deliverable.
Responsive inspection
Desktop, tablet and mobile preview controls expose layout issues before purchase/deployment.
Authoritative deliverable
Export packages the generated project—not a browser-captured copy.
After the applicable preview, payment and licence gates, Omega creates the platform-specific licensed ZIP from authoritative project files.
Pure HTML ZIP
Portable website source for compatible hosting.
WordPress package
Theme, content/setup material and WordPress installation deliverables.
Licensed export
Permanent Account/Licence/Website/domain identity is verified before protected licensed export.
Omega Web Pro documentation
The pipeline is designed to be inspectable, staged and recoverable.
Use How It Works for the customer-facing lifecycle, or open Builder to see the pipeline operate on a real project.