Custom Views and RSS
StatiBeat supports audience-specific views and feed-based distribution.
Custom views are for audience-specific visibility. RSS feeds are for machine-friendly or feed-reader-friendly distribution. They solve different communication problems and work well together.
For a dedicated walkthrough of custom views themselves, read:
Custom views
From the public and admin codepaths, custom views currently support:
- creating a view against selected component IDs
- loading a view by short code
- retrieving view data
- requesting a magic-link style access token
- validating management tokens
- updating and deleting a view
- adding, removing, and transferring managers
- setting an alias in the admin UI
The current admin custom-view surface also includes:
- search
- stats cards
- per-view management
- manager administration
- component-scoped view editing
The admin UI for custom views includes:
- name
- description
- URL alias
- component selection
- manager management
The current management modal is where most of the depth lives: it allows editing the view definition, changing the URL alias, and managing view managers from one place.
These capabilities are visible in application/frontend/src/pages/admin/CustomViewsManagement.jsx and the corresponding scoped routes in application/backend/cmd/server/routes.go.
RSS feeds
RSS feed administration currently includes:
- listing feeds
- viewing feed statistics
- deleting a feed
- invalidating a feed cache
- copying feed URLs in XML or RSS form
The current admin RSS surface also shows:
- feed statistics
- active feed counts
- format counts
- access counts
- last accessed date
- configured content types
- max item and max age limits
The backend also exposes public feed creation and management routes, including token-based management flows and XML/RSS endpoints.
The cache invalidation action is especially useful when you want to force a fresh read after changing the feed or after recent page activity.
How custom views and feeds fit together
Custom views are interactive and audience-facing. RSS feeds are passive and syndication-focused. A team might use custom views for customer portals or scoped links, while using RSS for operational consumers, dashboards, or subscriptions in feed readers.
The Terraform provider currently exposes RSS feeds as a read-only data source, not as a managed resource. This matches the provider’s documented scope and implementation in terraform-provider/internal/provider/provider.go.