Template-owned structure
Header, footer, row width, region order, and row gap stay under template control.
CMS Reborn Static Prototype
Premium frontend first. CMS database later.
This static prototype proves the visual direction before we create dynamic CMS tables. It is designed for Kiradoo Systems, VastuEngine, and future client websites.
✓ No old CMS runtime
✓ No database dependency
✓ Preview before production
Built as a premium, frontend-first CMS foundation for serious client-facing websites.
Frontend first
visual approval before DB
Token based
controlled style system
Multi-tenant
future client ready
Frontend system
A page should feel designed, not assembled from random modules.
This direction uses template-owned spacing, controlled surfaces, adaptive blocks, and a consistent premium visual language.
Block-owned content
Blocks manage headings, text, images, buttons, pricing rows, FAQ rows, and tool cards.
Controlled design profiles
Surface, background, typography, color, motion, and hover use safe design tokens.
Utility gateway
Ready for VastuEngine tools without mixing tools into CMS content.
CMS blocks can introduce calculators, reports, and paid workflows. Actual calculations remain in engine modules.
Yoni calculator gateway
Public block launches the tool. Engine handles formula and report logic.
Pada grid analyzer gateway
CMS explains the feature. Application module performs the computation.
Report preview gateway
CMS sells the value. Payment and PDF download stay protected.
Commerce section
Pricing cards are allowed. Full-row card stacks are not.
Commerce blocks may use elevated cards, highlighted plans, and payment CTAs while the section remains clean.
Starter
₹0
Prototype review
- ✓ Static visual preview
- ✓ Mobile check
- ✓ Frontend feedback
CMS Reborn
Core
Foundation build
- ✓ Theme + template system
- ✓ Block profiles
- ✓ Preview approval gate
VastuEngine
Next
Tools and reports
- ✓ Tool gateway blocks
- ✓ Payment unlock flow
- ✓ PDF report delivery
Help section
FAQ should be soft, clear, and not overdesigned.
Help blocks should reduce doubt. They should not create visual clutter or heavy cards.
Is this dynamic CMS?
Not yet. This is the static premium frontend prototype before database and admin work.
Why static first?
Because the database should support approved frontend quality, not force design decisions.
Can future block types be added?
Yes. The blueprint uses global block families, not only fixed names like FAQ or pricing.
Approve the visual direction only after seeing it in the browser.
This is the first static frontend proof. If the direction is accepted, the next step is visual refinement, not database migration.
Mobile proof is part of approval. Do not approve only on desktop.