Core Laravel Package

Product Decisions This Supports

• Build vs. Buy: Justifies a "buy" decision for static website needs, reducing development time and maintenance overhead for marketing sites, documentation hubs, or internal portals.
• Roadmap Alignment: Enables rapid iteration for non-core product features (e.g., landing pages, case studies, or blog-like content) without diverting engineering resources from core platform development.
• Tech Stack Consistency: Leverages PHP/Laravel ecosystem, allowing PMs to reuse existing talent, tooling (e.g., Laravel Mix, Forge), and CI/CD pipelines.
• Performance-Centric Use Cases: Ideal for high-traffic static content where speed (e.g., Lighthouse scores) and scalability (e.g., CDN-friendly) are priorities over dynamic interactivity.
• Multi-Channel Publishing: Supports headless CMS integrations (e.g., Strapi, Contentful) or Markdown-based workflows, aligning with content teams’ needs for flexibility.
• Cost Optimization: Eliminates server-side rendering costs for static assets, reducing cloud infrastructure spend (e.g., AWS S3 + CloudFront).

When to Consider This Package

• Avoid if:
  • Your use case requires real-time data (e.g., dashboards, user accounts) → Use Laravel’s full stack instead.
  • You need complex user flows (e.g., forms with validation, auth) → Evaluate Laravel Fortify or Filament.
  • Your team lacks PHP/Laravel familiarity → Consider Jamstack tools (e.g., Next.js, Hugo) or no-code platforms (e.g., Webflow).
  • You prioritize SEO for dynamic content (e.g., e-commerce product pages) → Use Laravel + Inertia.js or a dedicated SSG like Gatsby.
• Consider if:
  • You’re building static marketing sites (e.g., "About Us," "Careers") with minimal updates.
  • Content is authored externally (e.g., by marketing teams via CMS or Markdown).
  • You need lightweight, maintainable templates with reusable components (e.g., headers, footers).
  • Your stack already includes Laravel tools (e.g., Envoyer, Nova) for consistency.

How to Pitch It (Stakeholders)

For Executives: "Kiwa/core lets us ship high-performance static websites (e.g., our new customer portal or blog) 10x faster than custom builds, using our existing PHP team. It cuts hosting costs by 70% compared to traditional Laravel apps while improving load times—critical for conversions and SEO. Think of it as ‘Laravel for marketing sites’: no bloat, just speed and simplicity."

For Engineering: *"This is a minimalist Laravel-based SSG (Static Site Generator) that:

• Drops in alongside your existing Laravel apps (uses same routing, middleware, and Blade templates).
• Supports hybrid workflows: Serve static pages via CDN while keeping dynamic routes in Laravel.
• Reduces context-switching: No need to learn new tools—just PHP/Laravel skills.
• Future-proof: Add interactivity later via Alpine.js or Inertia.js if needed. Use case: Replace our bloated WordPress blog with a Git-backed, deploy-once static site that’s faster and cheaper to maintain."*

For Design/Content Teams: *"No more fighting with developers for simple page updates! Kiwa lets you:

• Edit content in Markdown or your CMS of choice (we’ll integrate Strapi).
• Preview changes locally before deployment.
• Get pixel-perfect templates that match our brand, with reusable components (e.g., hero sections, testimonials). Result: Faster launches for campaigns, docs, or internal tools—without engineering bottlenecks."*