How thomasveit89/designsnack-lead-generator works
Project type and purpose
• This is a full-stack lead generation web application (DESIGNSNACK Lead Generator).
• Frontend: Vue.js SPA served by Vite + Tailwind.
• Backend: Node.js + Express REST API.
• Core functionality: scrape job listings, score leads, discover contacts, generate AI emails, cache results on the filesystem.
File structure
• Root files:
• package.json / package-lock.json (dependency management & scripts)
• server.js (Express server & API routing)
• scraper.js (Puppeteer job-scraping logic)
• contact-service.js (Hunter.io & Google Search contact lookup)
• email-service.js (OpenAI GPT for email drafting)
• storage.js (JSON file read/write utilities)
• index.html, vite.config.js, tailwind.config.cjs, postcss.config.cjs (frontend build config)
• src/ directory: Vue 3 application (App.vue, main.js, style.css)
• data/ directory: file-system caches (search results, contact records, search history)
README for additional insights
• REST endpoints: /api/search, /api/search-history, /api/search/:id, /api/find-contacts, /api/generate-email
• External integrations: OpenAI, Hunter.io, Google Custom Search
• Caching strategy: 7-day contact cache, search history persisted as JSON
Components
a. Frontend (Vue.js SPA)
• User Interface (Search form, Results list, “Find Contact & Draft Email” buttons)
• Vite dev server / production hosting
b. API Layer (Express server)
• Route handlers
• Orchestrator glue between services
c. Scraper Service
• Puppeteer job scraper (jobs.ch pagination)
• Produces “search results” JSON
d. Contact Service
• Hunter.io API call
• Google Custom Search API call
• Caches contact data (storage.js → data/contacts)
e. Email Service
• OpenAI GPT-4o-mini call for personalized email templates
f. Storage Layer
• JSON files in data/ (searches, contacts, search-history)
• storage.js abstracts read/write operations
g. External Systems
• jobs.ch website
• Hunter.io
• Google Custom Search
• OpenAI API
Relationships and interactions
1. User → Frontend (Vue.js)
2. Frontend → HTTP request → Express API
3. /api/search → scraper.js → jobs.ch → returns job list → storage.js → data/searches → Express → Frontend
4. /api/find-contacts → contact-service.js → Hunter & Google Search → storage.js → data/contacts → Express → Frontend
5. /api/generate-email → email-service.js → OpenAI API → Express → Frontend
6. Frontend displays results, caches in local state, writes to search-history via GET /api/search-history
Architectural patterns and design principles
• Single-Page Application (SPA) for rich UI interactions
• RESTful API layer separating concerns
• Modular “service” classes for scraper, contact lookup, email generation
• File-based caching as a simple persistence layer (avoids database overhead)
• Configuration-driven integration via environment variables