vibespot 1.1.1 → 1.3.0

package/assets/plan-templates/email-announcement.md

@@ -0,0 +1,41 @@
+---
+id: email-announcement
+label: Product Announcement
+description: New feature, product update, or company news announcement
+icon: megaphone
+order: 110
+contentType: email
+---
+
+# Product Announcement Email
+
+## Goal
+Announce a new feature, product update, or company milestone. Drive recipients to try, learn about, or engage with the announcement.
+
+## Audience
+TBD — existing customers, all subscribers, specific segment?
+
+## Primary CTA
+TBD — common patterns: "Try It Now", "See What's New", "Read the Full Story".
+
+## Sections / Modules
+1. **preheader** — hidden inbox preview text
+2. **header** — logo, optional "What's New" badge
+3. **hero** — bold headline announcing the update, hero image or product screenshot
+4. **features** — 3-4 key benefits of the update (not features list — what it means for them)
+5. **cta-block** — primary CTA to try or learn more
+6. **footer** — unsubscribe link, physical address, social links
+
+## Subject Line & Preheader
+- Subject: TBD — e.g., "We just shipped [feature]. Here's why it matters."
+- Preheader: TBD — extends subject, 40-90 chars
+
+## Brand & Tone
+TBD — excited but grounded? Technical and precise? Casual and conversational?
+
+## Open questions
+- [ ] What is being announced (feature, product, update, milestone)?
+- [ ] What are the top 3 benefits for the recipient?
+- [ ] Is there a visual (screenshot, illustration, demo GIF)?
+- [ ] Is this available to everyone or a specific tier/segment?
+- [ ] Is there a deadline or urgency element?

package/assets/plan-templates/email-event-invite.md

@@ -0,0 +1,43 @@
+---
+id: email-event-invite
+label: Event Invitation
+description: Webinar, conference, meetup, or launch event invite
+icon: calendar
+order: 130
+contentType: email
+---
+
+# Event Invitation Email
+
+## Goal
+Drive registrations or RSVPs for an event. Communicate the value of attending clearly enough that recipients act within one read.
+
+## Audience
+TBD — existing customers, prospects, community, specific segment?
+
+## Primary CTA
+TBD — common patterns: "Register Now", "Save Your Spot", "RSVP".
+
+## Sections / Modules
+1. **preheader** — hidden inbox preview text
+2. **header** — logo, optional "You're Invited" badge
+3. **hero** — event name headline, date/time/location prominently displayed, hero image or event banner
+4. **details** — what the event covers, who should attend, what they'll learn (2-3 bullet points)
+5. **speakers** — speaker/host bios with headshots (if applicable)
+6. **cta-block** — single "Register" CTA with urgency note (limited spots, early-bird deadline)
+7. **footer** — unsubscribe link, physical address, calendar add link
+
+## Subject Line & Preheader
+- Subject: TBD — e.g., "Join us March 15: [Event Topic] with [Speaker]"
+- Preheader: TBD — extends subject, 40-90 chars
+
+## Brand & Tone
+TBD — professional and authoritative? Casual and community-driven? Exclusive and premium?
+
+## Open questions
+- [ ] Event name, date, time (with timezone), and format (in-person, virtual, hybrid)?
+- [ ] Location or platform (Zoom, venue address)?
+- [ ] Who are the speakers or hosts?
+- [ ] What will attendees learn or gain?
+- [ ] Is there a capacity limit or registration deadline?
+- [ ] Is there an early-bird or free-tier pricing?

package/assets/plan-templates/email-newsletter.md

@@ -0,0 +1,41 @@
+---
+id: email-newsletter
+label: Newsletter / Digest
+description: Curated content roundup — articles, updates, and resources
+icon: newspaper
+order: 120
+contentType: email
+---
+
+# Newsletter / Digest Email
+
+## Goal
+Deliver a curated selection of content, updates, or resources that keeps subscribers engaged and positions the brand as a trusted source.
+
+## Audience
+TBD — subscribers, customers, community members?
+
+## Primary CTA
+TBD — common patterns: "Read the Full Article", "Visit the Blog", "See All Updates".
+
+## Sections / Modules
+1. **preheader** — hidden inbox preview text
+2. **header** — logo, edition number or date, optional nav links
+3. **hero** — featured article or top story with image and summary
+4. **content-grid** — 3-4 secondary stories with thumbnails, titles, and 2-sentence summaries
+5. **cta-block** — link to full archive or blog
+6. **footer** — unsubscribe link, physical address, social links, "forward to a friend"
+
+## Subject Line & Preheader
+- Subject: TBD — e.g., "The Weekly Roundup: 5 things worth your time"
+- Preheader: TBD — extends subject, 40-90 chars
+
+## Brand & Tone
+TBD — editorial and curated? Casual and scannable? Data-driven and analytical?
+
+## Open questions
+- [ ] What is the newsletter cadence (weekly, biweekly, monthly)?
+- [ ] How many content items per issue (3-5 recommended)?
+- [ ] Is there a featured/lead article format?
+- [ ] What content types: blog posts, industry news, tips, product updates?
+- [ ] Should it include a personal note from the editor/founder?

package/assets/plan-templates/email-re-engagement.md

@@ -0,0 +1,42 @@
+---
+id: email-re-engagement
+label: Re-engagement Email
+description: Win-back email for inactive users or lapsed customers
+icon: refresh
+order: 140
+contentType: email
+---
+
+# Re-engagement Email
+
+## Goal
+Re-activate inactive subscribers or lapsed customers by reminding them of value, highlighting what they've missed, and offering a clear reason to return.
+
+## Audience
+TBD — inactive users (how long?), lapsed customers, churned subscribers?
+
+## Primary CTA
+TBD — common patterns: "Come Back and See What's New", "Reactivate Your Account", "Claim Your Offer".
+
+## Sections / Modules
+1. **preheader** — hidden inbox preview text
+2. **header** — logo, simple and clean
+3. **hero** — direct acknowledgment headline ("We noticed you've been away"), 1-2 sentence personal message
+4. **whats-new** — 2-3 highlights of what they've missed (new features, content, improvements)
+5. **offer** — incentive if applicable (discount, free month, exclusive content)
+6. **cta-block** — single "Come Back" CTA
+7. **footer** — unsubscribe link (prominent — respect their choice), physical address
+
+## Subject Line & Preheader
+- Subject: TBD — e.g., "A lot has changed since you left"
+- Preheader: TBD — extends subject, 40-90 chars
+
+## Brand & Tone
+TBD — genuine and low-pressure? Playful and lighthearted? Direct and value-focused?
+
+## Open questions
+- [ ] How long has the user been inactive (defines urgency level)?
+- [ ] What new features or content have launched since they left?
+- [ ] Is there a win-back offer (discount, free trial extension, exclusive access)?
+- [ ] Should the email include usage data ("You had X saved / X connections")?
+- [ ] What happens if they don't re-engage (account deletion, list cleanup)?

package/assets/plan-templates/email-welcome.md

@@ -0,0 +1,41 @@
+---
+id: email-welcome
+label: Welcome Email
+description: Onboarding email for new signups — confirm, orient, activate
+icon: mail
+order: 100
+contentType: email
+---
+
+# Welcome Email
+
+## Goal
+Welcome new subscribers or customers, confirm their action, and guide them to a first meaningful interaction with the product or service.
+
+## Audience
+TBD — new signup, new customer, new subscriber? What did they just do?
+
+## Primary CTA
+TBD — common patterns: "Get Started", "Complete Your Profile", "Explore the Dashboard".
+
+## Sections / Modules
+1. **preheader** — hidden inbox preview text extending the subject line
+2. **header** — logo centered, optional tagline
+3. **hero** — warm greeting headline, 1-2 sentence welcome message
+4. **getting-started** — 3 numbered steps to first value (with icons or numbers)
+5. **cta-block** — single primary CTA button
+6. **footer** — unsubscribe link, physical address, social links
+
+## Subject Line & Preheader
+- Subject: TBD — e.g., "You're in. Here's what to do first."
+- Preheader: TBD — extends subject, 40-90 chars
+
+## Brand & Tone
+TBD — friendly and helpful? Professional and concise? Warm and personal?
+
+## Open questions
+- [ ] What action triggered this email (signup, purchase, subscription)?
+- [ ] What should the recipient do first?
+- [ ] What are the 3 most important getting-started steps?
+- [ ] Is there a time-sensitive element (trial expiry, limited offer)?
+- [ ] Should this email include the user's name (personalization token)?

package/assets/plan-templates/event-registration.md

@@ -0,0 +1,42 @@
+---
+id: event-registration
+label: Event Registration
+description: Conference, webinar, or workshop — drive registrations
+icon: calendar
+order: 30
+---
+
+# Event Registration
+
+## Goal
+Drive ticket purchases or free registrations for a specific event.
+
+## Audience
+TBD — who is the event for? (industry, role, experience level)
+
+## Primary CTA
+TBD — typically "Register now", "Get tickets", "Save my seat".
+
+## Sections / Modules
+1. **event-hero** — countdown, event name, date, location, primary CTA
+2. **event-summary** — 2–3 sentence pitch + the value of attending
+3. **speakers** — grid with photos, names, titles, short bios
+4. **agenda** — timed schedule (single or multi-day)
+5. **sponsors** — tiered logo grid (or single block if no tiers)
+6. **venue-or-format** — location map / online platform details
+7. **ticketing** — tier comparison with "Register" CTA per tier
+8. **faq** — practical questions: refunds, accessibility, dress code, recordings
+9. **footer** — contact, legal, social
+
+## Brand & Tone
+TBD — energetic/anticipation, professional/industry-credible, intimate/community
+
+## Open questions
+- [ ] What is the event called and what's the one-line pitch?
+- [ ] When is it (date, time, time zone) and where (city/venue or online platform)?
+- [ ] Is it free or paid? If paid, what tiers and price points?
+- [ ] Who are the headline speakers (names + companies, even just 1–3 to start)?
+- [ ] What's the agenda format — single track, multi-track, multi-day?
+- [ ] Is there a registration deadline or capacity limit worth surfacing?
+- [ ] Does the event have sponsors, and how should they be tiered?
+- [ ] Any specific accessibility, refund, or COVID-style policies to call out?

package/assets/plan-templates/portfolio.md

@@ -0,0 +1,41 @@
+---
+id: portfolio
+label: Portfolio
+description: Personal or studio site — showcase work, drive contact
+icon: briefcase
+order: 50
+---
+
+# Portfolio
+
+## Goal
+Showcase work and convert visitors into project inquiries, hires, or collaborators.
+
+## Audience
+TBD — recruiters, agency clients, prospective collaborators?
+
+## Primary CTA
+TBD — typically "Get in touch", "Hire me", "Book a call".
+
+## Sections / Modules
+1. **hero** — name, role, one-line pitch, primary CTA
+2. **selected-work** — 4–8 case studies in a grid (image + title + tags)
+3. **about** — bio, photo, story / approach
+4. **services-or-skills** — what you do, listed concretely
+5. **clients-or-recognition** — logos, awards, press
+6. **testimonials** — 1–3 quotes from clients or collaborators
+7. **contact** — email + form, social links
+8. **footer** — minimal: copyright, social, return-to-top
+
+## Brand & Tone
+TBD — minimal/editorial, bold/expressive, technical/clean
+
+## Open questions
+- [ ] What's your name, role, and the one-line pitch you want at the top?
+- [ ] Solo portfolio, studio, or collective? If a studio, what's the team size?
+- [ ] Which 4–8 projects should be featured, and do you have imagery / case studies?
+- [ ] What primary action should a visitor take — email, form, calendar link?
+- [ ] Are you actively looking for work, freelance projects, or both?
+- [ ] Any awards, press mentions, or recognizable client logos to feature?
+- [ ] Reference portfolios you admire — Bruno Simon, Locomotive, plain Substack-bio style?
+- [ ] Should case studies open inline (modals) or link to dedicated detail pages?

package/assets/plan-templates/restaurant.md

@@ -0,0 +1,42 @@
+---
+id: restaurant
+label: Restaurant
+description: Single-location restaurant — drive reservations and visits
+icon: utensils
+order: 70
+---
+
+# Restaurant
+
+## Goal
+Drive reservations, takeaway orders, and walk-in visits.
+
+## Audience
+TBD — locals, tourists, special-occasion diners, lunch crowd?
+
+## Primary CTA
+TBD — "Book a table", "Order online", "View menu".
+
+## Sections / Modules
+1. **hero** — atmospheric photography, name, tagline, primary CTA
+2. **about** — story of the restaurant, chef, or concept
+3. **menu** — categories with featured dishes (skip full menu — link out)
+4. **gallery** — interior, dishes, ambience
+5. **reservations** — booking widget or instructions
+6. **reviews** — quotes from press or diners
+7. **location-and-hours** — address, map, opening hours, contact
+8. **events-or-private-dining** — optional, skip if not offered
+9. **footer** — social, newsletter, legal
+
+## Brand & Tone
+TBD — fine-dining/elegant, cozy/neighborhood, bold/trendy, casual/family
+
+## Open questions
+- [ ] What is the restaurant called, where is it, and what's the cuisine?
+- [ ] What's the one-line story or concept (chef-driven, family-run, fast-casual, etc.)?
+- [ ] Do you take reservations — and if so, via which platform (OpenTable, Resy, Tock, in-house)?
+- [ ] Is there online ordering or delivery, and via which platform?
+- [ ] Do you want a featured-dishes section or just a link to the full menu (PDF / external)?
+- [ ] Any press mentions, awards, or stars to call out?
+- [ ] Do you host private events or have a separate private-dining offering?
+- [ ] Reference vibes — Eleven Madison, Sweetgreen, In-N-Out, neighborhood bistro?

package/assets/plan-templates/saas-landing.md

@@ -0,0 +1,42 @@
+---
+id: saas-landing
+label: SaaS Landing Page
+description: Cloud product — sign-ups, demo bookings, or trial conversions
+icon: rocket
+order: 10
+---
+
+# SaaS Landing Page
+
+## Goal
+Drive sign-ups, demo bookings, or free-trial conversions for a cloud product.
+
+## Audience
+TBD — describe the target persona (industry, role, company size, key pain).
+
+## Primary CTA
+TBD — common patterns: "Start free trial", "Book a demo", "Get started free".
+
+## Sections / Modules
+1. **hero** — headline, sub-headline, primary CTA, optional product screenshot
+2. **trust-bar** — customer / partner logos
+3. **features-grid** — 3–6 product benefits with icons and short copy
+4. **how-it-works** — 3-step explainer (sign up → connect → see results)
+5. **testimonials** — 1–3 customer quotes with name, role, company
+6. **pricing-table** — 2–4 tiers with feature comparison
+7. **faq** — 4–8 Q&A covering common objections
+8. **cta-banner** — final conversion-focused CTA
+9. **footer** — links, legal, copyright
+
+## Brand & Tone
+TBD — confident/professional, playful/casual, technical/approachable?
+
+## Open questions
+- [ ] What is the product name and one-line description (pitch)?
+- [ ] Who is the primary buyer / user persona?
+- [ ] What is the single most important action a visitor should take?
+- [ ] What are the top 3 product benefits or differentiators?
+- [ ] Do you have customer logos, testimonials, or case studies ready?
+- [ ] Pricing — free + paid + enterprise, single price, or contact-sales only?
+- [ ] Are there integrations or platforms worth highlighting?
+- [ ] Any reference sites or competitors whose vibe you want to match (or avoid)?