- How do I install michaelmannucci/verseoftheday in a Laravel or Statamic app?
- Install it with Composer using composer require michaelmannucci/verseoftheday. Then publish and review any package configuration so you can set the Bible version explicitly instead of relying on the default. In Statamic, enable or configure the dashboard widget as described in the package documentation. Run your existing test suite after installation to confirm the widget and any service bindings load correctly.
- Which Laravel and Statamic versions does verseoftheday support?
- The package is intended for Laravel applications and adds a Statamic dashboard widget, so check its composer.json and README for the supported Laravel, PHP, and Statamic version matrix. Version support can change between releases, especially when new Bible version features are added. Confirm compatibility in a staging branch before upgrading production. If your app runs an older Laravel or Statamic release, verify support before adopting v1.1.0.
- How do I change the default Bible version from NIV?
- v1.1.0 introduces Bible version support with NIV as the default. Publish the package config and set the default version key explicitly rather than depending on the package default. Confirm the exact version identifiers the package accepts before deploying. If your application needs per-user or per-request versions, plan to pass version context through your own models or request flow.
- Which Bible translations or versions are supported?
- The v1.1.0 release adds Bible version support, but the available translations depend on how the package sources scripture content. Check the documentation and config for the list of supported version identifiers. Confirm how invalid or unavailable versions are handled, including whether the package falls back to NIV. Do not assume every translation is bundled or licensed for distribution.
- Can I use the verse of the day outside the Statamic dashboard, such as in views, APIs, or scheduled jobs?
- The package is described as offering a configurable way to fetch and display the verse of the day in views, APIs, or scheduled jobs, in addition to the Statamic dashboard widget. Review the public API or service bindings to see how to request a verse programmatically. Make the Bible version explicit in those calls if multi-version support matters. Cache or schedule fetches appropriately so you do not add unnecessary overhead.
- Is NIV text licensed for distribution in this package and in my application?
- NIV text is copyrighted, so licensing is a real production concern. Confirm that the package does not ship unlicensed Bible text and that your intended use has appropriate permissions. If translations are fetched from an external service, review that provider's terms as well. Document the licensing obligations for your team before rollout.
- Does v1.1.0 introduce breaking changes, migrations, or cache invalidation concerns?
- Treat v1.1.0 as a minor feature release but validate the new NIV default in staging because default behavior changed. Run Composer update in a branch, publish and compare config, review any migrations, and check whether cached content is keyed by Bible version. If your app stores rendered scripture or version metadata, add explicit version context where needed. Clear or warm caches after changing the default version.
- How should I cache or optimize verse of the day requests when supporting multiple Bible versions?
- Cache entries should be keyed by both Bible version and date or reference so that changing versions does not return stale NIV content. Avoid fetching or rendering all translations unless your application actually needs them. Monitor external API calls if translations are retrieved remotely. After changing the default version, clear relevant caches and verify fallback behavior for unavailable versions.
- How do I test the verse of the day package in my application?
- Install the package in a non-production branch and run your existing test suite to catch service-provider or widget registration issues. Publish the config and assert that your explicitly configured Bible version is used. Test invalid or unavailable version handling and confirm the dashboard renders as expected. If the package calls an external translation source, fake or stub those calls in tests.
- Is this package actively maintained, and what alternatives should I consider?
- Check the GitHub repository and Packagist release history for recent commits, open issues, and supported Laravel and PHP versions before adopting it. Alternatives include integrating a Bible API directly, building a small custom Statamic widget, or using a broader scripture package if you need more translations or search features. For production, confirm the translation source, licensing, and fallback behavior rather than relying on the default NIV setting.