Slidewire Laravel Package

Product Decisions This Supports

• Internal Developer Portals & Documentation: Replace static Markdown, Confluence, or Notion with interactive, self-hosted presentations for onboarding, technical deep dives, or API documentation. Slidewire’s Markdown support + Livewire interactivity enables searchable code snippets, collapsible sections, and real-time updates tied to Laravel’s database (e.g., sync with GitHub Issues or Jira tickets). Reduces tool sprawl and ensures content stays in version control.

• Sales/Marketing Collateral: Accelerate deck creation for customer demos, investor pitches, or internal sales enablement by leveraging Laravel’s ecosystem. Key advantages:

  • Dynamic data: Pull live metrics (e.g., "Q2 Growth: {{ $revenue }}") from Laravel models.
  • Reusable templates: Standardize themes/layouts across decks (e.g., corporate branding via Blade components).
  • Interactive elements: Embed product screenshots with hover tooltips or clickable "Try It" buttons (via Livewire).
  • Avoid vendor lock-in: No dependency on Google Slides/PowerPoint for internal use cases.

• Roadmap Visualization: Build interactive roadmaps that auto-update when linked to a Laravel database (e.g., ProductRoadmap model). Features:

  • Drag-and-drop timelines (via Livewire components).
  • Filterable views (e.g., "Show only Q3 features").
  • Deep linking: Share URLs to specific slides (e.g., app/roadmap#slide-3).
  • Version control: All content lives in Blade/Markdown files, tracked via Git.

• Build vs. Buy:

  • Buy Slidewire if:
    • Your team uses Laravel/Livewire and needs interactive presentations without frontend overhead.
    • You prioritize self-hosted, database-backed content over SaaS tools (e.g., Slides.com).
    • Your use case fits Slidewire’s scope (e.g., technical docs, sales decks) and doesn’t require offline support or complex animations.
  • Build custom only if:
    • You need SCORM/LMS integration (Slidewire lacks built-in compliance).
    • Your audience requires offline PDF exports (Slidewire renders HTML/JS).
    • You’re using a non-PHP stack (e.g., Python, Node.js).

• Use Cases:

  Type	Example	Slidewire Advantage
  Technical	Live-coded demos (e.g., "Deploying Laravel")	Syntax highlighting, executable code blocks, and real-time output via Livewire hooks.
  Business	Investor decks with live data	Pull real-time metrics (e.g., "MRR: {{ $dashboard->mrr }}") from Laravel models.
  Education	Training modules with quizzes	Use Livewire’s reactive state to track progress (e.g., "Slide 3/10: 75% complete").
  Internal Tools	Interactive runbooks	Embed CLI commands with copy-to-clipboard buttons (via Livewire JavaScript).
  Customer-Facing	Product tours	Highlight features with clickable annotations (e.g., "See how this works →").

When to Consider This Package

Adopt if:

• Tech Stack Alignment:
  • Your application uses Laravel 10+ and Livewire 3.x (Slidewire is tightly coupled to these).
  • You’re comfortable with Blade templating and Livewire components (low learning curve for Laravel devs).
• Content Requirements:
  • Need Markdown-first workflows with Blade/Livewire templating (e.g., mix static content with dynamic data).
  • Presentations require interactivity (e.g., toggleable details, code execution, data tables) but don’t need complex animations.
  • Content is database-backed (e.g., pull slide content from a Presentations table).
• Hosting/Control:
  • Prefer self-hosted solutions over SaaS (e.g., Slides.com, Reveal.js).
  • Want to avoid external dependencies for internal tools (e.g., no Google Slides API calls).
• Audience:
  • Presentations are browser-based (no offline/PDF requirements).
  • Audience has modern browsers (Livewire requires JavaScript).

Look Elsewhere if:

• Tech Stack Mismatch:
  • Using non-PHP stacks (e.g., Python/Django, Node.js, Ruby on Rails).
  • Livewire is not an option (e.g., legacy Laravel apps or Inertia.js-heavy projects).
• Advanced Features:
  • Need offline support (Slidewire is HTML/JS; no PDF/PPTX exports).
  • Require complex animations (e.g., GSAP timelines; Slidewire focuses on simplicity).
  • Mobile-first design is critical (Slidewire prioritizes desktop; test mobile responsiveness).
• Audience Constraints:
  • Presentations must work without JavaScript (e.g., internal tools for non-tech users).
  • Need multi-format exports (e.g., PDF, video; Slidewire renders HTML only).
• Performance Needs:
  • Decks will have >100 slides with heavy components (e.g., large data tables, embedded videos). Benchmark Livewire memory usage.
  • High-traffic public presentations (Slidewire lacks caching headers; may need Varnish/Nginx optimizations).

How to Pitch It (Stakeholders)

For Executives:

*"Slidewire lets us replace static decks with interactive, self-hosted presentations—built entirely within our Laravel ecosystem. This eliminates reliance on third-party tools like Google Slides or PowerPoint for internal use cases, saving time and reducing vendor lock-in.

Key Benefits:

• Faster Updates: Presentations are Blade/Markdown files—edit them like code, version-controlled in Git.
• Dynamic Content: Pull live data into decks (e.g., ‘Q2 Revenue: {{ $dashboard->revenue }}’) without manual updates.
• Reusable Components: Standardize themes, navigation, and layouts across all decks (e.g., corporate branding).
• Interactive Elements: Add clickable demos, code snippets with syntax highlighting, or progress trackers—all without frontend frameworks.
• Cost-Effective: Zero SaaS fees; open-source with no hidden costs.

Use Cases:

• Sales: Customizable pitch decks with real-time product metrics.
• Engineering: Interactive onboarding docs with searchable code examples.
• Product: Live roadmaps that auto-update when linked to our database.

Risk: Minimal—Slidewire is battle-tested (100% feature coverage in tests) and integrates seamlessly with Laravel. We can start with a proof-of-concept deck in under a day.

Ask: Approval to pilot Slidewire for [specific use case, e.g., ‘Q3 investor deck’ or ‘engineering onboarding’] and measure time saved vs. current workflow."*

For Engineering:

*"Slidewire is a Livewire-powered presentation layer that lets us build decks with Markdown + Blade + Livewire interactivity—no frontend frameworks required. Here’s why it’s a low-risk, high-reward choice:

Why Slidewire?

• Leverages Livewire: No need to learn React/Vue—just use Blade components and Livewire’s reactivity.
• Markdown + Blade: Write slides in Markdown (for content) and Blade (for reusable components like footers or navigation).
• Dynamic Data: Pull content from Laravel models (e.g., {{ $presentation->slides }}) or APIs.
• Interactive: Add code blocks with syntax highlighting, toggleable details, or progress trackers via Livewire.
• Seamless Routing: Built-in route macros for deep linking (e.g., app/deck#slide-3).

How to Get Started:

1. Install:

   composer require wendelladriel/slidewire
   

2. Scaffold a Deck:

   php artisan make:slidewire MyDeck
   

3. Edit Slides: Use resources/views/slidewire/decks/my_deck.blade.php (Markdown + Blade).
4. Test Locally:

   php artisan serve
   

5. Run Tests (critical for reliability):

   composer test:browser  # Playwright tests
   composer test          # Unit/feature tests
   

Customization:

• Themes: Extend Slidewire’s config-based themes to match your design system (Tailwind/Bootstrap).
• Components: Add custom Livewire components (e.g., a quiz system or data table).
• Navigation: Override defaults (e