LauraMepson Landing Page

A landing page application that collects company information and allows users to add additional details through email links.

• Simple landing page with LauraMepson branding
• Form to collect company name and email
• SQLite database storage for submissions
• Email functionality to send users a unique link
• Continuation page for adding more information
• Image upload and storage using Uploadcare

├── api/                  # API route handlers
│   ├── images.ts         # Image-related API endpoints
│   ├── submissions.ts    # Submission-related API endpoints
│   └── index.ts          # API routes configuration
├── controllers/          # Request handling logic
│   ├── imageController.ts # Image upload/retrieval logic
│   └── submissionController.ts # Submission handling logic
├── models/               # Data models and types
│   ├── image.ts          # Image-related types
│   └── submission.ts     # Submission-related types
├── services/             # Business logic
│   ├── imageService.ts   # Image metadata operations
│   ├── uploadcareService.ts # Uploadcare integration
│   ├── databaseService.ts # Database operations
│   └── emailService.ts   # Email sending functionality
├── utils/                # Utility functions
│   └── helpers.ts        # Helper functions
├── views/                # HTML templates
│   ├── landing.html      # Main landing page
│   └── continue.html     # Continuation page
├── public/               # Static assets and client-side JS
│   ├── css/              # Stylesheets
│   │   └── styles.css    # Common styles
│   └── js/               # Client-side JavaScript
│       ├── landing.js    # Landing page script
│       └── continue.js   # Continuation page script
└── index.ts              # Main entry point

The application uses a SQLite database with the following schemas:

CREATE TABLE IF NOT EXISTS laura_mepson_submissions_v1 (
  id TEXT PRIMARY KEY,
  company_name TEXT NOT NULL,
  email TEXT NOT NULL,
  created_at TEXT NOT NULL,
  additional_fields TEXT
)

CREATE TABLE IF NOT EXISTS laura_mepson_images_v1 (
  id TEXT PRIMARY KEY,
  original_name TEXT NOT NULL,
  content_type TEXT NOT NULL,
  size INTEGER NOT NULL,
  uploaded_at TEXT NOT NULL,
  submission_id TEXT NOT NULL,
  cdn_url TEXT NOT NULL
)

1. User visits the landing page
2. User submits company name and email
3. Data is saved to SQLite database
4. User receives an email with a unique link
5. User can click the link to add more information
6. Additional information is saved to the database
7. User can upload and manage images related to their submission

• Main landing page: https://[username].web.val.run
• Continuation page: https://[username].web.val.run?action=continue&id=[unique_id]

Images are stored using Uploadcare:

• Uploadcare handles file uploads, storage, and CDN delivery
• Image metadata is stored in our SQLite database
• Users can upload, view, and delete images
• Images are associated with a specific submission

• UPLOADCARE_SECRET_KEY: Secret key for Uploadcare API authentication

• When modifying the database schema, create a new table with a new version number
• Email templates are defined in emailService.ts
• The unique ID generation is handled in utils/helpers.ts
• Val Town HTTP vals use query parameters instead of path parameters for routing

The application uses a SQLite database with the following schema:

CREATE TABLE IF NOT EXISTS laura_mepson_submissions_v1 (
  id TEXT PRIMARY KEY,
  company_name TEXT NOT NULL,
  email TEXT NOT NULL,
  created_at TEXT NOT NULL,
  additional_fields TEXT
)

1. User visits the landing page
2. User submits company name and email
3. Data is saved to SQLite database
4. User receives an email with a unique link
5. User can click the link to add more information
6. Additional information is saved to the database
7. User can upload and manage images related to their submission

• Main landing page: https://[username].web.val.run
• Continuation page: https://[username].web.val.run?action=continue&id=[unique_id]

Images are stored using Val Town's blob storage:

• Images are stored with a unique ID
• Metadata is stored alongside each image
• Users can upload, view, and delete images
• Images are associated with a specific submission

• When modifying the database schema, create a new table with a new version number
• Email templates are defined in email.ts
• The unique ID generation is handled in utils.ts
• Val Town HTTP vals use query parameters instead of path parameters for routing