- How do I install ysfkaya/filament-shiplog in a Laravel app?
- Require the package with Composer, then register the shiplog page in your Filament PanelProvider so it appears in the admin navigation. You can optionally publish the config and views if you want to customize the timeline. The integration is presentation-only, so there are no jobs, queues, migrations, or external credentials to configure out of the box. A Filament-fluent developer can typically wire it up in well under a day.
- Does filament-shiplog work with Filament v4 or only Filament v5?
- The package targets Filament v5 and has a hard dependency on that major version. There is no documented v4 compatibility path, so installing it on a Filament v4 panel is not supported. Since Filament v5 is itself a young major release, plan your upgrade cadence for both packages together.
- Where should I store the changelog entries that shiplog renders?
- The package renders entries but does not dictate the source of truth, so you choose between markdown in the repo, a published migration and model, or an external CMS. Each option implies a different authoring owner, review workflow, and backup story. Decide this deliberately before rollout, because an unowned content source tends to drift. Entries carry version and date metadata plus markdown body content.
- Can I render the shiplog timeline outside the Filament admin panel?
- Yes. Alongside the native Filament page, the package ships Blade components, x-shiplog and ship-log, that render the animated release-notes timeline anywhere in your Blade views. That makes it viable to show the same changelog on a marketing or customer-facing frontend. Note that the component is class-based for theming and assumes Tailwind and Alpine in the host page.
- Is the Filament shiplog page protected by policies or authorization?
- There is no evidence in the package of policy gating on the Filament page or of draft and unpublished entry suppression on the public Blade component. Treat authorization as your responsibility and verify behavior in your own panel before exposing the page to clients or anonymous visitors. A leaked internal deprecation notice or unreleased feature mention is an incident rather than a cosmetic bug. Gate the page explicitly if your audience is not fully internal.
- Does filament-shiplog support dark mode?
- Theme handling is class-based only: theme set to class follows the dark class on the html element and nothing else. If your frontend resolves system preference with a media query, the timeline can render incorrectly. Version 0.2.0 fixed a dark-mode defect where the Filament page showed light text on a light background under OS dark preference, which shows this path has had limited testing.
- How do I customize the shiplog theme and styling?
- You can publish the views and config and override the component theme, but theming is class-based rather than token-based. Version 0.2.0 fixed an issue where the Blade component did not forward attributes, which had silently broken the documented theme override. Conflicts between Tailwind preflight, the animation layer, and your host design system are not proven, so budget a short design QA pass.
- Is filament-shiplog production ready and actively maintained?
- It is pre-1.0 software with a single maintainer, a small star count, no dependents, and a single release line, so there is no meaningful production adoption to borrow confidence from. Treat breaking changes as the norm and pin the exact version in composer.json. There is also limited public evidence of CI or test coverage, so validate the behavior you depend on yourself. It is best suited to low-risk, reversible presentation use.
- Does filament-shiplog support RSS feeds, JSON output, localization, or scheduled publishing?
- None of those capabilities are documented in the package, which focuses on rendering a versioned, dated markdown timeline. If you need feeds, translations, or future-dated entries, plan to build them around the package or in your own data layer. Confirm current behavior against the source before committing to a roadmap that depends on them.
- What happens to my shiplog page when I upgrade Filament?
- Because the package hard-depends on Filament v5, every Filament minor bump becomes a joint upgrade you need to test together. Pin both versions and run your panel through a smoke test after each upgrade, since upstream changes propagate straight into the page and component output. The 0.2.0 fixes for dark mode and attribute forwarding illustrate the kind of divergence a narrow QA matrix produces.