Weave Code
Default Template Bundle Laravel Package
os2display/default-template-bundle
Provides the default template bundle for OS2Display, supplying standard screen templates and layout definitions for digital signage content. Integrates with the OS2Display platform to give administrators ready-to-use templates for building and displaying slides across screens.
Os2Display default template
Frequently asked questions about Default Template Bundle
- Is os2display/default-template-bundle a Laravel package?
- No. It is a Symfony bundle from the OS2display digital signage platform, shipped with Twig templates and bundle conventions rather than a Laravel service provider. There is no package auto-discovery, no config publish command and no Blade namespace, so composer require alone will not wire it into a Laravel app. In a Laravel project the realistic approach is to harvest the templates and CSS as reference material and port them to Blade.
- How do I install os2display/default-template-bundle?
- You install it with Composer, but registration happens the Symfony way, by enabling the bundle in your kernel or bundles configuration. There is no artisan-style install or vendor:publish step, and nothing in the repository documents a Laravel installation path. If your target is a Laravel application, expect to copy templates rather than activate the bundle.
- Can I use the OS2Display screen templates in a Laravel Blade application?
- Yes, by treating the repository as a design and asset source rather than a runtime dependency. Copy the Twig templates, convert the markup to Blade, and carry across the CSS and any dark mode approach you decide to adopt. Because templates and styles are the lowest-coupling artifacts in the stack, this works even if the bundle is never installed. The cost grows with the number of templates you maintain, so keep the ported set small and documented.
- Which Laravel versions does this bundle support?
- None officially. Nothing in the package, the release notes or the repository targets Laravel, and there is no compatibility matrix at all. Treat it as a Symfony and OS2display component and do not assume Laravel 10 or 11 support in any estimate.
- What PHP, Symfony and Twig versions does version 2.2.0 require?
- This is not documented in the release note, and there is no published compatibility matrix. Check the composer.json on the 2.2.0 tag before you plan any work, and confirm the minimum PHP, Symfony and Twig constraints. This is one of the open questions that should be closed before estimation.
- How is dark mode activated in version 2.2.0?
- The release note only says dark mode support was added via PR #27, so the activation mechanism is unclear. Three implementations are plausible: a prefers-color-scheme media query that works automatically, a class or data-theme attribute you must set and persist, or a CSS custom property token system that requires your overridden templates to be refactored onto those tokens. Read the PR diff before wiring any toggle, because the inert-feature failure mode is common here. If it is opt-in, it will look broken until you set the attribute or flag.
- Will upgrading from 2.1.x to 2.2.0 break my existing template overrides?
- There is a real risk, because dark mode pull requests frequently rename or restructure CSS classes. The release note is a single line, there is no changelog, and it does not state whether template markup changed. Diff the templates between 2.1.x and 2.2.0, and check whether your forked templates still match the current class names.
- Is os2display/default-template-bundle actively maintained?
- OS2display is a Danish public-sector digital signage platform, and the fact that an outside PR (#27) was merged is a mildly positive signal that community input is accepted. However, a single merged PR is not evidence of a release cadence. There is no changelog, no CI status and no stated semver or backward-compatibility policy, so verify steward status before depending on it long term.
- Should I run the bundle or port the templates into Laravel?
- Choose one explicitly and record the decision. Harvest is the right default for a single Laravel product: copy the templates, port Twig to Blade, and adopt the dark mode approach rather than the code. Coexist only makes sense if you are actually operating the OS2display platform, in which case the bundle lives in a Symfony signage service that your Laravel app talks to over HTTP. Ambiguity between the two is what generates wasted estimates.
- How do I test dark mode and ported templates for digital signage screens?
- Test on the actual player hardware and browser, since prefers-color-scheme support varies and lobby screens may not be set to dark at all. Confirm which activation mechanism 2.2.0 uses before you report the feature as working, because it may be silently inert without a toggle. For ported Blade views, add visual regression snapshots so class renames in future upstream releases are caught early. Also decide whether dark mode is even desirable for your signage context.
Weaver
How can I help you explore Laravel packages today?