Weave Code
Manual Bundle Laravel Package
opifer/manual-bundle
A Symfony bundle for building and managing online manuals and documentation. It provides structured manual pages, content management, and integration with Opifer's CMS, letting teams organize help content and publish searchable documentation from within their application.
Provides a symfony2 project with a handy help system in which you can easilly add, update and remove help articles using Markdown
Frequently asked questions about Manual Bundle
- Can I install opifer/manual-bundle in a Laravel application with Composer?
- No. opifer/manual-bundle is a Symfony 2 bundle, not a Laravel package, and it depends on Symfony bundle registration, the DI container, YAML routing, Doctrine entities, and Twig views. Running composer require in a Laravel app is not a realistic integration path. Treat it as a design reference rather than a dependency.
- Is opifer/manual-bundle compatible with Laravel 10, Laravel 11, or PHP 8?
- No. The bundle targets Symfony 2, which reached end of life in 2019, and it will not resolve against modern symfony/* packages or PHP 8.x constraints. For Laravel applications, compatibility is a non-starter and should not consume discovery time. Use the concepts, not the code.
- What is opifer/manual-bundle used for?
- It is a Symfony bundle for building and managing online manuals and documentation. It provides structured manual pages, Markdown-backed article content with title, slug, body, category or order, and timestamps, plus public list and detail routes and an admin CRUD surface. It was also designed for integration with Opifer's CMS.
- Is opifer/manual-bundle maintained or archived?
- The repository is archived, which means there are no fixes, no maintainer response, and no security patching. It also has very low adoption signals, such as 3 stars and 0 dependents, so there is little real-world validation. Do not adopt it as a production dependency.
- What are the security risks of using an old Markdown documentation bundle?
- The bundle includes an old bundled Markdown renderer, which creates a stored-XSS surface if help content is ever author-editable. The end-of-life Symfony 2 foundation also means no security response from the framework or bundle. In a Laravel rebuild, use a maintained Markdown renderer in safe mode with HTML sanitization.
- How do I migrate from opifer/manual-bundle to Laravel?
- Do not port the bundle; reimplement the pattern in Laravel. Export any existing articles to neutral JSON or Markdown first, mirror the schema in Eloquent, keep the body as raw Markdown and render at read time, rebuild admin authoring on Filament, Nova, or Blade, and use the old public routes as contract tests. Add a render-parity gate comparing old and new HTML before cutover.
- Should I build a custom Laravel documentation module instead of using this bundle?
- Yes, for a Laravel codebase a small first-party module is the lower-risk choice. The portable contract is small: an article model with slug, title, Markdown body, category or order, publish state, and timestamps, plus public read routes and admin authoring. That can be built on supported Laravel primitives in roughly one sprint or less.
- Does opifer/manual-bundle support authenticated admin authoring for help articles?
- The bundle includes an admin CRUD surface, but it is Symfony and Twig based and does not map to Laravel authentication or authorization. Decide early whether you need authenticated authoring or only read-only public help, because that changes build cost by roughly an order of magnitude. In Laravel, rebuild authoring on your existing admin tooling.
- What are alternatives to opifer/manual-bundle for Laravel documentation?
- The context recommends a small first-party Laravel module over this archived Symfony bundle. Use Eloquent for articles, league/commonmark for Markdown rendering, and Blade or Filament or Nova for admin authoring. If you evaluate other Composer packages, require active maintenance, Laravel version support, tests, and a security response process.
- How should I test a Laravel reimplementation of this manual system?
- Start with an export verification step using row counts and sample diffs so no article content is lost. Add golden-file tests that compare old and new rendered HTML on a sample of real articles; this is the go/no-go gate. Also test public route behavior against the old routes as a contract and verify sanitization against stored-XSS cases.
Weaver
How can I help you explore Laravel packages today?