I love how TweetDeck presents and lets you organize multiple columns of feeds of data so that you can massively increase your information density. I also love RSS feeds and want to help increase their usage as much as possible.
I created TopicDeck to help me organise and aggregate RSS feeds into an TweetDeck inspired layout.
TopicDeck today is a npm module on GitHub that you can use to quickly host. One of those instances is pwa.topicdeck.com which aggregates a number of Progressive Web App related feeds into eiter a deck format or a single master feed.
I'm quite proud of this project. The UI is plain and simple, but under the hood it does a number of interesting things:
- All of the logic is shared between the Server and the Service Worker. I believe it was the first web app to do that. There have been 'isomorphic' examples of sites before, but they mostly did the work in the frontend. TopicDeck moves the server logic closer to the user. To achieve this I had to abstract away some of the differences the Node and Web ecosystems, such as unifying around the WhatWG Streams implementation; and bring a simple Express like clientside router to Service Workers.
- The service worker does full template rendering. If the service worker has the cached data it will merge that into the response stream so that there is no need to run JS in the client to asynchronously fetch the data.
- It takes all the individual feeds and creates a master aggregration of the feed data. This allowed me to create decks of decks. Check out the GDE Deck which aggregtes all of the feeds of Google's Developer Experts program, pulling in our Web, Android and IoT GDE's feeds.
- The original version used CSS-Grid to layout the columns and stream data into the UI out of order. I.e, column 1 might come in 10s later.
- It waits for UI state changes using the MutationObserver API and when a column is added to the UI it starts a flow which fetches the latest feed data.
I don't imagine that this project will take over the world, but I find it very useful. It pioneered a new Service Worker rendering model, and it helps me keep up to date with the world.
About Me: Paul Kinlan
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.