Can I vibe code Strapi?

Build a lightweight headless content engine in Node.js, Express, and PostgreSQL using Drizzle ORM to manage localized storefront landing page content.

1. DATA MODEL & SCHEMA:
- Dynamic Content Entries table: id (uuid), slug (string, unique), status ('draft', 'published'), locale (string, e.g. 'en-US'), publication_date (timestamp), created_at, updated_at.
- Components table: entry_id (fk), component_type ('hero_banner', 'product_grid', 'text_block'), rank (integer), schema_data (JSONB for dynamic fields).
- Media Assets table: id, file_name, file_url, mime_type, file_size, storage_provider ('s3', 'local').

2. CORE API ROUTING:
- REST GET endpoints for public consumption: `/api/v1/content/:slug?locale=en-US` returning merged JSON structures only if status is 'published'.
- Authenticated Admin Endpoints: POST, PUT, DELETE for entries and nested components protected by API Bearer tokens.
- Implement automatic draft mode query parameters for authenticated preview sessions (`?preview=true`).

3. WEBHOOK LOGIC:
- Maintain a Webhooks table storing target URLs and subscribed event triggers (`content.create`, `content.publish`).
- Dispatch asynchronous POST payloads with cryptographic HMAC signatures in headers whenever content status flips to 'published'.

4. FILE HANDLING & INTEGRATION:
- Implement direct file upload endpoint storing images in AWS S3 or Cloudflare R2 bucket with secure random key paths.
- Return JSON metadata matching Media Assets schema upon upload completion.

5. FAILURE MODES & EDGE CASES:
- Return explicit validation error responses when dynamic JSONB component schemas fail required key structures.
- Ensure database transactions wrap nested component creations so partial writes roll back on failure.
- Do NOT build a full visual admin interface in this prompt; restrict UI scope to JSON API routes and OpenAPI standard documentation specs.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs