FeedFlow - RSS Aggregation & WordPress Publishing Platform

The Challenge

I was tired of copy-pasting roundup items into WordPress by hand. Multiple feeds, inconsistent HTML, wrong attribution half the time. I wanted one screen to skim items and push them to drafts or live posts without leaving the browser.

The Solution

FeedFlow aggregates feeds into a single dashboard. Mapping rules line up feed fields with custom post types on the WordPress side. Publish or save draft in one action through the REST API.

Parsing runs in the client so the UI stays responsive. PrimeVue plus Tailwind handled the dense tables and forms without reinventing every primitive.

Photo by Christopher Gower on Unsplash

Technical Architecture

Vue 3 SPA talking straight to WordPress and feed endpoints. Vite for dev speed. Composition API kept fetch, parse, and publish steps separated.

RSS and Atom formats differ more than you'd think. Parser logic had to tolerate broken enclosures and odd date fields. CORS blocked direct fetches from plenty of feed hosts, so I added a small serverless proxy. That was the annoying week of the project, not the Vue UI.

My Role & Contributions

I owned architecture and implementation. Decoupled fetch, normalize, and publish so each piece could fail without corrupting the rest. UI work was PrimeVue components with Tailwind spacing. Proxy design avoided exposing API keys in the browser while still getting feeds through.

Challenges & Learnings

Browser security models bite hard on RSS. The proxy pattern fixed most cases. Daily use cut curation time a lot; batching 50 items stopped being an afternoon chore. People who tried it mentioned the UI staying calm under volume, which was the goal.

Impact & Results

Roundups that took hours dropped to minutes for me. If your team still copies from feeds into WordPress manually, I can shape something like this for your post types and fields. Contact or see other projects. Replies typically within 24 to 48 hours from Thessaloniki.