Draft Management
The Draft is the fundamental unit of Webround Sites. It represents the permanent development and staging environment where your project takes shape, going far beyond the capabilities of a simple visual editor.
Architecture and Philosophy
Architecturally, a draft is a collection of JSON schemas that describe every aspect of the site: layout, components, styles, and logic. This data is interpreted in real-time by the Webround Runtime (built on React + Vite).
This separation between configuration and runtime defines Webround's Open-Logic positioning: the draft is not a closed system, but a flexible framework that can be extended with proprietary logic while maintaining the advantages of a managed platform.
Key Features
- Isolation and Staging: Every draft is an autonomous and private entity. It serves as a secure staging environment where you can test configurations, code injections, or new Hooks without impacting the public version.
- Managed Infrastructure: Data persistence is handled by encrypted distributed storage. Webround manages the entire storage and permission pipeline, eliminating the need to configure databases or staging servers.
- Multi-tenancy: A single user can orchestrate multiple drafts, each with its own ecosystem of optimized media assets and specific configurations.
The Draft as an Extensibility Hub
The draft is the bridge between visual design and the freedom of custom development. It represents the integration point for three extension pathways:
1. Custom React Components (Front-end)
You can inject custom React code directly into the draft. Through the package.json file, you can install npm dependencies and compile components that become an integral part of the runtime. Thanks to Web Components, your logic is isolated: Webround platform updates will never interfere with your custom code.
2. Headless Commerce Integration
The draft is the native presentation layer for the Store. Although the Store is an independent headless entity, the draft is pre-configured to query its APIs, manage carts, and synchronize the e-commerce store state via the Webround SDK.
3. Transactional Logic and Middleware
The draft serves as the configuration center for critical services:
- Transactional Emails: Definition of flows for registration, welcome messages, and system notifications.
- Edge Routing: It is the starting point for applying Hooks, allowing the execution of server-side logic (Edge) before the page is served to the end user.
Lifecycle and Deployment
The transition from a private project to a public site follows a controlled flow:
- Drafting: Iterative modification and saving to the private cloud.
- Validation: Integrity check of JSON schemas and custom components.
- Edge Build: Upon publication, the system generates optimized assets and distributes them across the Webround Edge Network (CDN).
- Live: The site becomes accessible on a custom domain upon activation of a valid subscription.
Next Steps
Discover how to transform your design into an advanced sales system: