Can I vibecode Cargo?

Build a highly creative, localized website builder tailored for artists and designers, acting as a personal replacement for Cargo. Leverage a modern technology stack: Next.js 15, TypeScript, Tailwind CSS, and a local SQLite database. You must vibe-code an interface that is visually striking, embracing brutalist or avant-garde modern web design trends while maintaining extreme usability. Think bold typography, unconventional grid layouts, fluid animations, and a distinctly premium feel.

Core Functionality & Constraints:
1. **Section-Based Editor:** Develop a focused visual editor that allows users to assemble pages using a set of structured, highly customizable sections (e.g., masonry image grids, large typographic headers, video embeds, rolling marquees). Users must be able to drag, drop, and tweak these sections with real-time visual feedback.
2. **Responsive Previews:** Implement a robust preview mechanism to instantly view the site in mobile, tablet, and desktop viewports, ensuring the artistic layouts degrade gracefully across devices.
3. **Local Content Management:** All text, configuration, and image paths must be stored in a local SQLite database. Uploaded media should be saved securely to the local filesystem. This is a single-user, private-by-default system.
4. **Static Publishing:** The core utility of the app is its ability to compile the user's design into a bundle of highly optimized, static HTML/CSS/JS files, fully independent of the editor. This static export should achieve perfect Lighthouse scores and be instantly deployable to any simple static web host.
5. **Privacy & Security:** Do not include any third-party analytics, telemetry, ads, or account systems. All external credentials (if any) must be isolated in a `.env` file with a provided `.env.example`.
6. **Exquisite UI/UX:** The editor's interface must inspire creativity. Utilize high-end UI components, clear loading/success states, and robust error handling. Ensure accessible keyboard navigation and proper ARIA labeling. 
7. **Project Standards:** Write targeted unit tests for the database model and the critical static-generation workflow. Implement at least one end-to-end smoke test for the core editing loop. Produce a detailed README covering setup, data location, architecture, and backup procedures. Deliberately omit massive template libraries and multi-user collaboration features, focusing entirely on a pristine single-user creative experience.