Overview We run a Google Ads agency producing AI-generated advertorial landing pages at scale. We already have strong design and copy generation workflows, but we need a developer to build a deployment automation bot that takes generated page content and automatically publishes it to Vercel. The goal is to eliminate manual deployment and allow our system to generate, validate, and deploy advertorial pages automatically. This is a short build project that could turn into ongoing work maintaining and expanding the system. ⸻ What We Need Built A lightweight automation system that: 1. Receives generated advertorial page files • HTML/CSS/JS or JSON content • images/assets • metadata (slug, title, campaign, etc.) 2. Runs automated validation checks • required page sections exist (privacy link, disclaimer, etc.) • tracking parameters preserved • image size/optimization checks • broken link detection 3. Creates or updates pages in a GitHub repository • places files into the correct folder structure • commits changes automatically 4. Triggers automatic deployment via Vercel • using the existing Vercel GitHub integration • each advertorial becomes its own route (e.g. /campaign-name) 5. Supports multiple domains • ability to deploy pages across multiple advertorial domains ⸻ Example Workflow AI generates a new advertorial → Bot receives the page package → Bot runs validation → Bot commits to GitHub repo → Vercel automatically deploys → Page goes live on domain. ⸻ Preferred Stack Open to suggestions, but likely something like: • Node.js or Python automation script • GitHub API • Vercel deployments via Git integration • Optional queue system (if scaling later) Framework for pages may be: • Next.js • Astro • or simple static HTML ⸻ Deliverables • Working deployment automation • Clean repo structure for advertorial pages • Documentation on how the system works • Ability to easily add new advertorials via the bot ⸻ Nice to Have • Experience with Vercel deployments • Experience building content pipelines • Familiar with AI-generated content workflows • Experience with static site generation ⸻ Project Scope Initial build should take ~1–2 weeks. If successful, there will likely be ongoing work improving the system (domain management, scaling deployments, campaign tooling). ⸻ To Apply Please include: 1. Examples of similar automation or deployment pipelines you’ve built 2. Your suggested architecture for this system 3. Estimated timeline Looking for someone who can build a simple, robust system rather than over-engineering it. :::