ENGINEERING CASE STUDY / Web applications
WebBuilder AV
Build visually. Export a website you own.
Visit the project website Source repository
01 / THE PROBLEM
Problem & objectives
Make a portfolio visually while retaining editable local projects and exportable files that can be hosted independently.
A visual portfolio builder with drag-and-drop blocks, responsive editing, local project storage, and multi-page static HTML export. Available as a localhost editor and Windows/Android app.
02 / THE SYSTEM
Architecture & technology
A Vite client talks to a local Express API in browser mode. Tauri packages the editor for Windows and Android, using private IndexedDB storage and native save dialogs. A production renderer exports responsive HTML for each page.
- Blocks & visual editor
- Local project storage
- Multi-page HTML export
03 / THE BUILD
Implementation & key features
- Visual canvas, layers, property inspector, undo, and redo
- Eight starter templates and responsive editing views
- Independent pages with static HTML export
- Local project backups and Windows/Android packages
04 / THE BOUNDARIES
Security & reliability
Design notes and review considerations documented alongside this project:
- The local API binds to 127.0.0.1 by default
- Rich text is constrained rather than executed as arbitrary HTML
- Exported contact forms need a trusted delivery endpoint
05 / THE DECISIONS
Challenges & trade-offs
Editable project JSON and exported HTML serve different purposes; the exported site does not include the editor. The product website presents the app and downloads rather than hosting an editing service. Current native packages are previews.
06 / THE RESULT
Outcome & engineering takeaways
A local visual editor with portable project backups and static websites that need no Node.js runtime after export.
The engineering takeaway is to make the system’s capabilities and limits explicit. The repository documents the implementation and its current scope.
Read the project documentation