- How do I install jeffersongoncalves/website in a Laravel application?
- Install it with Composer using composer require jeffersongoncalves/website. The package ships a Laravel-native service provider, so it registers itself automatically without manual wiring. After installing, publish the package's config and views with the standard vendor:publish command so you can customize them. Then review the published config file to set your site options before hitting the public routes.
- Which Laravel versions does this package support?
- The package is built on Laravel-native conventions such as a service provider, publishable config and views, and standard public routing, so it targets modern Laravel releases. Because version constraints live in the package's composer.json, check that file or the repository's releases before adding it to an older application. If you are on an unsupported Laravel version, Composer will block the install rather than letting you end up with a broken site.
- How is jeffersongoncalves/website different from a full CMS like Statamic or WordPress?
- This package is a lightweight website layer, not a full content management system. Instead of an opinionated admin, database schema, and editor workflow, it gives you configurable pages, public routes, and publishable views that stay inside your existing Laravel application. That makes it a good fit when you mainly need marketing or content pages and want to keep site code separate from your application logic. If you need multi-author editorial workflows and complex content modeling, a full CMS is usually the better choice.
- Can I customize the views and configuration?
- Yes. Both the config and the views are publishable, so you can copy them into your application and edit them freely. Once published, Laravel resolves your copies ahead of the package defaults, which means you own the markup and settings without forking the package. This is the recommended path for matching your brand or adding your own layout components.
- How do I add or edit pages and dynamic content?
- Pages and content are managed through the package's configurable page layer, which supports both static sections and dynamic content. The exact registration format, whether config-driven or routed through your own data source, is described in the package documentation, so follow that when adding a new page. Because the site code stays separate from your application logic, you can add pages without touching unrelated parts of your app.
- Does the package handle SEO metadata and sitemaps?
- The package provides SEO-friendly URLs and metadata handling, and its routing is structured to be sitemap-ready. That means you get clean, predictable public URLs and the hooks needed to expose metadata per page. Sitemap generation itself is typically wired up in your application using the available routes, so plan to add or configure that piece rather than assuming it is fully automatic.
- Will the package conflict with my existing routes?
- The package registers its own public routes through its service provider, and those routes are separate from your application's existing route definitions. Conflicts are most likely if you already define a catch-all route or reuse the same URL prefixes, so review the published config and route list after installing. Running php artisan route:list right after installation is a quick way to confirm what was registered and spot overlaps.
- Can I manage website content with Filament?
- Yes. The package is designed to play well with Filament-based admin panels, which is useful if your application already uses Filament for administration. You keep Filament resources for editing content while the package handles the public-facing pages, routes, and views. That combination gives you an editing UI without adopting a separate CMS.
- What should I check before using this in production?
- Confirm that the published config matches your environment and that the public routes return the expected pages in a staging deploy. Test the site with config and route caching enabled, since cached routes and config are how most Laravel production deployments run. Also verify metadata output and any sitemap wiring, and add feature tests that request your key URLs so regressions in routing or views are caught early.
- What alternatives to jeffersongoncalves/website should I consider?
- If you need editorial workflows, media libraries, and content modeling, a full CMS such as Statamic or a Filament-based admin with custom models is a stronger fit. If your site is only a handful of fixed pages, plain Laravel routes and Blade views, or a static site generator, may be simpler than any package. Choose jeffersongoncalves/website when you want configurable pages, SEO-friendly routing, and publishable views without the weight of a complete CMS.