- Is webdevetc/blogetc compatible with Laravel 10 or Laravel 11?
- The package was last released in September 2020 and targets Laravel 6 and 7 era conventions, so its Composer constraints will likely block Laravel 9, 10, 11, or 12. Run composer why-not webdevetc/blogetc against your installed framework version to confirm before planning adoption. Expect to fork or vendor the package and update its constraints if you need a newer Laravel release.
- How do I install webdevetc/blogetc in a Laravel project?
- Install it with Composer, publish the package config, migrations, views, and assets, then run migrations. The package registers a service provider and exposes public blog routes plus admin routes by default. First render is usually quick, but plan time to mount the admin routes behind your own auth middleware and style the public views.
- Is webdevetc/blogetc actively maintained?
- Activity is very low; the last release was September 2020 and the project has around 228 GitHub stars. Treat it as effectively unmaintained and assume there are no upstream security patches. If you adopt it for customer-facing use, budget for forking and maintaining it yourself.
- Can I use webdevetc/blogetc with a headless or API-only Laravel app?
- The package ships Blade views and web routes, not a JSON API, so a headless frontend such as Next.js or Nuxt would require writing an API around its Eloquent models. It fits a conventional Laravel monolith with Blade much better than an API-first architecture. If you need a content API, consider building a thin content model instead.
- How do I secure the blogetc admin panel?
- The package includes an admin panel mounted at /blogetc-admin by default, and you must put it behind your application authentication and authorization middleware. Do not leave it on a default or open gate; tie access to your roles and policies. Also review image upload handling and sanitize the WYSIWYG HTML output server-side.
- Does blogetc include comments, and should I enable them?
- Yes, the package includes blog comments, but enabling them adds spam, moderation, and attack surface that becomes your permanent responsibility. Many teams drop comments entirely and use an external discussion tool if needed. If you keep them, plan moderation, spam controls, and output sanitization from day one.
- How do I customize the blog views and routes in webdevetc/blogetc?
- The package provides publishable config, Blade views, and assets so you can override the public templates and adjust behavior. Routes are owned by the package by default, including /blog and /blogetc-admin, so changing URL structure means editing or wrapping its routes. Published views can drift from package expectations, so track overrides carefully when you fork or upgrade.
- What are the alternatives to webdevetc/blogetc for a Laravel blog?
- Alternatives include building a thin custom blog with your own Post, Category, and Tag models, or using a maintained CMS or headless content platform. If your need is truly a standard blog inside a Laravel monolith on an older framework, blogetc can save initial effort. For long-lived or customer-facing projects on modern Laravel, a small custom implementation is often lower risk.
- Can webdevetc/blogetc handle custom content types or localization?
- No; it is an opinionated standard blog with fixed models for posts, categories, tags, authors, and comments. Custom content types, localization, editorial workflows, or a separate content API mean fighting its schema and routing. If those requirements exist, evaluate building your own content layer instead.
- How do I migrate away from webdevetc/blogetc later?
- Plan an exit path before adoption: export posts, categories, tags, comments, and media, and preserve public URLs with redirects. Because the package owns its tables and routes, moving to another system is a data migration plus routing change rather than a simple package swap. Confirm the export and SEO redirect requirements up front.