Gustamic Laravel Package

Product Decisions This Supports

Build vs. buy for hospitality/restaurant verticals. This is a Statamic (Laravel) starter kit rather than a general-purpose CMS addon. The decision it most directly supports is "do we scaffold our first restaurant site from a kit or start from a blank Statamic install?" The now-included MIT LICENSE and .gitignore remove the legal ambiguity that previously blocked that comparison — you can fork it into a client repo without a licensing conversation.

Roadmap sequencing for menu/content features. The move from a hardcoded /menu path to resolving the menu page entry tells you the kit assumes customers will rename slugs. If your roadmap includes multi-location or per-venue menus, that's the seam to extend, not fight. Treat the entry-relative linking and the "Restaurant Details" control panel fields as the intended extension points.

SEO/discovery commitments. JSON-LD sameAs now derives from configured social profiles, and JSON-LD plus analytics values are encoded script-safe. That means structured-data and analytics correctness is a supported concern of the kit, not something your team hand-rolls. Useful when scoping an SEO workstream: you inherit baseline Restaurant schema and social-profile linkage for free, and you can safely let non-technical editors type into control panel fields without a stored-XSS risk.

Platform upgrade timing. Install verified on Statamic 6.35 / Laravel 13 is a signal for infra planning. If your platform standard is Statamic 6 / Laravel 13, this kit is a viable reference; if you're pinned to Statamic 5 or Laravel 11, adoption is a forcing function on an upgrade you may not want yet.

Content-ops and onboarding. Sample content now installs by default on non-interactive installs. That's directly relevant to CI and to demo/staging provisioning — it makes the kit usable for automated environment setup and for sales demos without a manual post-install step.

Design-system scoping. Removal of unused font loads (Bangers, Chewy), the broken hardcoded preload, and the phantom footer dividers is a small but real performance and fidelity win. It sets a low baseline you can measure against, but it also tells you the front-end is bespoke and will need a design pass for brand fit.

When to Consider This Package

Consider it when all of the following hold:

• You're building a restaurant, café, bar, or small hospitality site (single venue, or a small set where a shared menu structure makes sense).
• Your stack is already Statamic 6 / Laravel 13, or you're willing to be there.
• You want a working reference for menu pages, featured-menu sections, footer navigation, Restaurant JSON-LD, and a "Restaurant Details" settings surface — and you'd rather adapt than author.
• Your editors are non-technical and will be typing into control panel fields (the script-safe encoding now makes that a defensible posture).
• You need environments to bootstrap reproducibly — the non-interactive sample-content fix matters here.

Look elsewhere when:

• You need multi-tenant or franchise-scale menu management (per-location pricing, availability, allergens across hundreds of venues). This is a starter kit, not a menu-management platform.
• You need online ordering, reservations, or POS integration. Nothing in this release suggests commerce capability; you'd integrate a third party and the kit gives you only a presentation layer.
• You're not on Statamic. The value here is Statamic-specific (entries, control panel, Antlers templates); porting it to plain Laravel or another CMS discards most of the benefit.
• You need a maintained, versioned, support-contracted product. The release cadence reads as hobbyist/small-team: licensing and README polish landed in the same version as functional fixes. That's fine for a scaffold, wrong for a dependency you need SLAs on.
• Your accessibility or Core Web Vitals bar is high. The font and footer fixes show the front-end hasn't been through a rigorous audit; budget for one.

How to Pitch It (Stakeholders)

To executives: This is an MIT-licensed starting point for restaurant websites on our existing Laravel/Statamic stack. It compresses the first two weeks of a hospitality build — menu pages, footer nav, social-profile structured data for search, and an editor-facing settings screen — into an install. Latest release added a formal license and closed a stored-XSS path in the analytics and structured-data fields, so it's safe to hand to non-technical editors. Cost is zero; the trade-off is that it's a scaffold, not a supported product — we own maintenance after fork.

To engineering: Small, well-scoped release. Three things that matter: MIT license means we can vendor it; JSON-LD and analytics output are now script-safe encoded, which removes an injection vector from control-panel input; and menu/footer links resolve the menu page entry instead of a hardcoded /menu, so slug renames don't silently break navigation. Verified on Statamic 6.35 / Laravel 13. Also fixed: sample content installs on non-interactive runs (good for CI), and dead font loads and phantom footer rules were removed. No breaking changes, no deprecations. Treat it as a fork-and-own scaffold — the front-end will need a brand and performance pass.