Content Stacks

Content Stacks are reusable content blocks that can be embedded across multiple pages. They enable consistent content that updates everywhere when edited in one place.

What Are Content Stacks?

A Content Stack is a named block of HTML content stored independently from any page. Think of them as reusable components — a contact information block, a disclaimer, a featured product section, or any content that appears on multiple pages.

When you update a Content Stack, every page that embeds it automatically displays the updated content. This eliminates the need to edit the same content in multiple places.

Creating a Content Stack

1. Navigate to Content Stacks in the admin navigation.
2. Click + New Stack.
3. Enter a name for the stack (descriptive, for admin reference).
4. Write your HTML content in the editor.
5. Click Save.

Stacks are stored as PHP panel files in the panels/ directory, following the naming convention content-stack-{name}.php.

Embedding Stacks in Pages

Use the panel shortcode to embed a Content Stack:

[[panel:content-stack-my-block.php]]

Place this shortcode anywhere in your page content — main column, right column, or within other HTML. The stack content renders inline at that position.

Editing Stacks

To edit an existing stack:

1. Open Content Stacks from the navigation.
2. Click the Edit button on the stack card.
3. Modify the content in the editor.
4. Click Save.

Changes take effect immediately on all pages that embed the stack.

Use Cases

• Contact information — Address, phone, email blocks used across multiple pages
• Disclaimers and legal notices — Footer disclaimers that need to be consistent
• Call-to-action blocks — Promotional sections reused across the site
• Widget sections — Social media feeds, newsletter signups, or ad blocks
• Event summaries — Auto-generated event content from AgentScheduler pipelines

Best Practices

• Use descriptive names that make the stack's purpose clear at a glance.
• Keep stacks focused — one purpose per stack for maximum reusability.
• Test stack changes by previewing a page that embeds it before going live.
• Use CSS classes in your stack HTML and style them via per-page CSS or the global stylesheet.