Bringing the content workflow into one workspace.

The work around writing a caption

Creating social content involves more than writing a caption. There is planning, choosing a platform, organising media and reviewing what comes next. I used this project to explore how those steps could sit together in one application.

The current application surface

The Nuxt application has a dashboard, calendar, media area, account management, inbox, analytics and a post-composition screen. Its backend includes account connection and disconnection routes, settings and authentication callbacks for social platforms. Pinia manages application state and Supabase supports the account layer.

OAuth is one boundary; publishing is another

There are connection and disconnection handlers, settings endpoints and social-platform authentication callbacks. Those establish useful integration surfaces. The composer screen, however, still has draft and schedule controls without a complete publishing path behind them.

A reliable scheduler would need durable jobs, token-expiry handling, retries and a clear record of whether a provider accepted the post. Those are the design questions I would tackle next. They are not implemented capabilities I can infer from a calendar view or a dependency list.

A schedule button is not a scheduler

It is important to separate the product idea from the finished behaviour. The composer has draft and schedule controls, but the inspected screen does not yet wire those buttons into a complete publishing workflow. The documentation also describes AI captions; that is not enough evidence to claim the full feature is working.

The milestone is one complete publishing path

This is an interface and integration project in progress. The next useful milestone is a reliable end-to-end path from composing a post to a verified platform action—not simply adding another dashboard panel.