Weave Code
Nova Rss Card Laravel Package
beyondcode/nova-rss-card
beyondcode/nova-rss-card is a Laravel Nova card that displays RSS feeds directly on your dashboard. Add a feed URL to show recent posts in a clean, customizable card, giving teams quick at-a-glance updates without leaving Nova. Simple setup and customization make it a handy way to keep your team inf...
A Laravel Nova card.
Frequently asked questions about Nova Rss Card
- What is beyondcode/nova-rss-card and what does it do in Laravel Nova?
- beyondcode/nova-rss-card is a lightweight Laravel Nova dashboard card that fetches an RSS or Atom feed and renders recent entries as a clean, customizable tile. It is designed for at-a-glance updates such as blog posts, changelog entries, or news without leaving Nova. It owns no application logic, middleware, or migrations; it sits at the presentation edge of the admin panel.
- Is beyondcode/nova-rss-card compatible with the latest Laravel Nova versions?
- Do not assume compatibility. The only release is 0.0.1, published on 2018-08-23 and labelled experimental, and the repository is archived. That timing aligns with Nova 1.x and Laravel 5.x-era card conventions, so installation against a current Nova major is unverified. Because Nova is not on Packagist, a real compatibility probe requires a Nova license and access to the private Nova repository.
- How do I install and register the Nova RSS card?
- Installation follows Nova's standard card pattern: require the package with Composer and register the card in your Nova dashboard cards array. The package provides a simple fluent API for setup, so you can configure the feed and display options in one place. If you are on a modern Nova major, treat the install as a probe rather than a guaranteed drop-in.
- How do I configure the RSS feed URL and item limit?
- The card is configured with a feed URL and a configurable item limit, plus an optional cache duration. The fluent API is intended to keep that setup short and readable inside your dashboard registration. Exact method names should be confirmed against the package source, since the release predates current Nova documentation.
- Does the card support Atom feeds as well as RSS?
- Yes. The package is described as working with both RSS and Atom formats, so you can point it at a blog feed, changelog feed, or news source. The card renders recent entries from either format in the same tile. Feed parsing is still external XML input, so validate behavior with your real feed before relying on it.
- How does caching work for the RSS card, and can I change the cache duration?
- The package advertises built-in caching with a configurable cache duration, which is useful for avoiding a fetch on every dashboard load. However, the TTL, cache key strategy, and fail-open versus fail-closed behavior are not documented in the overview. Verify those semantics in the source, because a stale cache that silently misleads an operator is the realistic failure mode.
- Is beyondcode/nova-rss-card still maintained, and what are the risks of using an archived package?
- It is archived and effectively unmaintained: one experimental 0.0.1 release from 2018 and no upgrade path for future Nova majors. Adoption therefore transfers the maintenance obligation to your team. The license is permissive MIT and the scope is small, so the worst case is cheap: fork it or rebuild the card.
- Can I display or hide the feed title and item publish dates?
- Yes. The card supports an optional feed title and optional date display, so you can choose whether operators see the source name and publish dates. That makes it easy to keep the tile compact or add context for release notes and status updates. Confirm the exact option names in the package source before wiring them into a shared dashboard.
- Are there security concerns with rendering external RSS feed content in Nova?
- Yes, and they are worth naming. Feeds are externally controlled content, so XML parsing raises XXE concerns and rendered titles or descriptions raise XSS concerns, and a Nova admin session is a high-value target. Outbound fetching also raises SSRF if the URL ever becomes admin-editable rather than developer-set in config. Sanitize rendered feed HTML and keep the URL in code or config.
- What are alternatives if the package doesn't work with my Nova version, and how hard is it to reimplement?
- If the card does not work with your Nova major, you have three practical paths: fork and patch it, replace it with a maintained RSS card, or reimplement it as a small custom Nova card. The assessment puts a reimplementation at roughly one engineer-day, which removes the ownership question entirely. Because the card is additive and has no migrations, swapping it later is a one-file change behind the same config key.
Weaver
How can I help you explore Laravel packages today?