Resurface evergreen blog posts for another social push

I want an app for working through our back catalog of blog posts and deciding which evergreen articles deserve another push on social. It is a review desk, not a scheduler. Nothing runs on its own. I open it, look at what has gone quiet, and decide by hand what to requeue.

The main view is a table of published WordPress articles, loaded with WordPress List Posts filtered to published status. Columns: title (linking to the live article), publish date, category, last promoted, and a state chip reading Never shared, In cooldown, or Ready. Paginate through the archive and let me sort by publish date and by time since last promotion.

Filters across the top: category, tag, and date range, plus the three I reach for most as one-click presets: never shared, not shared in the last 90 days, and by category. WordPress List Posts supports filtering by status, category, tag and date, so push those down into the call wherever you can. Note there is no separate operation for listing categories or tags, so build the filter options from the category and tag values present on the posts you have already loaded.

The last promoted column is the load-bearing piece of this app. Whenever this app queues a reshare it tags the Buffer post with the article slug, so the lookup is Buffer List Posts filtered by that tag, taking the most recent match. For anything shared before this app existed, fall back to scanning Buffer post text for the article URL. Treat the URL match as a backfill path only. The slug tag is the real index. Compute the whole slug-to-last-promoted map once per refresh and reuse it across rows rather than making a call per article.

Cooldown rule: any article promoted within the last 30 days is greyed out and cannot be selected, with the date it was last promoted shown on hover so I understand why. Make that window configurable, and give me a toggle to show or hide cooled-down rows.

Selecting an article opens a compose panel. Pull the available channels from Buffer List Channels. Draft a fresh caption per channel rather than reusing the original headline or any caption used before, because identical repeat copy is exactly what makes recycling read as spam. Show the captions previously used for this article, taken from the tagged Buffer posts, right there in the panel so both I and the drafting step can deliberately steer away from repeats. Every caption stays editable before it goes out. Include an optional angle selector (straight resurface, seasonal, or a throwback framing) that changes how the caption is written.

Before anything is queued, call Buffer Get Daily Posting Limits for the selected channels on the target date. Any channel already at its cap for that day is skipped, shown clearly as skipped with the reason, and not attempted.

Queue the approved captions with Buffer Create Post, one per channel. Always include the article slug in the post tags. That tagging is what makes the last promoted column work at all, so it is mandatory on every post this app creates, with no exceptions.

Save for later files the drafted caption as a Buffer idea using Create Idea, with the slug included as a tag, and then confirms it saved. Important constraint: there is no operation to read ideas back, so do not build any view that lists or manages saved ideas. Push it to Buffer, confirm, and stop there.

On pulling back a queued reshare, work within a real limitation: Buffer exposes no delete operation and no update operation here, so the app cannot cancel or edit a queued post itself. Instead, keep a record of everything the app queues (article slug, channel, scheduled time, and the post id Buffer returns) and show a Queued state on the article row with a direct link through to that post in Buffer, where I can edit or remove it. Do not put a Delete or Edit button in the app that cannot actually do the thing it promises.

Buffer exposes no analytics or engagement data, so do not attempt to rank articles by social performance and keep any engagement claims out of the interface. Rank and sort only by publish date, category, and time since last promotion.

Remember my filter and sort selection between visits. The record of what has been queued is shared across the workspace, so a teammate opening the app can see what was already sent back out and does not double promote the same article.