Short answers to the questions behind the workflow.

Yes, the visual workflow can be used without writing code while the page is being composed. The difference is the intended handoff: Windblocks is designed to produce a structured source project that developers can continue editing normally.

Not to arrange the initial project visually. React and TypeScript knowledge becomes useful once you export the project and continue application-specific development outside the builder.

The editing canvas includes builder controls and editing constraints. Preview uses an isolated viewport with a real width, allowing CSS and Tailwind breakpoints to be evaluated much closer to the generated application.

The visual structure can still be generated, but the exporter has less information about event contracts and client boundaries. Mapping actions prepares cleaner callback wiring without inventing your business logic.

Yes. Project components can be composed from HTML containers, made reusable and configured with shared appearance, defaults and export behaviour.

The current file manager accepts JPG, JPEG and PNG source images. The backend processes them into optimized WebP assets for the project workflow.

It remains useful as an editable backup and transfer format. It can be downloaded and imported later, while generated application source remains the primary developer handoff.

The account area includes profile and security management, active-session controls and account deletion. Account operations belong to the account area rather than the visual builder itself.