Back in August I released a WordPress plugin for showing a FeedLand river — the stream of items from the feeds a FeedLand user subscribes to — on a WordPress page or post. As of yesterday it's officially published on the WordPress.org Plugin Directory:
https://wordpress.org/plugins/river-embed-for-feedland/
That means you no longer need GitHub at all. From your site's dashboard:
[feedland-rivers] shortcode on a page, post, or widget.Everything from the original post still applies: it fetches the river server-side and renders it in a sandboxed iframe, so it can't leak feed content into your theme and your theme can't clobber its styling. No third-party fonts or scripts. You can show more than one river with the username, category, and server shortcode attributes — see the live example I've had running since August.
Bugs and feature requests welcome on GitHub issues.
I've released a WordPress plugin that shows a FeedLand river on a page or post: feedland-rivers.
Drop the shortcode `[feedland-rivers]' onto a page, point it at your FeedLand username in the settings, and it fetches the river JSON server-side and renders it in an isolated iframe. No FeedLand front-end scripts, no third-party fonts or stylesheets beyond an optional favicon lookup. Here is an example.
You can also show more than one river on a site by overriding the username, category or server per shortcode instance, e.g. '[feedland-rivers username="alice" category="tech"]'.
It's not on the WordPress.org plugin directory yet. Grab the zip from the latest release and upload it via Plugins > Add New > Upload.
I'd appreciate beta testers. Let me know in the issues if something looks wrong or the instructions are unclear.
I took a quick look at blurt, the new WordPress short-form blogging theme available on WordPress.com.
It's a theme, just like Baseline is a theme. Themes can alter the behavior of WordPress in almost any way imaginable. It's still just a theme, so if Blurt is not using too much WordPress.com magic, it should be able to used on a self-hosted site.
The artificial 500-character limit is clunky. The compose box simply is disabled if there are too many characters. If you edit the post in the WordPress dashboard, when saved extra characters are silently dropped.
With WordLand I can post 600 characters, and they don't get cut off. If I try to edit that, the save fails. It's an early version, Blurt doesn't know how to handle posts coming from outside its UI.
I'm not sure why everyone thinks a character limit is a defining feature of social media. That should be up to the writer, not the platform. It should be a threshold, not a wall. micro.blog seems to handle this well (at 300 characters the UI show a title field you may choose to use or not).
All in all, it's a cute idea, and I look forward to see how it develops. (Sorry for the fart joke title.) (Actually I'm not sorry. 😃)
It's been a while since we checked in here, so here's what's going on with the Baseline theme.
Upcoming changes will include:
I've published a minor update v0.1.5 to the Baseline theme. It now shows a minimum number of posts on the home page, even if you haven't written any posts in the past two months.
Now that linkblogs have been added as a feature to WordLand, we're thinking about how best to display them with the Baseline theme. I've put up a prototype of a linkblog in WordPress to experiment with the layout. (The prototype gets it's data by polling the RSS feed once an hour rather than from WordLand, but the basic idea is the same.)
I'm trying out a new logic for the home page. Instead of using infinite scroll to eventually show all posts, we're showing only the posts for the current and previous month, just like Scripting News. We don't link to anything older, since old news is no longer news, and good older posts will have links from elsewhere.
There will be an option to show the traditional WordPress pagination links to older posts for those who prefer that behavior.
It's nice to have the baseline around, because now I have something to match the presentation of H3's with. The next version of WordLand will have that worked out.
Had to back out of the Styles panel of the Settings command, I did it way too fast, each feature it added had to be tested in this very particular context.
The context is Medium Editor, Markdown and WordPress. None of which were designed to work with each other. We're lucky to have a core subset that works, enough to support writers.
I think to get a really complete editor, you have to start with Markdown or HTML and work it out with WordPress.
I have made the style of H3 agree with the style of in the Baseline theme.
My answers to the questions from May 4, 2025:
Other problems I've noticed
like this isn't very distinguishable from normal text (issue on GitHub).This is a list of things that I want to try out on the new baseline theme.
Here are five great MLB first basemen and what made each of them especially interesting:
Lou Gehrig – The "Iron Horse" of the Yankees, famous for his durability, humility, and tragic early retirement due to ALS, which now bears his name.
Albert Pujols – A modern legend known for his all-around hitting, consistency, and longevity, finishing with over 700 home runs.
Willie McCovey – Towering lefty slugger for the Giants, feared for his monstrous power and iconic presence in the batter’s box.
Keith Hernandez – Brilliant defensively, redefining how first base was played with range, quickness, and leadership—also a memorable personality.
Frank Thomas – “The Big Hurt” dominated the ‘90s with his intimidating size and incredible hitting eye, combining power with patience.
Thanks for listening, this has been a test!
I've applied the single column layout proposed by Christy Nyiri. I personally think it looks fantastic.
Here are some WordLand styles.
This is a block quote. (This doesn't seem to be styled yet.)
Bold, italics, underlined (hmm, it's not underlined).
An ordered shopping list:
Notes as an unordered list:
Here's a paragraph that appears under the unordered list.