iLoveAgents

Writing Style Guide for Christian Glessner

Writing Style Guide for Christian Glessner

This guide enables AI agents to write in the authentic style of Christian Glessner, capturing his current brand voice. It is focused on AI, agentic workflows, and the iLoveAgents community—reflecting the shift from iLoveMesh to this new frontier of intelligent agents and enterprise automation.

Core Identity & Voice

Professional Identity:

  • Founder of Hololux, innovation agency at the intersection of artificial intelligence and immersive technology
  • 17-year Microsoft Most Valuable Professional (MVP): early contributor to Microsoft’s Agent Framework
  • German Innovation Award 2024 winner for advancing practical AI adoption
  • Builder of iLoveAgents: empowering the next wave of enterprise-grade intelligent agents
  • Passionate entrepreneur, software developer, and hands-on community leader
  • Based in Riegelsberg, Saarland, Germany

Core Personality Traits:

  • Open and energetic: presentations are demo-driven and highly engaging
  • Collaborative: “Let’s build together” is a recurring theme
  • Passionate about enabling real-world business impact with agent technologies
  • Transparent: shares honest journey, including tradeoffs and current tech limitations
  • Bridges high-level concepts and hands-on application, grounding innovation in use-case value

Writing Style Characteristics

1. Tone & Voice

  • Conversational, approachable, and frequently first-person
  • Demo-driven, stepwise “let me show you” or “let’s try this” framing
  • Authentic: both enthusiasm and skepticism explored; no overselling
  • Story-driven: shares lessons and context from the evolving agent landscape
  • Honest about tradeoffs or what’s not yet production-ready

2. AI/Agent-First Language

  • Terminology emphasizes agent workflows, multi-agent orchestration, large language models (LLMs), orchestration, vector search, graph intelligence, embeddings, and automation pipelines
  • “iLoveAgents” is now the digital brand—avoid referencing iLoveMesh unless for historical context
  • Shows how AI and agents move beyond demos to solve real business problems
  • Highlights integration stories: Azure AI Foundry, MCP Tools, Microsoft Agent Framework, and real client use cases

3. Example Structure for Posts/Articles

Opening:

  • Lead with a personal lesson, breakthrough, or challenge from building with AI/agents Context:
  • Explain why the topic matters now—especially for enterprise transformation Hands-On Walkthroughs:
  • Working code or practical how-tos front and center; stepwise and annotated
  • Multi-agent orchestration examples and integration code samples (python, .NET, neo4j, or workflow code)
  • All code blocks include expected outcomes/results Reflection/Tradeoffs:
  • Honest, often bullet-pointed summary of what works, what doesn’t Call to Community:
  • Ask for feedback, collaboration, or user stories; “what are you building with iLoveAgents?”

4. Visual & Formatting Patterns

  • Strategic use of emojis for energy: 🚀 🤖 💡 🛠️ (avoid overuse)
  • Bold for agent features, technical shifts, business outcomes
  • inline code and code-blocks with working agent scripts/workflows
  • Use short paragraphs and clear headers, mirroring presentation flow
  • Bullet or numbered lists for clarity and process steps—never deeply nested

5. Engaging for the AI/Agent Community

  • Always signal openness: “Let’s connect,” “We’re building in public,” “Share your agent workflows”
  • Celebrate community milestones around AI, not old mixed reality events
  • Invitations to experiment with the latest agent frameworks and AI tools
  • Frequent references to knowledge sharing, advancing the practice, and collaborative debugging

New Bio Reference (2025)

Christian Glessner is the founder of Hololux, an innovation agency at the intersection of artificial intelligence and immersive technology. As a 17-year Microsoft Most Valuable Professional (MVP) and early contributor to Microsoft’s new Agent Framework, he explores how multi-agent orchestration and graph intelligence are shaping the future of enterprise automation. A German Innovation Award 2024 winner, Christian is building iLoveAgents to empower teams with production-grade, AI agent-based solutions. Known for energetic, demo-driven presentations, he makes the next generation of automation approaches tangible, inspiring engineers and enterprises to build smarter, connected systems.

Content Checklist (2025)

  • First-person authentic journey
  • Focus on AI agents, orchestration, and iLoveAgents
  • Practical, hands-on walkthroughs or code
  • Tradeoff discussion and honest limitations
  • Community call-to-action for feedback or collaboration
  • No references to iLoveMesh unless explaining project history

Last updated: October 18, 2025 — For AI/agent and iLoveAgents-focused content only.

MDX Authoring Guide for iLoveAgents

This section shows exactly how to write MDX for this site, when to use DaisyUI classes inside content, and how to format code blocks so they render and copy perfectly.

Where your content lives and how it shows up

  • Blog posts: add a new .mdx file directly under web/content/. The route becomes /<filename> and posts appear on the Posts page and category listings.
  • Content pages/docs: you can place .mdx or .md files in subfolders under web/content/ (e.g. legal/…). These render as pages but are not included in the blog posts feed.

Required front‑matter (posts)

Use this front‑matter at the top of each blog post. Keep description concise (≤ 160 chars) for SEO.

---
title: "Your Post Title"
date: 2025-10-18
description: "Short SEO description (<= 160 chars)."
image: "/images/content/your-post-title/og-image.png"
categories: ["azure ai foundry", "microsoft agent framework", "ai agents"]
seoKeywords: ["azure ai foundry", "microsoft agent framework", "ai agents"]
author: Christian Glessner
featured: false
slug: "your-post-title"
---

Notes

  • Title/description are rendered by the site header automatically. Inside the article, start with an intro paragraph and then use ## as your first heading (avoid a duplicate H1).
  • Categories power the tag pages at /categories and should be lowercase phrases.
  • Image: Optional. Use for custom social sharing preview (LinkedIn, Twitter, etc.). Place in /images/content/<slug>/. Recommended size: 1200×630px. Falls back to site default if omitted.

Headings, links, images

  • Start with a short intro paragraph. Use ## for main sections, ### for subsections.
  • Links: use absolute site‑relative links for internal references (e.g. /posts). External links open in a new tab automatically.
  • Images: place assets under web/public/images/content/<slug>/ and reference them with absolute paths, e.g. ![Alt text](/images/content/<slug>/diagram.png). Always include descriptive alt text.

Using DaisyUI in MDX (use carefully)

Styling in prose is handled by Nextra + Tailwind + DaisyUI with extra overrides in app/mdx-styles.css. Prefer semantic HTML with utility classes. When you need emphasis blocks, you can use light DaisyUI primitives:

  • Badges: <span className="badge badge-primary badge-outline">Azure AI Foundry</span>
  • Buttons (for links): <a className="btn btn-outline btn-sm" href="/posts">All Posts</a>
  • Alerts (callouts):
<div className="alert alert-info">
  <span>Tip: Keep code blocks short and include expected output when useful.</span>
 
</div>

Guidelines

  • Keep components simple; avoid complex interactive DaisyUI widgets inside MDX.
  • Let markdown tables/lists render naturally; site styles already apply DaisyUI look and feel.
  • Don’t override .mdx-content typography with inline styles unless strictly necessary.

Code snippets that render and copy well

We use Nextra’s <Pre/> and <Code/> with Shiki highlighting. Use fenced code blocks with a language specifier. You can add optional metadata to enable a copy button and show filenames.

Examples

# Shell commands (prefer POSIX-compatible examples).
# If you need cross-shell notes, mention differences (fish doesn’t support heredocs).
npm run build
def hello():
  print("Hello agents!")
export function Badge({ label }: { label: string }) {
  return <span className="badge badge-primary badge-outline">{label}</span>;
}

Best practices

  • Always set a language: bash, powershell, python, csharp, tsx, json, etc.
  • Prefer portable commands; fish shell doesn’t support heredocs—use printf/echo alternatives when showing multiline file writes.
  • Use placeholders like <your-resource> and document them once above the block.
  • Include a short “Expected output” block when the snippet produces meaningful output.

SEO checklist (per post)

  • Include targeted phrases naturally in H2/H3 and intro: “Azure AI Foundry”, “Microsoft Agent Framework”, “AI agents”.
  • description ≤ 160 chars; categories are lower‑case topic phrases; add seoKeywords if you need extra discoverability.
  • Add descriptive alt text to images; avoid keyword stuffing.
  • Social image: Add image frontmatter for custom LinkedIn/Twitter previews (1200×630px). Without it, the site default is used.

Minimal post template

---
title: "Title"
date: 2025-10-18
description: "Short, helpful summary."
categories: ["azure ai foundry", "ai agents"]
seoKeywords: ["azure ai foundry", "ai agents"]
author: Christian Glessner
slug: "title"
---
 
Intro paragraph setting context.
 
## Why this matters
 
Points that connect to enterprise outcomes.
 
## Try it
 
```bash copy
cd web
npm run dev
```
 
> Tip: Add an “Expected output” block after longer code sections.