What Blogged is

Blogged runs the content engine behind a SaaS blog, from research and topic selection through drafting, images, internal links and publishing.

Blogged is a blog that runs itself for a software product. You describe the product once, approve a strategy, and the platform researches topics, writes drafts, sources or generates images, links posts to each other, and publishes to a blog it hosts for you.

The part worth understanding before anything else is that Blogged is not a text generator with a publish button attached. It is a pipeline with a review gate at every stage, and you decide how many of those gates stay open.

The pipeline#

1. 1
   Evidence

   Everything starts from what is true about your product. A scan of your website, a written description, or files you upload. Nothing downstream runs until there is enough evidence to work from.

2. 2
   Strategy and directions

   The evidence becomes a strategy: who the audience is, what the product does, and a set of Content Directions. A Direction is a lane the blog writes in, and it carries its own approval policy.

3. 3
   Topics

   Directions produce Topics: specific articles worth writing, each bound to a Direction and to a keyword. Topics are approved before anything is written against them.

4. 4
   Drafts

   An approved Topic becomes a Post. Research runs, the article is written against your Knowledge Engine so claims trace back to real sources, images are placed, and internal links are proposed against destinations that actually exist.

5. 5
   Review

   A Post sits at whatever gate its Direction requires. Some Directions publish on their own, some wait for a review, some wait for you specifically.

6. 6
   Publication

   An approved Post is scheduled and published to your blog, with its sitemap, metadata, structured data and internal links in place.

What you actually operate#

Four things carry most of the product, and the rest of this documentation is organised around them.

What it will not do without you#

This is worth stating plainly, because it is the difference between an automation you can leave running and one you cannot.

• Nothing publishes until an owner or admin activates Autopilot on the Project. Creating a Project does not start it.
• Every Post still has to satisfy its Content Direction's approval policy, no matter which Autopilot mode is running.
• Approving a Direction for automatic publication is a decision you make per Direction, not a global switch.

Where things live#

Blogged has three surfaces you will use, on three addresses.

Your blog is a real hosted site rather than an export. It has its own theme, navigation, search, sitemap and analytics, and it can serve from a custom domain you control.