Blog

The sources a draft is allowed to use

Settings lock the product to one URL, then read the changelog, the blog, and the pages you choose. Drafts stay on that site until you add another product.

A draft is only as good as the pages it was allowed to read. Settings is where that boundary is drawn: one product URL, the people you are writing for, the voice, and the three places new sources can come from. Change those, and the posts queue changes with them. Leave them sloppy, and every draft inherits the sloppiness.

The screen is ThinkReview’s. The same form is what you get after you paste a URL and build the pack.

The URL stays put

The product URL is locked once drafts exist, so every draft stays about this site. Rebuilding the pack refreshes the name and the feeds from that URL. It does not quietly retarget the workspace at a different product. A second site is a second product, with its own queue, its own channels, and its own search property.

That lock is what keeps a busy week honest. You can have a marketing site and a docs site. They should be two products if you intend to post about both. One workspace aimed at whichever URL you edited last will mix their changelogs, and the drafts will sound like neither.

Product settings with a locked URL, audience and voice chips, and release notes, blog, and website page sources
Audience is who the draft is for. Voice is how it should sound. The three cards under that are the only feeds drafts can use.

Who it is for, and how it should sound

Audience is up to three. ThinkReview’s are developers, DevOps, and SaaS founders. A draft for those people can mention a pull request and a self-hosted install. A draft for restaurant owners should not, and it will, if you leave “developers” selected on a product that is a reservation book.

Brand voice is one choice. Clear and technical. Warm and plain. Direct. Pick the one you would actually send. A voice chip you do not recognize in your own writing will show up as a paragraph you delete every time, which means the chip is wrong.

Language follows the same idea. Drafts are written in the default language. A secondary language is there for readers who need that version. Set it when you will really post in both. An unused second language is another pile of drafts.

Three ways a source gets in

Under the voice, three cards match the three tabs on the posts queue.

Use the cards by the shape of the company:

Edit in settings when a feed URL changes. The queue labels the saved source on each tab, so you can see which feed a row came from before you generate anything. Build pack when you want the name, the description, and the detected feeds refreshed from the locked URL. Then go back to the queue and open one source.

More notes

All notes

Legaltech where firms already talk

Law-firm, contract, and compliance tools now map to ALCA, Docusign, and Acrobat Sign — plus the legal subreddits, not a generic SaaS board.

Restaurant software in kitchen forums

QR menus, POS, and kitchen displays belong on ChefTalk. ProductPost 360 keeps restaurants separate from traveller forums.

Measure the rooms that send people

Communities keep posts that help. Track which rooms send signups, and draft each one from the release instead of rewriting it by hand.

Poker tools in player forums

Poker and betting products belong on Two Plus Two and the study forums. Those player rooms are one post, not a release feed.

Listings you submit once

Directories want a name, a tagline, and a maker comment. Draft them from the pages you already published, submit once, and mark the listing live.

Community apps where people already gather

Social, dating, and community apps are not marketing tools. ProductPost 360 gives them their own pack and their own rooms.