River Embed for FeedLand

What is this?

This is a WordPress plugin that displays a FeedLand river — a constantly-updated stream of news items from feeds a FeedLand user subscribes to — on a WordPress page or post.

FeedLand also has its own News Product feature, a whole standalone HTML page you deploy on your own server. This plugin doesn't use that; instead it fetches the same underlying river JSON directly from FeedLand's API on the server side (cached), renders it with its own template, and embeds the result on the page via an isolated iframe.

How to Use

1. Install and activate the plugin.
2. Adjust the plugin settings at Settings > River Embed: enter your FeedLand username and, optionally, a category to limit the river to feeds in that category (leave it blank to show everything the user subscribes to). Description, Image URL, and Template URL are optional — see "Customizing the template" below.
3. Add the [feedland-rivers] shortcode anywhere on your site to display the river.

Adding the Shortcode

Whether selecting a widget or a block, you will choose "Shortcode", then copy/paste this into the input:

[feedland-rivers]

You can also output the shortcode in your PHP templates like this:

echo do_shortcode( '[feedland-rivers]' );

Multiple rivers

The username, category and server attributes override the corresponding setting, so you can embed different rivers on different pages:

[feedland-rivers username="alice" category="tech"]
[feedland-rivers username="bob" server="https://myfeedland.example.com/"]

A bare [feedland-rivers] still uses the username/category/server configured at Settings > River Embed.

How it works

FeedLand doesn't offer a lightweight "just the river, sized to content" embed URL — its News Product pages (/newsproduct) are always full standalone HTML documents pulling in ~25 scripts/stylesheets (legacy jQuery, Bootstrap, a WebSocket connection, etc.), meant to be deployed as their own page rather than embedded inside another site's layout.

Instead, on each shortcode render this plugin:

1. Calls FeedLand's own JSON river API directly — getriverfromcategory (or getriver for "everything the user subscribes to") — server-side via wp_safe_remote_get(), cached in a transient (FEEDLAND_RIVERS_CACHE_TTL, 3 minutes by default) so we're not hitting FeedLand on every page view.
2. Renders items as sections in FeedLand's own reverse-chronological order (includes/render.php) — one section per batch the API returns, without merging or re-sorting, so the same feed can reappear further down if other feeds' items interleave chronologically — styled to match feedland.com's own river page (?river=true&...), no FeedLand front-end scripts involved at all.
3. Fetches a document template (see below) and drops that rendered content into it, then embeds the result via `