Home/Documentation

Carousels

Create LinkedIn carousels by writing simple Markdown files.

Frontmatter

Each file starts with YAML frontmatter:

---
title: My Carousel
author: Your Name
theme: default
tags: [linkedin, productivity]
---
FieldTypeDescription
titlestringCarousel title (required)
authorstringAuthor name shown on cover slide
descriptionstringShort description (not rendered)
themestringdefault · ocean · forest · illuin
tagsstring[]Hashtags shown on cover and end slides

Slide types

Separate slides with ---. Each slide opens with key-value directive lines, followed by an optional Markdown body.

🚀

My Carousel

An engaging subtitle here

1 / 1

cover

The opening slide — shown first. Displays the carousel title, optional subtitle, icon, author, and tags from frontmatter.

Available fields:

titlesubtitleicon
type: cover
title: My Carousel
subtitle: An engaging subtitle here
icon: 🚀

Key Points

The most important insight
  • First key point to highlight
  • Second element with details
  • Third point that wraps naturally
1 / 1

content

The main slide type for bullet lists, paragraphs, and callout boxes.

Available fields:

titlesubtitlehighlighticonbody (Markdown)
type: content
title: Key Points
highlight: The most important insight

- First key point to highlight
- Second element with details
- Third point that wraps naturally
💬

A memorable quote or key insight that changes how you think about this topic.

— Author Name

1 / 1

quote

A focused quote or statement slide. The body becomes a styled blockquote.

Available fields:

iconhighlightbody (Markdown)
type: quote
icon: 💬
highlight: — Author Name

A memorable quote or key insight that changes how you think about this topic.

Thank you!

Follow for more insights

linkedin.com/in/yourprofile

1 / 1

end

The closing slide. Good for a call to action, contact info, or tags.

Available fields:

titlesubtitleiconbody (Markdown)
type: end
title: Thank you!
subtitle: Follow for more insights

linkedin.com/in/yourprofile

Themes


Battle Cards

Side-by-side comparison cards for two solutions, exported as a 1920×1080 image.

Frontmatter

---
title: Solution A vs Solution B
solution_a: Solution A
solution_b: Solution B
logo_a: 🅰️          # emoji, URL, or omit
logo_b: 🅱️
description_a: One-line pitch for Solution A.
description_b: One-line pitch for Solution B.
theme: default
---
FieldDescription
titleCard headline (required)
solution_a / solution_bNames of the two solutions (required)
logo_a / logo_bEmoji, absolute URL, or omit for letter avatar
description_a / description_bShort one-line pitch
themedefault · ocean · forest · illuin

Sections

After the frontmatter, separate sections with ---. Each section starts with section: <name>.

Section nameFormatDescription
strengths_a / strengths_bBullet listKey strengths — shown prominently
pros_a / pros_bBullet listAdvantages
cons_a / cons_bBullet listDrawbacks
criteriaLabel: A value | B valueComparison table rows
verdictwinner: a|b|tie
reason: text
Closing verdict bar

strengths_a / strengths_b

Key strengths displayed prominently below the solution name. Use bullet points.

section: strengths_a
- Enterprise-grade scalability
- Large ecosystem & community
- Excellent observability tooling

pros_a / pros_b

Advantages of each solution. Shown as a collapsible mini-list.

section: pros_a
- Easy to integrate with existing stack
- Strong type safety

cons_a / cons_b

Drawbacks of each solution.

section: cons_a
- Steep learning curve
- Higher infrastructure cost

criteria

Comparison table rows. Format: Label: A value | B value

section: criteria
Performance: ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐
Learning Curve: ⭐⭐⭐ | ⭐⭐⭐⭐⭐
Ecosystem: ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐
Vendor lock-in: High | Low

verdict

Closing verdict bar. winner must be a, b, or tie.

section: verdict
winner: a
reason: Better choice for large-scale production workloads

Rex Clients

Single-page client case studies exported as a 1920×1080 landscape image, presenting the client context, solution, advantages, and highlighted KPIs.

Frontmatter

---
title: Digital Transformation Success
client: Company Name
logo: 🏢          # emoji, URL, or omit for letter avatar
theme: default
---
FieldDescription
titleCase study headline (required)
clientClient company name (required)
logoEmoji, absolute URL, or omit for letter avatar
themedefault · ocean · forest · illuin · illuin-white

Sections

After the frontmatter, separate sections with ---. Each section starts with section: <name>.

Section nameFormatDescription
contextFree textClient initial situation and challenges
solutionFree textDescription of the solution implemented
advantagesBullet listKey benefits of the solution
kpisvalue: labelKey performance indicators (value shown large)

Themes

context

Describes the client's initial situation, challenges, and the problem to solve. Written as free text.

section: context
The client, a mid-sized logistics company, was struggling with manual data entry processes that led to frequent errors, delays in reporting, and a lack of real-time visibility across their supply chain operations.

solution

Describes the solution implemented. Written as free text.

section: solution
We designed and deployed a cloud-native data platform integrating their legacy ERP with a real-time analytics dashboard. Automated ETL pipelines replaced manual workflows, and a unified API layer enabled seamless data sharing across departments.

advantages

Key benefits of the solution. Use bullet points — each item appears with a checkmark.

section: advantages
- Fully automated data pipelines
- Real-time visibility across all operations
- Reduced manual errors and processing time
- Scalable architecture ready for future growth

kpis

Key performance indicators to highlight. Format: value: label. The value is shown large and prominent.

section: kpis
+65%: Productivity gain
3×: Faster reporting
-40%: Error reduction
99.9%: Uptime achieved