Page Format

LandingRabbit Page Format Skill

Purpose

Use this skill when a user is writing landing page copy in Claude/ChatGPT/Gemini and wants:

• Use the LLM service of their choice for content brainstorming and content creation and later bring that content into LandingRabbit.
• Get the copy in a markdown format that LandingRabbit can parse reliably and turn into a page.
• Use only supported LandingRabbit section types and content fields so that users can easily import their ready page structure and copy text into LandingRabbit

Step-by-step task

Your task is to read user's ready landing page copy and format it into the LandingRabbit-Ready Markdown.

1. If not already discussed in the chat, ask user to provide a ready copy text for a landing page (e.g., homepage, ads landing page, newsletter subscription page, lead magnet page, pricing page, etc.)
2. Review the planned copy text and page structure
3. Ask the user for more information if you are unsure about any parts of the content and what section type in LandingRabbit would fit the best for each part of the plan
4. Match the copy with the available sections and content items
5. Provide your answer in LandingRabbit-ready markdown following the example answers

Important instructions

• Provide your answer as a single document that is easy to copy and paste to LandingRabbit
• Avoid making changes to user's text and section order
• Only share the LandingRabbit-ready markdown with section types and suggested layouts. Don't add any additional comments or explanations in your answer
• Examples in this skill are only to show the supported structure. Preserve user's content and tone of voice
• You don't need to use all available sections and content items. Respect the user's ready content
• Use --- only between sections in the final answer, never inside section content blocks
• Never invent any of the optional layout configurations. Refer to the user's instructions, and ask user's guidance when needed.
• If the user is planning a blog post, help document, or any other page that is a standard article format, you can use a single Custom section with markdown.
• Do not output URL-only lines (e.g. /schedule-a-call, https://...) as normal copy text; keep URLs only inside markdown links [text](url)

Available sections

• hero: The main section with the opening value proposition and primary conversion action on most pages.
• trustedBy: Social proof section for logos and credibility content.
• collection: Structured how it works, benefits, and list of services/features blocks with repeatable items. These are the most typical layouts on any landing page.
• testimonials: Customer proof quotes
• pricing: A single service offer or pricing plan comparison table
• steps: Process, checklist, sequence of actions/outcomes, or problems customers face. Only used for clear and simple lists and statements, not for describing something more complex, requiring multiple repeatable items.
• comparison: Before/after or current/future contrast comparison. For example, showing how the customer felt before and after purchasing the service.
• faq: Question-and-answer section to handle objections.
• cta: Focused conversion section, often near the end, but sometimes in between the page content as well.
• custom: Free-form mixed content (headings, text blocks, image, embed, CTA). Typically used for sections like "About us", simple statements (e.g., H2 and text block), or a full article page content
• tabs: Clickable tabs, each swapping in its own content card. For example, one tab per audience or use case.
• feed: Dynamic list of posts from a workspace collection (configuration-only). Shows, for example, the latest blog posts and news articles on a homepage.

Response format for sections

Provide the section type in your answer (e.g., Section type: hero), and when requested by the user, section-specific layout configurations.

For each section, use markdown-native structure like this:

• Eyebrow: [eyebrow]: ...
• Icon (for collection + boxes-icons items): [icon]: ... (leave empty when user should pick icons in UI)
• Smallprint: [smallprint]: ...
• Section or item title: #, ##, ###
• Description/body: plain markdown paragraphs
• CTA links: one per line (each on its own line), e.g.: [Primary CTA](url) [Secondary CTA](url)
• Images: ![Alt](url)
• Embeds/forms/widgets: fenced html blocks

In hero, cta, and collection (alternate layout), users can add:

• A grid of boxes that show, for example, company achievements or details about the service. Start with a [boxes] line, then one heading + paragraph per box (### in hero/cta, #### inside a collection-alternate item).
  • fields: [eyebrow]: ... (optional), title (the ###/#### heading), description (paragraph), CTA links (one per line)
• A testimonial from a happy client or partner, supporting the section copy and giving it credibility. Start with a [testimonial] line.
  • fields: quote (first line), name, role, company

(In collection, [boxes] and [testimonial] apply only when suggestedLayout: alternate.)

Use --- between sections.

Bullet Lists in Descriptions

In any description or subtitle field, start a line with one of these markers to add a styled bullet list:

• ✅ Text - success (green checkmark); benefits, features, positive outcomes
• ✓ Text - success (legacy plain checkmark); benefits, features, positive outcomes
• ☑ Text - check (plain checkmark); checklists, "what's included"
• ❌ Text (or ✗) - destructive (red X); problems, pain points, negative items
• ⭐ Text - star; highlights, featured items
• → Text (or ➡️) - arrow; directional flows, "next step"
• - Text (or *, •) - standard bullet (dot); neutral lists
• :word: Text - a custom icon by one word, e.g. :rocket: Build faster. The word resolves to a matching icon if there's a confident match; otherwise it renders as a plain dot.

Mix marker types and regular paragraphs in the same field. Consecutive lines with the same marker become one list.

Example - hero description with success bullets:

# Your page headline

✅ Pages live in 5 mins
✅ Loved by 200+ teams
✅ GDPR-friendly

[Get started](/signup)

Suggested Layout

For sections that support multiple layouts, add suggestedLayout: on its own line before the section content.

Hero

• horizontal (default) - text left, media right
• horizontal-reversed - media left, text right
• vertical - centered text, no media or media below

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• mediaVisibility: all | desktop | mobile | none — show or hide the hero media per device (none hides it)
• imageFit: fill | free-ratio — how the hero media fills its slot

Steps

stepDecoration controls the icon shown beside each item. Add it before the section content.

• number (default) - numbered; use for sequential process steps
• none - no icon; use for plain content lists
• check - checkmark; use for feature checklists and "what's included" lists
• star - star; use for highlights and notable achievements
• arrow - arrow; use for directional flows and "next step" sequences
• success - filled circle check; use for benefits and positive outcomes
• destructive - filled circle X; use for problems and pain points

If steps item lines already start with emoji markers (for example 😩, ✅, 🚀), set stepDecoration: none. If stepDecoration is not none, remove leading emoji/icon markers from step lines.

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• mediaVisibility: all | desktop | mobile | none — show or hide the section media per device
• imageFit: fill | free-ratio — how the section media fills its slot
• mediaPosition: left | right — which side of the list the media sits on
• stepIcon: <one descriptive word or exact CamelCase icon name> — custom icon beside every step (replaces stepDecoration)

Tabs

• top (default) - tab strip above the card
• left - tab strip in a column left of the card
• right - tab strip in a column right of the card

Based on the user's request, you can also define optional layout configurations:

• cardStyle: stacked | split — card as one stack, or media in its own column (top layout only)
• mediaSide: left | right — which side the media column is on (top layout with cardStyle: split)
• tabContentMode: expand | show-all — whether only the active tab shows its description, or all do (left/right layouts only)
• autoplay: <seconds> | off — auto-advance the tabs
• autoplayProgress: on | off — moving progress bar on each tab
• style: <saved style name> — apply a named section style
• imageFit: fill | free-ratio — how card media fills its slot

Collection

• alternate - narrative benefit blocks (each item: title + paragraph, alternating sides) → For example, Benefits, Value propositions, Solutions, "Why choose us", Case study examples and Customer Stories
• boxes - feature grid with per-item images → For example, Services, Features, Integrations, Technical capabilities
• boxes-text - text-only feature grid, no images → For example, Use cases, Capability lists, Short feature summaries
• boxes-icons - icon grid (icon handled separately from text content) → Often quick-scan feature/service highlights or how it works in a few steps (numbers as icons)

When using boxes-icons, do NOT add item [eyebrow]: ... above the icon unless clearly requested in the planned copy. For each [icon]:, use ONE descriptive word (e.g. [icon]: rocket), an exact CamelCase component name that preferably contains one or two semantic words (e.g. [icon]: IconRocket or [icon]: IconArrowRight), or leave it empty ([icon]:) for the user to pick in the UI. Exact names and confident single-word matches resolve to real icons. If a phrase is supplied, only its first word is searched; unmatched values fall back to empty.

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• imageFit: fill | free-ratio — how item media fills its slot (alternate and boxes layouts only)
• sectionHeaderPosition: above | left — section header placement (boxes layouts only)
• dividers: on | off — dividers between boxes (boxes layouts only)

Testimonials

• carousel (default) - horizontal scroll, best for 3+ testimonials
• grid - all testimonials visible at once, best for 2-4

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• sectionHeaderPosition: above | left | right — section header placement
• imageFit: fill | free-ratio — how testimonial media fills its slot
• carouselAutoplay: on | off — auto-advance the carousel (carousel layout only)
• carouselAutoplayDuration: 2-30 — seconds per slide (decimals allowed; only with autoplay on)

Comparison

• boxes-text (default) - side-by-side text-only comparison
• boxes - sides with a per-side image
• boxes-icons - sides with a per-side icon (provided via [icon]: ... inside each side)

Bullet line icons: a leading marker chooses that line's icon and is removed from the text — ✅ → success, ✓ → check, ❌/✗ → destructive, ⭐ → star, → → arrow. Unmarked lines use the side defaults (before: destructive, after: success). One marker per line; do not use other emoji as line markers.

imageFit: fill | free-ratio controls how side images fill their slots (boxes layout only).

CTA

• default (default) - centered title, description, and buttons
• embed - title and buttons with image or embed alongside

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• mediaVisibility: all | desktop | mobile | none — show or hide the media per device (embed layout only)
• imageFit: fill | free-ratio — how the media fills its slot (embed layout only)

Custom

• left (default) - left-aligned, article or blog style
• middle - centered, landing page style

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style

Pricing

Pricing has no layout options.

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• pricingSwitch: billing-period=toggle, currency=tabs — selector style per switch (bare toggle or tabs applies to the billing switch; toggle needs exactly two options)

FAQ

FAQ has no layout options.

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• sectionHeaderPosition: above | left — section header placement

TrustedBy

TrustedBy has no layout options.

Based on the user's request, you can also define optional layout configurations:

• style: <saved style name> — apply a named section style
• logosScroll: off | right-to-left | left-to-right — auto-scroll the logo row (off by default)
• logosScrollSpeed: 5-120 — seconds per scroll loop (only when scroll is on)

Feed

• boxes (default) - post grid with per-post images
• boxes-text - text-only post grid, no images
• alternate - narrative post blocks, alternating sides

Feed configuration goes on its own lines after Section type: feed:

• suggestedLayout: boxes | boxes-text | alternate
• style: <section style name>
• collection: <exact collection title or slug>
• itemCount: 1-100
• showDescription: on | off
• showTimestamp: on | off
• readMoreText: <text>
• imageFit: fill | free-ratio (boxes and alternate only)

Section Guide

1) Hero (type: 'hero')

Purpose

Open with the primary promise, context, and next action.

Section fields

• eyebrow
• title
• h2, h3
• description
• ctas
• smallprint
• Image: ![Alt text](url) - renders in the image slot
• Embed: fenced html block with <iframe> - renders in the embed slot

Additionally, you can add:

• A grid of boxes that show, for example, company achievements or details about the service. Start with a [boxes] line, then one heading + paragraph per box (### in hero/cta, #### inside a collection-alternate item).
  • fields: [eyebrow]: ... (optional), title (the ###/#### heading), description (paragraph), CTA links (one per line)
• A testimonial from a happy client or partner, supporting the section copy and giving it credibility. Start with a [testimonial] line.
  • fields: quote (first line), name, role, company

The grid of boxes and testimonials aren't the most typical parts of the hero section, so only add them when the user's page plan and request supports it.

Hero example with an image

[eyebrow]: B2B Website Builder

# Build campaign pages your team can launch this week

Create landing pages from ideas, sales materials, and product docs without starting from a blank page.

![LandingRabbit editor preview](https://example.com/hero-image.webp)

[Start your free trial](https://example.com/signup)
[See examples](https://example.com/examples)

[smallprint]: No credit card needed. Publish your first page in minutes.

Hero example with an embed

[eyebrow]: B2B Website Builder

# See how teams publish pages faster with LandingRabbit

Watch a quick walkthrough to understand how drafting, editing, and publishing work in one flow.

```html
<iframe
  width="560"
  height="315"
  src="https://www.youtube.com/embed/abc123"
  title="LandingRabbit walkthrough"
  frameborder="0"
  allowfullscreen
></iframe>
```

Start your free trial Book demo

[smallprint]: Join 200+ teams building and publishing campaign pages.

#### Hero example with a testimonial

```markdown
[eyebrow]: Customer story

# Keep every project on track without the status meetings

Plan work, assign owners, and see progress at a glance — so updates happen in the tool, not in your inbox.

[testimonial]
"We replaced three apps and a weekly status call with one board everyone actually checks."
Maya Chen
Head of Operations
Brightside Studio

[Start free](https://example.com/signup)

![Project board preview](https://example.com/hero-image.webp)

Hero example with a box grid

[eyebrow]: Trusted advice

# Grow your wealth with guidance you can rely on

Work with a dedicated advisor who builds a plan around your goals and adjusts it as life changes.

[boxes]

### $2B+

Assets under management

### 30 yrs

Average advisor experience

### 4.9/5

Client satisfaction

### 24/7

Portfolio access

[Book a consultation](https://example.com/consultation)

2) Steps (type: 'steps')

Purpose

Lists and simple statements — process steps ("How it works"), checklists, pain points, or parallel facts and metrics. Not for two opposing groups (before/after, "say goodbye / hello") — use comparison for those.

Section header fields

• eyebrow
• title
• subtitle
• ctas
• Image: ![Alt text](url) - renders beside the steps list
• Embed: fenced html block with <iframe> - renders beside the steps list

Item fields

Items can be plain lines or structured. Structured items support:

• eyebrow
• title
• description
• ctas

Additionally, you can add:

• Intro or outro paragraphs and ##/### headings before or after the list.
• More lists — each additional list renders as its own step group.
• Extra images or an [embed] iframe beyond the section media slot.
• A [sectionCtas] line whose CTA links become the section's closing buttons.

Problem section pain points (without item descriptions) example

[eyebrow]: Problem

## You know you need new pages, but content creation keeps falling behind

1. Creating new pages is a hassle and a time drain.
2. Other tasks always feel more urgent than website updates.
3. Every update risks inconsistency across channels.

Problem section pain points (with item descriptions) example

[eyebrow]: Problem

## Why teams delay launching new pages

Launching new pages is incredibly hard.

[eyebrow]: Speed

### Slow page creation workflow

Teams jump between docs, design tools, and dev queues before anything goes live.

[eyebrow]: Priorities

### Competing priorities

Campaign pages get deprioritized because production is heavy and hard to repeat.

[eyebrow]: Messaging

### Inconsistent messaging

Updates across ads, pages, and sales assets drift when the process is fragmented.

Steps with check decoration example

• stepDecoration: check

[eyebrow]: What's included

## Everything in one place

- Unlimited pages
- Custom domain publishing
- AI section generation
- Team collaboration

3) Tabs (type: 'tabs')

Purpose

Parallel alternatives the reader clicks between — audiences, use cases, feature modes, workflows — each swapping the content of one card. Use it only when the options are alternatives to choose between: a sequential process is steps, and a list where everything is visible at once is collection.

Section header fields

• eyebrow
• title
• subtitle
• ctas

Item fields

Each tab has two parts. The Tab is the clickable label, an ordered stack (all optional except the heading):

• [eyebrow]
• the ### heading
• one text line
• CTA links

CTA links always come last on the label.

The Card is everything after the label, an ordered stack. Place its parts in the order they should read:

• text
• #### headings
• CTA links
• images
• [embed]

Use-case switcher example

• layout: top

[eyebrow]: Who it's for

## One workspace, every team

### Marketing

Launch campaign pages without waiting on a design queue.

[See marketing pages](/marketing)

#### Ship in an afternoon

Start from your brand and publish to your own domain the same day.

[Start free](/signup)

### Sales

Build one-pagers for the accounts you are working right now.

#### Personalise per account

Reuse the page you already have and swap only what changes.

[Book a walkthrough](/demo)

### Support

Turn your best answers into pages customers can find.

#### Cut repeat questions

Publish the answer once and link to it from every channel.

Product tour with a split card example

• layout: top
• cardStyle: split
• mediaSide: right

## See it work

### Plan

Describe the page you want and get a full structure back.

![Plan view](https://example.com/plan.png)

### Write

Every section is generated in your brand voice.

![Editor view](https://example.com/editor.png)

### Publish

Go live on your own domain in one click.

![Published page](https://example.com/published.png)

4) Collection (type: 'collection')

Purpose

Structured content where each item pairs a heading with a description — features, benefits, services, integrations, value propositions. Can appear multiple times; each distinct section is its own collection.

Section header fields

• eyebrow
• title
• description
• ctas

Item fields

• eyebrow
• title (the item's ### heading)
• description
• ctas
• [icon]: ... (boxes-icons layout)
• Image: ![Alt text](url) (alternate and boxes layouts)
• Embed: fenced html block with <iframe>, or an [embed] line for inline

In the alternate layout only, an item can additionally contain:

• A [boxes] grid inside the item — a [boxes] line, then one #### heading + paragraph per box. This is nested inside the item, not a separate collection item.
• A [testimonial] supporting the item (quote, name, role, company).

Don't use [boxes] or [testimonial] as the collection's main items — they only nest inside an alternate item.

Bottom CTAs

Rarely used. CTA links using a [bottomCtas] marker line render after the last item.

Collection with features example

• suggestedLayout: boxes

[eyebrow]: Features

## Build pages faster with fewer bottlenecks

Create pages that prospects love and search engines find.

[eyebrow]: AI Drafting

### Generate full page structures

Create complete first drafts from a short campaign brief.

[eyebrow]: Brand controls

### Keep messaging consistent

Apply your tone, value props, and key claims across sections.

[eyebrow]: Publishing

### Go live on your domain

Publish quickly and iterate without rebuilding from scratch.

Collection with benefits

• suggestedLayout: alternate

[eyebrow]: Benefits

## Why teams switch to LandingRabbit

[Start your free trial](https://example.com/signup)

[eyebrow]: Speed to launch

### Ship campaign pages in hours

Move from idea to published page in one streamlined workflow.

[eyebrow]: Better conversion focus

### Keep every section outcome-oriented

Structure pages around pain points, proof, and clear CTA paths.

[eyebrow]: Team alignment

### Reduce handoff friction

Marketers and stakeholders work from one source of truth.

Collection with icons

• suggestedLayout: boxes-icons

## Built for modern B2B campaign teams

[icon]:

### Launch fast

Create campaign-ready drafts in minutes.

[icon]:

### Match audience intent

Build pages tailored to keyword, industry, or use case.

[icon]:

### Stay on-brand

Maintain voice, positioning, and visual direction across pages.

Collection boxes with text only

• suggestedLayout: boxes-text

[eyebrow]: Use cases

## Create pages from materials you already have

### Keywords

Turn SEO and ad keywords into dedicated pages

### Product docs

Convert specs into clear solution pages

### Sales notes

Create account-specific ABM pages from call insights

5) Testimonials (type: 'testimonials')

Purpose

Customer proof — quotes from happy clients or partners, with optional author photos and company logos. Can appear multiple times.

Section header fields

• eyebrow
• title
• subtitle
• ctas

Item fields

• quote
• name
• role
• company
• Avatar: an image whose alt starts with Author (e.g. ![Author: Maya Chen](url))
• Media: any other image ![alt](url), or an <iframe> embed
• Logos: a [logos] line followed by logo image lines

A testimonial can also be written as a blockquote: > quote — name, role, company.

Bottom CTAs

Rarely used. CTA links using a [bottomCtas] marker line render after the last item.

Testimonials section example

[eyebrow]: Loved by teams

## What our customers say

Real results from real marketing teams.

"We cut campaign page production from two weeks to one day."
Maya Chen
Growth Lead
Northbeam AI

![Author: Maya Chen](https://example.com/maya.jpg)

> Publishing became a same-day workflow for our team. — Jonas Ranta, Demand Gen Manager, ScaleForge

[logos]

![ScaleForge](https://example.com/scaleforge-logo.png)
![Northbeam](https://example.com/northbeam-logo.png)

[Read customer stories](https://example.com/customers)

6) Pricing (type: 'pricing')

Purpose

Pricing tables and plans — plan names with prices, and optionally feature bullets. Use when the user clearly provides plans and prices; otherwise consider a custom section.

Section header fields

• eyebrow
• title
• description
• ctas

Item fields

• eyebrow
• h3 (plan name)
• price lines (see below)
• subtitle
• description
• plan CTA as a markdown link [text](url)

Price lines

• Single price: one bare price line — $49/month. A price without digits (Custom) renders as-is.
• Billing switch: one labeled line per period — Monthly: $49/month and Yearly: $470/year. The labels become the switch options; the FIRST line listed is the default.
• Several periods on one line ($12/month or $120/year) are split into one option per period.
• Currency switch: repeat a label (or bare line) with another preset currency ($, €, £) — Monthly: $49/month + Monthly: €45/month. The first currency listed is the default.
• Combined switches: write every intended billing-period and currency combination explicitly. Missing combinations stay blank; LandingRabbit does not infer exchange rates or fabricate prices.
• Per-period units work too: $5/user/month.
• Feature lists and copy are shared across switch options (editing per-option copy happens in the editor).

Simple pricing example with two plans

[eyebrow]: Pricing

## Simple, transparent pricing

Pick the plan that fits your team.

[eyebrow]: For individuals

### Starter

$19/month

Everything you need to get going.

✅ 1 workspace
✅ Core features
✅ Email support

[Start Starter](https://example.com/signup)

[eyebrow]: For teams

### Pro

$49/month

Scale with your whole team.

✅ Unlimited workspaces
✅ Team collaboration
✅ Priority support

[Choose Pro](https://example.com/signup)

Pricing section example with monthly and yearly pricing

pricingSwitch: toggle

[eyebrow]: Pricing

## Plans for every growth stage

Pick the plan that matches your campaign volume.

[Compare all plans](https://example.com/pricing)

[eyebrow]: For lean teams

### Starter

Monthly: $49/month
Yearly: $470/year

Launch quickly

✅ 5 active pages
✅ AI section generation
✅ Custom domain publishing

[Start Starter](https://example.com/signup)

[eyebrow]: Most popular

### Growth

Monthly: $149/month
Yearly: $1,430/year

Scale campaigns with collaboration

✅ 25 active pages
✅ Team collaboration
✅ Advanced exports

[Start Growth](https://example.com/signup)

7) Comparison (type: 'comparison')

Purpose

• Show a clear before/after or current/future contrast.
• Exactly two sides, each a ### heading: first = before, second = after.
• Also use comparison when one section has two contrasting bullet groups (e.g. "say goodbye to" and "hello to").

Section header fields

• eyebrow
• title
• subtitle
• ctas (CTA links before the first ### side heading)

Side content (ordered, per side)

• [eyebrow]: ... line
• the side's ### heading
• bullet lines — a leading ✅/✓/❌/✗/⭐/→ marker chooses that line's icon and is removed from the text; unmarked lines use the side defaults (before: destructive, after: success)
• plain paragraphs (no bullet, no icon)
• CTA links (side-specific button)
• an image ![alt](url) — shown in the boxes layout
• an [icon]: <one descriptive word or exact CamelCase icon name> line — shown in the boxes-icons layout; use names such as IconRocket or IconArrowRight, and note that phrases search only their first word

Comparison section example

[eyebrow]: Before vs after

## What changes with LandingRabbit

A side-by-side view of your workflow shift.

[See migration guide](https://example.com/migration)

### Legacy process

- ❌ Copy and design in separate tools
- ❌ Slow review loops
- ✗ Delayed launches

### LandingRabbit workflow

- ⭐ One place for structure, copy, and publish
- → Faster iteration cycles
- ✅ Better consistency across campaigns

Comparison from "goodbye / hello" copy pattern

[eyebrow]: Effortless efficiency

## If your team can use email and WhatsApp, they can use HotKup

### Say goodbye to

- Endless status meetings and chasing updates
- Duplicating work across tools
- Tasks falling through the cracks
- Hefty, modular price tags

### Hello to

- Everything in one place — no more "which WhatsApp group was that in?"
- Update once, everyone sees it — no more copying between sheets and apps
- Everyone knows what needs doing next — work actually gets done
- One price. Full functionality. Designed for SMMEs.

8) FAQ (type: 'faq')

Purpose

Answer common questions and handle objections. Only include when the user explicitly provides Q&A content.

Section fields

• eyebrow
• title
• subtitle
• ctas

ctas are CTA links before the first question.

Item fields

• question
• answer

Link-only lines inside an answer stay in the answer.

Bottom CTAs

Rarely used. CTA links using a [bottomCtas] marker line render after the last item.

Example

[eyebrow]: FAQ

## Questions teams ask before switching

Short answers to common blockers.

### Can we publish on our own domain?

Yes. You can publish pages to your custom domain.

### Can we export content and designs?

Yes. Export to Webflow, Figma, JSON, Markdown, PDF, and PNG.

### Is this only for marketers?

No. Growth, product marketing, and content teams use it collaboratively.

[bottomCtas]

[See our documentation](https://example.com/docs)

9) CTA (type: 'cta')

Purpose

Call-to-action section — a focused conversion block, often closing a page but usable anywhere. Can appear multiple times.

Section fields

• eyebrow
• title
• h2, h3
• description
• ctas
• smallprint
• Image: ![Alt text](url) - renders in the embed-layout media slot
• Embed: fenced html block with <iframe> - renders in the embed-layout media slot

Additionally, you can add:

• A grid of boxes, e.g. company achievements or service details. Start with a [boxes] line, then one ### heading + paragraph per box.
  • fields: [eyebrow]: ... (optional), title (the ### heading), description (paragraph), CTA links (one per line)
• A testimonial from a happy client or partner, supporting the section copy. Start with a [testimonial] line.
  • fields: quote (first line), name, role, company

CTA section example

[eyebrow]: Ready to launch

## Build your next B2B campaign page today

Start with AI-assisted structure, refine messaging, and publish in minutes.

[Create my page](https://example.com/signup)
[Talk to sales](https://example.com/demo)

[smallprint]: Free trial available.

10) Custom (type: 'custom')

Purpose

Free-form prose that doesn't fit a structured type — "About us", "Our story", company background, or a full article/blog body. Not for subtitle + description item pairs (use collection).

Section fields

• eyebrow
• h1, h2, h3
• text
• smallprint
• blockquote: Markdown > quote
• code: fenced code block shown as-is. Tag it with the actual language (html, css, javascript, typescript, json, bash) to syntax-highlight it. For plain text or anything that isn't one of those languages, label the fence with a phrase like code block text so a human reading the markdown recognizes it as a code block; it renders as plain monospace. A fenced <iframe> renders instead — see Embed.
• highlight: callout box — wrap inner lines in [highlight] … [/highlight] (eyebrow, ##/###, text, smallprint, CTA links; no nested image)
• table: Markdown pipe table (first row is the header)
• cta
• author-date: byline, e.g. By Jane Smith · Apr 27, 2026
• Image: ![Alt text](url)
• Embed: fenced html block with <iframe>, or a plain YouTube/Vimeo URL

Custom section example

[eyebrow]: Our approach

# Build momentum, not bottlenecks

## Why we built LandingRabbit

### A faster path from idea to live campaign

LandingRabbit is for B2B teams that need fast launches and consistent conversion-focused copy.

[Read customer stories](https://example.com/customers)

![Editor screenshot](https://example.com/editor.webp)

```html
<iframe src="https://www.youtube.com/embed/abc123xyz" frameborder="0" allowfullscreen></iframe>
```

### 11) TrustedBy (`type: 'trustedBy'`)

#### Purpose

Add social-proof credibility with logos and supporting text. Use for customer/client logos and social-proof sections ("Trusted by", "Customer logos", "Partners", "Join 5,000+ businesses").

#### Section fields

- `eyebrow`
- `h2`, `h3`
- `text`
- `ctas`
- `logos`: `[logos]` line, then logo images `![Alt](url)` — or leave empty to upload logos in the editor
- Image: `![Alt text](url)`
- Embed: fenced `html` block with `<iframe>`, or a plain YouTube/Vimeo URL

#### TrustedBy section example

```markdown
[eyebrow]: Social proof

## Trusted by modern B2B teams

Used by SaaS, fintech, and agencies running high-velocity campaigns.

Logos: [Add 6-10 customer logos in editor]

[See customer stories](https://example.com/customers)

12) Feed (type: 'feed')

Purpose

Render a dynamic list of posts from a workspace collection (e.g. a blog). Feed is configuration-only.

Rules

• A feed MUST begin with a Section type: feed line — it is never inferred from copy.
• No post items are authored; posts come from the selected collection.
• Prefer the collection slug (unique) over the title (may collide).
• Use [bottomCta] for the closing button.
• Export does not preserve the collection selection — add a collection: line before re-importing.

Section fields

• Optional [eyebrow]:, ## title, subtitle, and section CTA links.
• Configuration directives: collection, itemCount, showDescription, showTimestamp, readMoreText, imageFit.

Feed example

Section type: feed
collection: blog
itemCount: 4
suggestedLayout: alternate
showTimestamp: off
readMoreText: Read the story
imageFit: free-ratio

## Latest stories

Insights and practical guides from our team.

[Subscribe](/newsletter)

[bottomCta]

[View all stories](/blog)

Example answers

• Provide as a single txt or markdown file the user can copy and paste to LandingRabbit

Example document A

Section type: hero

• suggestedLayout: vertical

[eyebrow]: B2B Website Builder

# Turn your ideas into marketing pages in 10 minutes

✅ Create landing pages in minutes
✅ Turn existing materials into publish-ready drafts
✅ Keep messaging consistent across teams

[Start your 14-day free trial](/signup)
[Book demo](/demo)

[smallprint]: No credit card needed.

Section type: steps

• stepDecoration: destructive

[eyebrow]: Problem

## You know you need new pages, but content creation keeps dropping down your list

- Creating new pages is slow and repetitive.
- Higher-priority tasks always win.
- Updates feel risky and inconsistent.

Section type: collection

• suggestedLayout: alternate

[eyebrow]: How it works

## LandingRabbit creates marketing pages from ideas and materials you already have

[eyebrow]: STEP 1

### Add your website URL

LandingRabbit learns your brand and business context.

![Add your website URL](https://example.com/step1.webp)

[eyebrow]: STEP 2

### Create pages from ideas and materials

Turn page ideas, sales decks, and docs into drafts.

![Create pages from ideas](https://example.com/step2.webp)

Section type: comparison

[eyebrow]: Before vs after

## Replace fragmented workflows

A side-by-side view of your workflow shift.

[See migration guide](/migration)

### Legacy process

- ❌ Copy in one tool, design in another
- ❌ Slow handoffs
- ❌ Late launches

### LandingRabbit workflow

- ✅ One workflow from brief to publish
- ✅ Faster iteration
- ✅ Better consistency

Section type: faq

## Frequently Asked Questions

### Can I use my own domain?

Yes, custom domains are supported.

### Can I export to other tools?

Yes. Export to Webflow, Figma, JSON, Markdown, PDF, and PNG.

Section type: cta

• suggestedLayout: default

[eyebrow]: Ready to launch

## Create new pages from ideas you already have

Sign up and create unlimited pages.

[Start your 14-day free trial](/signup)
[Talk to sales](/demo)

[smallprint]: Free trial available.

Example document B

Section type: hero

• suggestedLayout: vertical

[eyebrow]: Security operations

# Reduce alert fatigue with AI-assisted triage

Help analysts focus on real threats with smarter prioritization.

[Start trial](https://security.example.com/start)
[Request demo](https://security.example.com/demo)

[smallprint]: Deploy in days, not months.

Section type: collection

• suggestedLayout: alternate

[eyebrow]: Product value

## What your SOC gains immediately

[eyebrow]: Signal quality

### Fewer false positives

Improve triage confidence by prioritizing actionable threats.

[eyebrow]: Analyst efficiency

### Faster investigations

Automate repetitive classification and enrichment tasks.

Section type: comparison

[eyebrow]: Current vs improved

## SOC workflow transformation

A side-by-side view of your workflow shift.

[See architecture](https://security.example.com/architecture)

### Before

- ❌ Noisy queues
- ❌ Slow context gathering
- ❌ Inconsistent prioritization

### After

- ✅ Cleaner queues
- ✅ Faster context
- ✅ Better prioritization

Section type: testimonials

• suggestedLayout: grid

## What customers say

"We cut campaign page production from two weeks to one day.”
Maya Chen
Growth Lead
Northbeam AI

“Publishing became a same-day workflow for our team.”
Jonas Ranta
Demand Gen Manager
ScaleForge

Section type: cta

• suggestedLayout: default

[eyebrow]: Next step

## See how your SOC can triage faster

[Book technical demo](https://security.example.com/demo)

[smallprint]: Includes architecture review.

Example document C

Section type: hero

• suggestedLayout: vertical

[eyebrow]: HR and People Ops

# Onboard new hires with confidence and consistency

Create role-specific onboarding journeys that improve ramp

…(truncated)