Generated Site Quality
Public quality requirements for Qokit generated sites regarding content, structure, CTAs, responsiveness, and maintainability.
Generated Site Quality
Qokit generated sites allow industry-specific themes, but outputs must maintain structural integrity, readable content, clear CTAs, reliable responsiveness, and pass existing rendering contracts.
Structural Requirements
- Pages are generated from structured Blocks, content mappings, and theme variables;
- Avoid using hard-to-check and maintain free-form HTML as a replacement for existing Schemas;
- Hero, features, trust signals, FAQ, CTA, and Footer are combined according to page goals;
- New Blocks are added only for stable business semantics, SEO, forms, or CMS bindings.
Content Requirements
- The first screen explains business value and primary actions;
- Each page has a clear purpose, avoiding vague placeholder copy;
- CTA copy directly states the result;
- Images match the industry, brand, and current content, and provide alt text;
- Pages do not rely on critical actions visible only on hover.
Responsiveness & Publishing
- Desktop, tablet, and mobile are independently checkable states;
- Text, media, tables, and action groups naturally reflow on narrow screens;
- Check links, forms, SEO, images, languages, and unsaved changes before publishing;
- Generated results continue to output through the structured contracts of PageRenderer and BlockRenderer.
Integrator Checklist
- Real content is readable and has no horizontal overflow;
- The page has only one clear primary CTA;
- Theme overrides do not break token semantics;
- Forms, links, and keyboard focus are usable;
- Content, Schema, and rendering results can be debugged and rolled back.