Graper Laravel Package

Product Decisions This Supports

• Accelerated Time-to-Market for Marketing Assets: Eliminates the need for custom frontend development to build landing pages, marketing sites, or promotional content. Non-technical teams (e.g., marketing, sales) can create and iterate on pages independently, reducing dependency on engineering.
• Customization Without Complexity: Supports build vs. buy by providing a pre-built solution that can be extended with custom blocks via PHP classes. Ideal for teams needing flexibility without the overhead of developing a full-fledged CMS.
• A/B Testing and Personalization: Enables the creation of multiple page variants (e.g., different CTAs, layouts) for split testing or targeted campaigns. Pages can be dynamically routed or served based on user segments or other criteria.
• Client-Facing Portals: Facilitates the creation of white-labeled or client-specific pages (e.g., for SaaS platforms). Clients can log into Filament to edit their own content, reducing support overhead.
• Content Reusability: Built-in blocks (e.g., hero sections, testimonials, pricing tables) encourage consistency across pages while allowing for modular updates. Custom blocks can be developed to match product-specific needs (e.g., product carousels, dynamic pricing).
• Roadmap for Headless or Hybrid Content: While primarily a visual editor, the package stores content in the database (Eloquent models), enabling future integration with APIs, headless delivery, or dynamic content systems.

When to Consider This Package

Adopt When:

• Your primary admin panel is Filament 3.2+, and you need a visual page builder without investing in a full CMS (e.g., Strapi, Contentful).
• You prioritize speed of iteration over granular control, especially for marketing, sales, or client-facing content.
• Your team lacks frontend expertise but has PHP/Laravel developers who can extend the package with custom blocks.
• You need database-backed content for pages (e.g., to version, API-access, or programmatically manipulate content).
• Your use cases align with static or semi-dynamic content (e.g., landing pages, email templates, internal dashboards) rather than highly interactive or real-time applications.
• You want to reduce developer bottlenecks for content updates, allowing non-technical teams to manage their own pages.

Look Elsewhere When:

• You require multi-language support, advanced media libraries, or workflow features (e.g., approvals, collaborations) beyond what Filament/GrapeJS offers.
• Your project demands real-time collaboration or complex animations/interactivity (e.g., SPAs, dynamic data visualization).
• You’re using Laravel Nova or another admin panel—this package is Filament-specific.
• You need headless CMS capabilities (e.g., GraphQL APIs, decoupled frontend) without the overhead of a full solution like Strapi or Craft CMS.
• Your team prefers low-code/no-code tools (e.g., Webflow, Framer) over a Laravel-integrated solution, even if they require more setup.
• You require server-side rendering of dynamic content (e.g., personalized recommendations, real-time data fetching) beyond static HTML/CSS.

How to Pitch It (Stakeholders)

For Executives:

*"This package is a game-changer for how we deliver marketing and client-facing content. Here’s the value it unlocks:

• Faster Campaigns: Marketing teams can build and publish landing pages in hours—not weeks—using a drag-and-drop editor. No more waiting for developers to code templates for every promotion.
• Reduced Costs: Eliminates the need to hire or train frontend developers for static content creation. Non-technical teams gain self-service capabilities.
• Scalable Personalization: Easily create A/B test variants or client-specific pages (e.g., for SaaS customers) without manual template swaps. Pages are stored in our database, so we can dynamically serve content based on user segments.
• Future-Proof: The package is open-source and extensible—we can add custom blocks (e.g., product carousels, dynamic pricing) to match our product’s unique needs. It integrates seamlessly with our Laravel/Filament stack, so there’s no vendor lock-in.
• Client Satisfaction: For SaaS or agency use cases, clients can edit their own pages via Filament, reducing support requests and improving their experience.

Example Use Cases:

• Launch a Black Friday landing page in a day, not a sprint.
• Let sales teams customize demo pages for prospects without IT involvement.
• Automate onboarding flows with dynamic pages tied to user roles.

This is a low-risk, high-reward investment. We can pilot it in [X] weeks, and if successful, it’ll pay for itself by cutting dev time and empowering our teams. The MIT license means we own the tool—no subscriptions or hidden costs."*

For Engineering Teams:

"GrapeJS + Filament = A Force Multiplier for Content Creation. Here’s why this package is a smart technical choice:

• Zero Frontend Overhead: Uses GrapesJS under the hood, but we get a Filament-native UI with no React/Vue/Alpine.js complexity. The package handles all the heavy lifting of integrating GrapeJS with Filament’s admin panel.
• Extensible via PHP: Custom blocks are added via PHP classes, so we can:
  • Create product-specific components (e.g., ProductCarouselBlock, DynamicPricingBlock).
  • Reuse existing Filament resources (e.g., relationships, policies) in block logic.
  • Example:

    class FeaturedProductsBlock extends Block {
        public function getTemplate() {
            return view('blocks.featured-products')->render();
        }
    }
    

• Database-Backed Content: Pages are stored as Eloquent models (GraperPage), so we can:
  • Fetch content via API (/graper/api/page/{id}) for headless or dynamic use cases.
  • Add soft deletes, revision history, or custom validation via model events.
  • Programmatically create pages (e.g., for onboarding sequences).
• Lightweight and Maintainable: ~20 stars, MIT license, and no dependencies beyond Filament/GrapeJS. The codebase is small enough to audit or fork if needed.
• Roadmap Alignment: Supports our goals for:
  • Self-service marketing tools (e.g., campaign pages).
  • Client portals (e.g., white-labeled instances).
  • A/B testing (e.g., duplicate pages, dynamic routing).

Trade-offs to Consider:

• Static HTML/CSS Only: Blocks can’t include dynamic PHP logic (e.g., @foreach loops). For dynamic content, we’d need to pre-render or use Blade includes in templates.
• GrapeJS Learning Curve: While abstracted, custom block development requires familiarity with GrapeJS’s component system. However, the package provides a simple API for registration and templating.
• Smaller Community: Less documentation or community support than alternatives like Strapi, but faster to implement for Filament users.

Proposed Next Steps:

1. Pilot: Install in a staging environment and test:
   • Basic block customization (e.g., add a TestimonialsBlock).
   • Filament integration (e.g., permissions, resource policies).
   • Frontend rendering (e.g., @include('graper.page') in Blade).
2. Extend: Build 2–3 custom blocks for our top use cases (e.g., product grids, dynamic CTAs).
3. Document: Create internal guides for non-devs on:
   • Using the drag-and-drop editor.
   • Requesting new block types via GitHub issues or PRs.

Why This Beats Alternatives:

• Vs. Strapi/Webflow: No need to manage a separate CMS or pay for hosting. Everything stays in Laravel.
• Vs. Custom Build: Avoids 3–6 months of frontend dev work. We get 80% of the functionality in a few days.
• Vs. Laravel Nova: Filament is our admin panel of choice, and this package is Filament-native.

Let’s prototype this in [X] weeks and validate if it meets our needs for [specific use case]."