Skip to main content

​
Overview

The Page Revamp is a full-stack solution that transforms design sources (Figma URLs or PDFs) and business details into structured, editable landing page content. It solves the problem of turning raw designs and basic business context into production-ready copy and sections using AI, while providing tooling to upload, extract, plan, generate, preview, and manage landing pages.
This Page Revamp Generator is part of Weam. Configuration, usage, and access happen within Weam.

​
What It Does (Capabilities)

  • Design ingestion – Upload PDFs or reference Figma URLs; basic validation and metadata capture.
  • Content extraction – OCR/parse PDFs; extract design elements and structure from URLs/Figma (public demo endpoints available).
  • Business context capture – Collect business name, overview, audience, brand tone, and optional website URL.
  • AI content generation – Use Gemini to plan and generate section-based landing page content; per-section regeneration supported.
  • Section management - Normalize sections with titles, ordering, components, and bounding boxes; publish flow.
  • Editing & preview – Review, inline edit, and preview generated content in the Next.js app.
  • History & management – List, filter, update, and delete landing pages; track status (draft/published/archived).
  • Security and validation – Request validation, input sanitization, basic rate limiting, and structured error handling.

​
User Flows (Non-Ops Usage)

  1. Configure business context → Enter business details (name, overview, audience, tone, optional website URL).
  2. Ingest design → Upload a PDF or provide a Figma/website URL for extraction.
  3. Extract & analyze → Parse files or URLs and extract layout/content hints.
  4. Plan & generate → Use AI endpoints to plan content structure and generate copy by sections.
  5. Review & edit → Adjust sections, regenerate selectively, and refine text in the editor.
  6. Save & publish → Save updates, manage status, and publish when complete.

​
Architecture

​
Technical Design

  • Modules
    • Ingestion – Validates uploads (type/size) via Multer; captures metadata.
    • Extraction – OCR or parse PDFs; normalize data into sections.
    • Planning & Generation – Combines business context and extracted data; uses Gemini for structured copy.
    • Lifecycle – CRUD for landing pages; handles section normalization and ordering.
    • Logging & Errors – Centralized logger (Winston) and error middleware.
  • Pipelines
    Extraction → Validation → Content Planning → Section Generation → Edit/Preview → Publish.
  • Retrieval Logic
    Section normalization ensures consistent schema (title, content, components, order, bounding boxes).
  • Security & Validation
    • Helmet, CORS, express-validator, bcrypt for hashing.
    • express-rate-limit for request throttling.

​
API Reference (High-Level)

​
Auth

  • POST /api/auth/register
  • POST /api/auth/login
  • GET /api/auth/me
  • PUT /api/auth/profile
  • PUT /api/auth/change-password

​
Landing Pages

  • GET /api/landing-pages
  • GET /api/landing-pages/:id
  • POST /api/landing-pages
  • PUT /api/landing-pages/:id
  • PUT /api/landing-pages/:id/sections
  • DELETE /api/landing-pages/:id
  • PUT /api/landing-pages/:id/publish

​
Upload & Processing

  • POST /api/upload/public
  • DELETE /api/upload/cleanup
  • POST /api/upload/pdf
  • POST /api/upload/figma
  • GET /api/upload/status/:fileId
  • DELETE /api/upload/:fileId

​
AI & Content

  • Extraction: POST /api/ai/extract-pdf, extract-design-from-url, extract-figma
  • Planning: POST /api/ai/validate, plan-content, analyze-design
  • Generation: POST /api/ai/generate-content, regenerate-section
  • Full-page: POST /api/ai/generate-landing-page, preview-landing-page, download-landing-page
Public demo endpoints exist; production should enforce JWT authentication.

​
Data & Schemas (Conceptual)

​
User

​
LandingPage

​
Troubleshooting

Symptoms
  • 400 errors on upload
  • “Invalid file type” message
  • Large PDFs fail quickly
Common causes
  • MIME type not allowed (PDF/JPEG/PNG/GIF)
  • File exceeds max size
  • Incorrect form field name
Solutions
  • Use pdf field for PDF uploads
  • Reduce file size under configured limit
  • Verify Content-Type and multipart form settings
Symptoms
  • GET /api/upload/status/:fileId returns 404
  • File deleted prematurely
Solutions
  • Use correct fileId
  • Confirm uploads dir matches backend config
  • Avoid early cleanup
Symptoms
  • 400 error on POST /api/upload/figma
  • “Invalid Figma URL format”
Solutions
  • Use full file URL (https://www.figma.com/file/...)
  • Avoid share/prototype links

​
Tech Stack Summary

​
Best Practices

  • Normalize sections before publish.
  • Provide rich business and design context.
  • Validate inputs per schema.
  • Keep public and private routes separate.
  • Paginate and filter results efficiently.
  • Log actions meaningfully (avoid sensitive data).
  • Restrict uploads to safe types and sizes.
  • Limit regeneration and cache stable planning steps.