▤ OMEGA WEB PRO DOCUMENTATION • WEBSITE SPECIFICATION

Define the Website First. Generate from One Authoritative Brief.

A strong Omega project starts by deciding what the website must be, who it serves, how it is structured, how it should look and what it must do. This guide explains the information that belongs in the website specification and how Omega resolves conflicting or incomplete inputs.

Create Website Specification → Documentation Hub Customer Support

Business facts firstAudience + market scope111 selectable page types6 repeatable systemsComplete design controls50,000-character briefExplicit choices authoritative

SPECIFICATION • ARCHITECTURE • CONTENT • DESIGN • PLATFORM

AUTHORITATIVE PROJECT BRIEF● CURRENT PLATFORM REFERENCE

DocumentationPrinciplesBusinessPage ArchitectureContentDesignMediaPlatformReview

✓ One source of truth✓ Explicit selections preserved✓ Auto resolves only gaps

Website editing after purchase

The correct editor depends on your hosted website platform.

Omega Hosting customers select their authorised purchased website in My Account. The dedicated Pure HTML Editor is dashboard.omegawebpro.com/website-editor.php; the dedicated native WordPress Editor is dashboard.omegawebpro.com/website-editor-wordpress.php. HTML file editing and sandbox preview remain separate from live WordPress Pages/Posts editing and the integrated WordPress Manager. Each editor has its own applicable Omega hosted plugins and optional third-party plugin tools, with website-scoped validation and guarded publication. Omega AI Agent is embedded in both editor pages to help explain code, suggest fixes and assist with validation; proposed changes require customer review and an explicit save. Explore Omega AI Agent functions.

Specification principles

Separate facts, requirements, preferences and optional Auto decisions.

This distinction prevents generated content from treating a guess as a business fact.

FACT

Business facts

Legal/business name, services, products, locations, contact information, operating areas and claims you can substantiate.

REQ

Requirements

Pages that must exist, required functions, regulatory disclosures, platform target, supported languages/regions and deployment constraints.

PREF

Preferences

Visual style, typography, imagery, tone, hero treatment, cards, buttons, spacing and motion.

AUTO

Auto choices

Areas the planning system may resolve when you deliberately leave them open.

Business + market

Give Omega enough real context to write and structure the website responsibly.

Generated text cannot invent accurate private business facts that were never provided.

🏢

Identity

Business/organization name, trading name, purpose, industry, sub-industry and business model.

🌍

Markets

Countries, regions, cities, service areas, local/national/international scope and regional language conventions.

👥

Audiences

Primary and secondary customer/user groups, knowledge level, buying context and trust concerns.

🎯

Goals

Lead generation, ecommerce, bookings, education, information, support, portfolio, recruitment or another measurable purpose.

Architecture

Choose the information architecture deliberately.

Page count should follow user needs and project scope rather than an arbitrary template count.

111

Selectable page types

Use the 111-page-type catalogue to select the public pages the project needs.

Repeatable page families

Use structured service, location, product, case study, team and article lists when individual pages are valuable.

Custom pages

Add project-specific page requirements not represented by a built-in page type.

120

Current maximum

The generated total must stay within the current 120-page build limit.

Content direction

Define voice, terminology, factual boundaries and calls to action.

AI-assisted writing is stronger when the brief defines what may be said and what must not be fabricated.

Voice + tone

Professional, technical, friendly, luxury, editorial, direct, educational or another appropriate voice.

TERM

Terminology

Preferred service names, capitalization, product language, regional spelling and terms to avoid.

PROOF

Claims + evidence

Supply the facts behind credentials, guarantees, statistics, awards, experience, locations and commercial claims.

CTA

Conversion strategy

Define the main action: contact, quote, book, buy, call, visit, apply, subscribe, download or another conversion.

Design requirements

Translate brand intent into explicit design controls.

Use a blueprint as a starting direction, then override component systems where the brand requires it.

🎨

Colour + theme

Brand colours, light/dark/auto mode and contrast expectations.

Typography

Heading/body font direction, text scale and readability.

☰

Navigation

Header architecture, navigation treatment, mobile menu and hierarchy.

Hero + sections

Hero type/height, section rhythm, background systems and content width.

▣

Cards + media

Card treatment, image shape, gallery layout and visual density.

Buttons + motion

CTA hierarchy, button style and motion level.

Images + supporting material

Provide source media at the highest useful quality you control.

Omega can generate responsive derivatives but should not be expected to invent missing originals or improve a tiny source beyond its actual information.

LOGO

Logo

Upload the official logo that should identify the generated site.

IMG

Supporting images

Use relevant owned/licensed imagery and provide guidance about where it belongs.

↘

No unnecessary upscale

Responsive derivative generation caps widths to the source image when appropriate.

ZIP

Supporting documents

Use controlled text/markup/ZIP inputs to provide context that belongs alongside—not above—the Builder specification.

Production target

Specify platform requirements before generation.

Pure HTML and WordPress have different runtime, form, installation and maintenance assumptions.

</>

Choose Pure HTML when

You want a CMS-free portable website using ordinary HTML/CSS/JavaScript and compatible hosting.

Choose WordPress when

You need a native WordPress project, theme architecture, WordPress content/editing features and WordPress-specific runtime behavior.

Human review

Review the specification before generation and review the generated site before publication.

Automation does not transfer responsibility for business accuracy, legal compliance or deployment suitability.

✓

Before Generate

Check domain, business facts, pages, repeated lists, design direction, image rights and platform selection.

✓

Before Purchase

Use Builder preview to check layout, navigation, imagery and obvious content issues.

✓

Before Publish

Check live forms, legal text, prices, claims, accessibility, SEO, analytics/cookies and industry-specific obligations.

Omega Web Pro documentation

A better website starts with a better specification.

Open Builder and define the business, architecture, design and platform requirements before asking Omega to generate.

Create Website Specification →All Documentation

OMEGA WEB PRO HOSTING

Specify with the deployment target in mind

The website specification should capture requirements that affect the eventual runtime environment—forms, PHP needs, WordPress, databases, upload requirements and operational integrations.

Customer control plane

For recurring plans, Omega Web Pro Hosting becomes the managed runtime and control-panel environment. Lifetime-licensed projects remain portable and can instead be exported for compatible customer-selected hosting.

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.

Current production customer architecture

Build, purchase, billing, hosting and editing continue through one authenticated Omega customer relationship.

For a first-time Omega Hosting checkout, Omega saves the selected plan and pending website to one restricted checkout-bound customer account before payment, sends a secure one-time account-setup email, and requires the customer to set a password and sign in before continuing to the required purchase acknowledgements and secure Stripe Checkout. Paid Hosting and Editor entitlement remain locked until Stripe confirms payment. For a first-time Lifetime Licence purchase, an existing account is reused where available, or the customer account is created after Stripe confirms the purchase. My Account is the commercial identity, website, licence and billing centre; recurring hosting customers can use the Full Hosting Dashboard while entitled; lifetime customers retain their separate same-domain software rights.

My Account

Purchased websites, subscription/renewal state, lifetime licences, Pending Checkout, Purchase History, profile/security, Builder and Website Editor entry points.

Billing Centre

Secure Stripe customer-portal access for the account's usable canonical production billing customer, including supported payment-recovery and subscription billing actions.

Billing documentation →

Omega Hosting Dashboard

Entitled operational hosting controls for project workspaces, provisioning, deployment, backups, databases, SFTP and usage, with customer-facing DNS/SSL state surfaced through Omega interfaces.

Hosting documentation →