Skip to content
Ileen Docs

Tutorial 3: Content Mode — Marketing & Social Media

What you’ll accomplish: Create a project briefing that captures your brand voice, then generate ready-to-publish social posts, long-form marketing copy, and a structured changelog — all consistent with your brand identity.

Time to complete: 5–10 minutes per content piece.

Prerequisites: An Ileen account with a credit balance.

Overview

Content Mode generates marketing materials and documentation for your products. Every agent builds on a central briefing that keeps all outputs consistent with your brand voice, audience, and key messages.

AgentWhat it does
📋 BriefingDefines your brand voice, audience, and key messages
📣 Social PostsGenerates platform-specific social media content
📝 General ContentCreates long-form copy: landing pages, feature descriptions, guides
🔍 Content ReviewChecks consistency and brand compliance; suggests improvements
📒 ChangelogGenerates human-readable release notes from your connected repositories’ commit history

Use the interactive demo to see Content Mode in action before you start.

Interactive Demo📝 Content
Step 1 / 5
📋Briefing●
›
📣Social Posts🔒
›
📝General Content🔒
›
🔍Content Review🔒
›
📒Changelog🔒
📋 Project Briefing
Product / Company name
Acme MarketPlace
Target audience
SME business owners and solo entrepreneurs in the EU
Brand voice
Professional but approachable. No jargon. Focus on ROI and time savings.
Key messages
Launch your online store in minutes. Connect with 50+ payment providers. Scale without hiring.
Save Briefing →
💡 Start by creating a project briefing — the AI learns your brand voice, target audience, and key messages. Every subsequent agent uses this briefing as context.

Step 1 — Switch to Content Mode

  1. Open the Ileen app and look at the mode selector in the sidebar footer.
  2. Click Content to switch mode.

Step 2 — Create a project briefing

The briefing is the foundation of everything Content Mode generates — it captures your brand voice, audience, and key messages. In Ileen the briefing is AI-generated from the inputs you provide; you don’t fill in each field manually.

  1. Click Briefing in the agent pipeline.
  2. Fill in the form:
    • Project Name — the name that identifies this content project (e.g. “My Company Blog”).
    • Description (optional) — a free-text paragraph describing your business, product, or service: what it does, who it’s for, what tone you want. The more detail you give, the more targeted the generated briefing will be (up to 4000 characters).
    • Reference Documents (optional) — drag-and-drop any files that describe your brand: pitch decks, existing marketing copy, style guides, press releases. The agent extracts text from them.
    • Repositories (optional, only when creating a new project) — connect Git repos so the agent can also learn from your codebase (e.g. for technical changelogs).
  3. Click Create Project & Generate Briefing (first time) or Generate Briefing (subsequent regenerations). The AI produces a structured briefing covering brand voice, audience, and key messages, which is then used as context for every other Content Mode agent.

Step 3 — Generate social posts

  1. Click Social Posts in the agent pipeline.
  2. Describe the post context: “Launch announcement”, “New feature: multi-currency support”, “Weekly product tip”.
  3. Ileen generates platform-optimised posts for:
    • LinkedIn — professional tone, engagement-oriented
    • Twitter / X — within character limit, hashtags included
    • Instagram — caption with hashtag set
    • Facebook — community-friendly tone, longer form allowed
    • Threads — conversational, short-form
  4. Each post respects your briefing’s brand voice and key messages automatically.
  5. Each post appears as a collapsible card — click Copy on any card to put that post on your clipboard.

Step 4 — Generate general content

For longer-form materials, use the General Content agent. Pick one of the supported content kinds — Email, Presentation, Newsletter, Blog Post, Press Release, Report, Commercial Proposal, Internal Memo, or Other — choose a tone, describe what you need, and click Generate.

Examples of what you can request:

  • “Write the hero section copy for our landing page”
  • “Write a 300-word feature description for the payments module”
  • “Draft an onboarding email sequence (3 emails) for new users”
  • “Write a press release for our Series A announcement”

The agent outputs structured, ready-to-use copy. You can follow up in chat to adjust length, tone, or specific sections.

Step 5 — Review and refine

The Content Review agent checks all generated content for:

  • Brand consistency — does the tone match your briefing?
  • Message alignment — are the key messages present?
  • Platform fit — is the LinkedIn post too short? Is the tweet too long?
  • Accuracy — are any claims potentially misleading?
  1. Click Content Review in the agent pipeline.
  2. The agent scans all generated content and presents issues as a prioritised list.
  3. Chat with the agent to apply fixes: “Apply all suggestions” or “Rewrite the LinkedIn post but keep the CTA”.
  4. Once all issues are resolved, content is marked Approved and ready to publish.

Step 6 — Generate a changelog

The Changelog agent produces human-readable release notes by reading the recent commit history of every repository connected to the content project.

  1. Click Changelog in the agent pipeline.
  2. Set Days Back — how far back to look in the commit history (1–365, default 7).
  3. Choose the Language — Italian, English, Spanish, French, or German.
  4. Click Generate Changelog. The agent reads commits from all connected repos over the selected window and categorises changes automatically:
    • ✨ New Features
    • 🔧 Improvements
    • 🐛 Bug Fixes
    • ⚠️ Breaking Changes (if any)
  5. The generated changelog is rendered as formatted Markdown. Use the Copy button to copy it to the clipboard.
  6. Past changelog generations are stored in the History list — click any entry to expand and re-read it, or delete entries you no longer need.

Generated changelogs are suitable for:

  • In-app “What’s new” panels
  • Email newsletters and release announcements
  • Public-facing documentation pages
  • GitHub / GitLab release notes

What’s next?