LD3 — Content type selection

Overview

Ottili LD3 is the content automation module of Ottili ONE and is in Beta*. Before LD3 generates a draft, a content type* is selected. The content type decides which fields are required, whether source verification and approval are mandatory, whether SEO metadata is expected, and which channels the content later routes to.

Selection is not a cosmetic label: it drives validation, approval gates, and the type's channel strategy. That is how one source becomes the right content for the right channel — articles for WordPress, posts for social, copy for the newsletter.

The 7 registered content types

LD3 keeps a fixed type registry (LD3 Platform Plan v2 §10). Each type is a first-class object with required fields, validation rules, and a recommended channel list.

Product data for product_content comes from Ottili Shop / Shopping. Campaign Content is prepared by LD3; the actual ad management runs through the Growth / Ads system.

How selection works

The content type is set at the source of generation — typically in a topic's metadata or on the generation request. LD3 uses the type for type-specific generation (LD3-071): the AI generator receives a matching template hint, and the subsequent validation checks the type's required fields.

In LD3 preferences (ld3-preferences) you can store a content type focus* (content_type_focus). It shapes the default for recurring batches but does not replace an explicit selection per topic or generation.

Required fields and validation

Each type defines its own required fields. If one is missing, validation reports an error before the draft is passed on. Common rules:

• Title and body length*: news and product types have tighter limits than social or newsletter copy.
• Source verification*: only news_article strictly requires verified sources.
• SEO metadata*: most article types expect SEO title and description; for social and newsletter types it is optional.
• Product and campaign reference*: product_content and campaign_content bind to an object from the shop or campaign.

Approval and verification

LD3 publishing is draft/approval-first by default. Some types make approval a hard gate (news_article, product_content, social_content, newsletter_content, campaign_content); others can be approved without a review step (evergreen_article, local_guide). Every publish stays auditable.

Channel strategy

Each type recommends target channels. A package is routed in one step to the channels assigned to the type — provided those channels are connected in LD3. The available channels (WordPress, social accounts, newsletter, news) are described in the publishing channels article.

AI actions

Content type selection and generation can be triggered through LD3 AI actions under the ld3.* namespace — for example, generating a topic into a specific type and routing it to review. That enables recurring, automated content batches via Ottili AI or Flows.

Related articles

• LD3 Content Automation — the full pipeline overview.
• LD3 Topics and LD3 Topic Expansion — where the content type lives on the topic.
• LD3 Content Packages — one story, many channel assets.
• LD3 Publishing Channels — where packages are routed.
• LD3 Reviews and LD3 Source Verification — approval and verification before publish.
• LD3 Preferences — shape tone, language and content type focus.