Quickstart

From an empty brand to a scheduled post. About 15 minutes, most of it spent connecting an account.

1. Create a content profile

Studio, then Content profiles, then New.

A content profile is your content identity: a name, an accent colour, your handle, a voice guide and your content pillars.

Fill in the voice guide properly. It is what every AI feature reads first, and a thin one produces generic output. Be specific and blunt:

Simple, direct, conversational English. No vocabulary I would not say out loud.
Banned: delve, leverage, game-changer, unlock, seamless, robust.
First person. If something failed, say it failed. No spin.
Hook in the first line. Short paragraphs. Concrete numbers over vague claims.

Pillars are the 3 to 5 themes you post about. For example:

A: build-in-public, what happened this week
B: technical takes, backed by something I built or broke
C: product value, spoken to the reader's problem
D: lessons and failures, the mistake first

Almost nothing works without this

The AI planner, the comment scan, carousel rendering, and every idea import need a content profile. If you skip this step you will get "No profile configured for this team yet" from all of them.

2. Fill in your persona

Studio, then Settings, then the Content tab.

Three fields: your niche, your audience, and what to avoid. These ground every AI feature, not just one.

There is an Interview me button that asks you tailored questions and fills the fields from your answers. It is faster than staring at three empty boxes.

3. Connect an account

Studio, then Settings, then Connections.

Start with Bluesky

If you want to see the whole pipeline work today, connect Bluesky. It takes two minutes with an app password, it publishes for real, and it syncs metrics.

Instagram is more capable but needs a Meta developer app. Threads and Facebook connect but cannot actually publish yet, pending Meta's review.

See Platform support for what each one can do.

4. Set your posting schedule

Studio, then Settings, then Content.

Set the posting timezone first. This is separate from wherever the servers run, and it is the one that decides when your posts go out.

Then add time slots per platform, for example Mon 09:10, Wed 09:10, Fri 17:30. These are the times the queue offers you when scheduling.

5. Get a first idea in

Three ways.

Type one. The quick-capture button in the top bar drops an idea into the Library without navigating away.

Mine your commits. If you write code, the CLI turns your git history into ideas:

npm install -g @postlyra/cli
postlyra init && postlyra login
postlyra mine --dry-run   # look first
postlyra mine

Research. Track a channel under Channels, wait for a sync, then generate ideas from an outlier video.

6. Promote it to a draft

Studio, then Planning, then the Library view.

Find your idea and click Promote. That creates a draft, optionally AI-written in your voice, and drops you into the draft editor.

Edit it until it sounds like you. This is the part nobody should skip.

7. Approve and schedule

In the draft editor, click Approve.

Approval is the gate. Until a draft is approved it cannot be scheduled, and there is no way around that.

Then Schedule: pick the connected account, pick a slot, adjust the caption for that network if you want. That creates a slot in the Queue.

8. Watch it go out

Studio, then Queue.

Your slot sits at pending until its time, then flips to publishing, then published.

Check the scheduler dot

Bottom of the sidebar. Green means the scheduler is running and due slots will publish. Red means it is stale and nothing will go out, however perfect your queue looks.

What next

• Core concepts — what each status means, and how failures behave
• Planning — the calendar, list and library views
• Automations — Instagram keyword replies
• Comments — drafted replies on other people's posts