- Is soltys/slate-bundle compatible with Laravel?
- No. soltys/slate-bundle is a Symfony bundle that depends on Symfony's kernel, bundle registration, DI container, and config-tree conventions. Laravel uses Symfony components but does not boot a Symfony kernel, so the bundle cannot be installed and run as a normal Laravel package. Treat it as a Symfony-only dependency.
- Can I install soltys/slate-bundle with Composer in a Laravel project?
- You can add the Composer package, but it will not boot or integrate with Laravel's service container in the way a Laravel package would. The bundle expects Symfony bundle registration and configuration, so any install in a Laravel app would be incomplete without a fork or separate Symfony runtime. Do not plan a drop-in Composer install.
- What does soltys/slate-bundle actually do?
- It wraps the generation of Slate-style API documentation and exposes it as configurable Symfony bundle output. Slate is a static, single-page, markdown-driven documentation site, and this bundle helps turn configuration into that output. The core value is a build-time transformation rather than runtime framework behavior.
- Which Symfony and PHP versions does soltys/slate-bundle support?
- The provided evaluation does not confirm exact version constraints; it flags this as a key spike question. Check the repository's composer.json and release history before relying on it. Given the low adoption profile, expect the bundle to be pinned to older Symfony and PHP versions.
- Does soltys/slate-bundle generate docs from OpenAPI or route annotations?
- That is not confirmed in the available context and should be verified by reading the source. The bundle is described as configurable Slate output, so it may use a bespoke config format rather than an OpenAPI spec. If an OpenAPI-first workflow matters, confirm this before any spike.
- Can I reuse the Slate markdown logic from soltys/slate-bundle in Laravel?
- Potentially, but not as a drop-in package. The useful config-to-markdown transformation appears separable from the Symfony wiring, so a fork could strip the container coupling and become an internal Laravel command. Budget maintenance effort because you would own that fork.
- What are the best Laravel alternatives to soltys/slate-bundle for API documentation?
- For Laravel-native API docs, evaluate dedoc/scramble or knuckleswtf/scribe to generate OpenAPI or collection artifacts from routes and annotations. If you need Slate's single-page look, add a CI step that transforms an OpenAPI spec into Slate markdown and builds the static site. Redoc or Scalar are simpler renderers if Slate's visual output is not a hard requirement.
- Is soltys/slate-bundle actively maintained and production-safe?
- The evaluation signals high technical risk: 4 stars, 0 dependents, a single maintainer, and a composite score of 0.08. That profile suggests upstream fixes are unlikely and the bundle may not track newer Symfony, PHP, or Slate releases. MIT licensing removes legal friction but provides no SLA or vendor support.
- How should I test Slate documentation generation in a Laravel CI pipeline?
- If you adopt an OpenAPI-first pipeline, generate the spec in CI and validate it before transforming it to Slate markdown. Keep any Slate build step isolated at build time and never in the request path. If you fork the bundle's logic, add unit tests around the config-to-markdown transformation.
- Can I use Slate documentation with Laravel without installing this bundle?
- Yes. The recommended path is to generate an OpenAPI spec with a Laravel tool such as Scramble or Scribe, then transform that spec into Slate markdown in CI and build the static site. That avoids a Symfony runtime and keeps the documentation pipeline Laravel-native. Slate then acts only as a renderer fed by generated specs.