Specialized Layouts
ZiraDocs provides specialized slide layouts that automatically apply optimized styling and validation for different content types. Each layout includes specific CSS styling and validation rules to ensure content is appropriate for its intended purpose.
Overview
Section titled “Overview”Specialized layouts help you create professional presentations by:
- Automatic styling - Each layout applies appropriate CSS styles
- Content validation - Built-in rules ensure appropriate content for each layout type
- Visual optimization - Layouts are designed for specific use cases and content types
- Cross-mode support - Available in both Strict Mode and Flex Mode
Layout Types
Section titled “Layout Types”Basic Layouts
Section titled “Basic Layouts”title - Title Slide Layout
Section titled “title - Title Slide Layout”Purpose: Primary presentation cover slide
Characteristics:
- Centered design with large typography
- Support for company logo
- Clean, impactful visual presentation
Strict Mode:
SLIDE title heading: "My Presentation" subtitle: "Descriptive subtitle" logo: "assets/logo.png"Flex Mode:
---layout: title---
# My Presentation## Descriptive subtitle
Validation Rules:
- Must have
headingor title - Should avoid complex content elements
- Maximum 1 decorative element allowed
content - General Content Layout
Section titled “content - General Content Layout”Purpose: Standard content slides for main presentation material
Characteristics:
- Flexible layout for mixed content types
- Support for all content elements
- General-purpose design
Strict Mode:
SLIDE content title: "Main Content" TEXT Regular content with mixed elements. POINTS - First point - Second pointFlex Mode:
---layout: content---
# Main Content
Regular content with mixed elements.
- First point- Second pointValidation Rules:
- Must have a title
- Must have at least one content element
- No restrictions on element types
section - Section Introduction Layout
Section titled “section - Section Introduction Layout”Purpose: Introduction slides for new presentation sections
Characteristics:
- Optimized for introductory text
- Clean design marking new topic sections
- Simple, readable layout
Strict Mode:
SLIDE section title: "Development Methodology" subtitle: "Processes and best practices" TEXT In this section we'll explore agile methodologies and how to implement them in our projects.Flex Mode:
---layout: section---
# Development Methodology## Processes and best practices
In this section we'll explore agile methodologiesand how to implement them in our projects.Validation Rules:
- Must have title or subtitle
- Should contain simple, introductory content
- Avoids complex elements (code, charts, tables)
Comparison and Analysis Layouts
Section titled “Comparison and Analysis Layouts”comparison - Side-by-Side Comparison Layout
Section titled “comparison - Side-by-Side Comparison Layout”Purpose: Compare two or more options side by side
Characteristics:
- Column-based layout for visual comparison
- Balanced content distribution
- Clear visual differentiation
Strict Mode:
SLIDE comparison title: "Framework Comparison" :::info title: "React" content: "Component-based, virtual DOM, large ecosystem" :::success title: "Vue" content: "Progressive, template-based, gentle learning curve"Flex Mode:
---layout: comparison---
# Framework Comparison
:::info ReactComponent-based, virtual DOM, large ecosystem:::
:::success VueProgressive, template-based, gentle learning curve:::Validation Rules:
- Must have balanced content sections
- Minimum 2 comparable elements
- Supports tables, points, and special blocks
stats - Statistics and Data Layout
Section titled “stats - Statistics and Data Layout”Purpose: Display statistical information and data visualizations
Characteristics:
- Optimized for charts and tables
- Clean presentation of numerical data
- Focus on data clarity
Strict Mode:
SLIDE stats title: "Performance Metrics" TABLE headers: ["Metric", "Q3", "Q4", "Growth"] rows: [ ["Revenue", "$1.2M", "$1.8M", "+50%"], ["Users", "15K", "23K", "+53%"] ]Flex Mode:
---layout: stats---
# Performance Metrics
| Metric | Q3 | Q4 | Growth ||--------|----|----|--------|| Revenue | $1.2M | $1.8M | +50% || Users | 15K | 23K | +53% |Validation Rules:
- Must include data elements (charts, tables, or metrics)
- Minimum 1 data visualization element
- Avoids code blocks and diagrams
Technical and Content Layouts
Section titled “Technical and Content Layouts”code_example - Code Example Layout
Section titled “code_example - Code Example Layout”Purpose: Technical documentation and code demonstrations
Characteristics:
- Optimized for code readability
- Syntax highlighting support
- Clear technical presentation
Strict Mode:
SLIDE code_example title: "API Implementation" TEXT Basic usage example: CODE javascript const api = new DataProcessor({ endpoint: 'https://api.example.com', apiKey: process.env.API_KEY });
const result = await api.process(inputData);Flex Mode:
---layout: code_example---
# API Implementation
Basic usage example:
```javascriptconst api = new DataProcessor({ endpoint: 'https://api.example.com', apiKey: process.env.API_KEY});
const result = await api.process(inputData);**Validation Rules:**- Must contain at least one code block- Should include explanatory text- Optimized for technical content
### Marketing and Communication Layouts
#### `hero` - Hero/Impact Visual Layout
**Purpose:** Maximum visual impact with hero elements
**Characteristics:**- Full-screen background image support- Overlay text with visual effects- Prominent call-to-action- Cinematic design
**Strict Mode:**```slidelangSLIDE hero background: "images/hero-bg.jpg" title: "Revolutionizing the Future" subtitle: "The next generation is here" cta: "Discover More"Flex Mode:
---layout: herobackground: "images/hero-bg.jpg"---
# Revolutionizing the Future## The next generation is here
[Discover More](#cta){.btn-primary}Validation Rules:
- Must have a title
- Maximum 3 content elements
- Avoids complex elements (code, tables, charts)
testimonial - Testimonial Layout
Section titled “testimonial - Testimonial Layout”Purpose: Display customer testimonials and social proof
Characteristics:
- Quote-focused design
- Author attribution with photo support
- Credibility-focused styling
Strict Mode:
SLIDE testimonial quote: "This solution increased our productivity by 300% in just three months." author: "Sarah Johnson" position: "CEO" company: "TechCorp" avatar: "images/sarah.jpg"Flex Mode:
---layout: testimonial---
> "This solution increased our productivity by 300% in just three months.">> **— Sarah Johnson, CEO of TechCorp**
Validation Rules:
- Should include quote and author information
- Maximum 3 content elements
- Focus on testimonial content
call_to_action - Call to Action Layout
Section titled “call_to_action - Call to Action Layout”Purpose: Drive specific user actions
Characteristics:
- Action-oriented design
- Prominent buttons and links
- Urgency and motivation focus
Strict Mode:
SLIDE call_to_action title: "Ready to Get Started?" subtitle: "Join thousands of satisfied customers" primary_cta: "Start Free Trial" secondary_cta: "Learn More"Flex Mode:
---layout: call_to_action---
# Ready to Get Started?## Join thousands of satisfied customers
[Start Free Trial](#primary){.btn-primary}[Learn More](#secondary){.btn-secondary}Validation Rules:
- Must include action-oriented content
- Should contain call-to-action elements
- Maximum 3 elements for focus
Organization and Process Layouts
Section titled “Organization and Process Layouts”timeline - Timeline Layout
Section titled “timeline - Timeline Layout”Purpose: Display chronological information and timelines
Characteristics:
- Chronological visual layout
- Clear temporal progression
- Event-focused design
Strict Mode:
SLIDE timeline title: "Project Roadmap" events: [ { date: "Q1 2025", title: "Planning Phase", status: "completed" }, { date: "Q2 2025", title: "Development", status: "in-progress" }, { date: "Q3 2025", title: "Testing", status: "planned" } ]Flex Mode:
---layout: timeline---
# Project Roadmap
- **Q1 2025** - Planning Phase ✅- **Q2 2025** - Development 🔄- **Q3 2025** - Testing 📅Validation Rules:
- Minimum 2 temporal events
- Maximum 6 timeline elements
- Focus on chronological content
process - Process/Methodology Layout
Section titled “process - Process/Methodology Layout”Purpose: Explain step-by-step processes and methodologies
Characteristics:
- Sequential step layout
- Process flow visualization
- Clear progression indicators
Strict Mode:
SLIDE process title: "Development Process" steps: [ "Requirements Analysis", "Design & Architecture", "Implementation", "Testing & QA", "Deployment" ]Flex Mode:
---layout: process---
# Development Process
1. **Requirements Analysis** - Understanding project needs2. **Design & Architecture** - Planning the solution3. **Implementation** - Building the product4. **Testing & QA** - Ensuring quality5. **Deployment** - Releasing to productionValidation Rules:
- Minimum 2 sequential steps
- Maximum 6 process steps
- Focus on procedural content
Business and Marketing Layouts
Section titled “Business and Marketing Layouts”pricing - Pricing/Plans Layout
Section titled “pricing - Pricing/Plans Layout”Purpose: Display pricing tiers and plan comparisons
Characteristics:
- Pricing table optimization
- Plan comparison features
- Clear value proposition
Strict Mode:
SLIDE pricing title: "Choose Your Plan" plans: [ { name: "Basic", price: "$29/month", features: ["5 users", "10GB storage"] }, { name: "Pro", price: "$79/month", features: ["50 users", "100GB storage"] } ]Flex Mode:
---layout: pricing---
# Choose Your Plan
| Feature | Basic | Pro ||---------|-------|-----|| Price | $29/month | $79/month || Users | 5 | 50 || Storage | 10GB | 100GB |Validation Rules:
- Must include pricing information
- Should contain plan comparison
- Maximum 4 pricing tiers
team - Team Presentation Layout
Section titled “team - Team Presentation Layout”Purpose: Introduce team members and organizational structure
Characteristics:
- Member profile layout
- Role and department display
- Professional presentation
Strict Mode:
SLIDE team title: "Meet Our Team" members: [ { name: "Alice Johnson", role: "Lead Developer", email: "alice@company.com" }, { name: "Bob Smith", role: "Product Manager", email: "bob@company.com" } ]Flex Mode:
---layout: team---
# Meet Our Team
## Alice Johnson**Lead Developer**alice@company.com
## Bob Smith**Product Manager**bob@company.comValidation Rules:
- Should include member information with roles
- Maximum 8 team members
- Focus on person-related content
dashboard - Dashboard/Metrics Layout
Section titled “dashboard - Dashboard/Metrics Layout”Purpose: Display real-time interfaces and metrics
Characteristics:
- Interface simulation styling
- Integrated charts and metrics
- Real-time data presentation
Strict Mode:
SLIDE dashboard title: "Control Panel" widgets: [ { type: "metric", title: "Total Sales", value: "$2.4M", change: "+15%" }, { type: "chart", title: "Monthly Growth", data: "chart_data.json" } ]Flex Mode:
---layout: dashboard---
# Control Panel
## Key Metrics- **Total Sales:** $2.4M (+15%)- **Active Users:** 15,847 (+8%)- **Conversion Rate:** 3.2% (+0.5%)
<<chart: line>> title: "Monthly Growth" data: [125, 145, 167, 189]Validation Rules:
- Should include metrics or charts
- Maximum 6 dashboard elements
- Focus on data visualization
before_after - Before/After Layout
Section titled “before_after - Before/After Layout”Purpose: Show transformations and improvements
Characteristics:
- Split-screen comparison design
- Clear before/after sections
- Transformation focus
Strict Mode:
SLIDE before_after title: "Transformation Results" before: "Manual process taking 8 hours daily" after: "Automated process completed in 15 minutes"Flex Mode:
---layout: before_after---
# Transformation Results
## BeforeManual process taking 8 hours daily- Time-consuming- Error-prone- Resource intensive
## AfterAutomated process completed in 15 minutes- Efficient- Accurate- Cost-effectiveValidation Rules:
- Must have both “before” and “after” sections
- Minimum 2 comparison elements
- Maximum 4 total elements
Special Purpose Layouts
Section titled “Special Purpose Layouts”feature_showcase - Feature Showcase Layout
Section titled “feature_showcase - Feature Showcase Layout”Purpose: Highlight product features and benefits
Characteristics:
- Feature-focused layout with icons
- Benefit highlighting
- Multi-feature support
Strict Mode:
SLIDE feature_showcase title: "Key Features" features: [ { icon: "🚀", title: "Ultra Fast", description: "Processing in milliseconds" }, { icon: "🔒", title: "Secure", description: "End-to-end encryption" } ]Flex Mode:
---layout: feature_showcase---
# Key Features
## 🚀 Ultra FastProcessing in milliseconds
## 🔒 SecureEnd-to-end encryption
## 📊 AnalyticsReal-time insightsValidation Rules:
- Should highlight at least 2 features
- Maximum 6 feature highlights
- Focus on feature-benefit content
closing - Closing Slide Layout
Section titled “closing - Closing Slide Layout”Purpose: Presentation conclusion and final thoughts
Characteristics:
- Clean, conclusive design
- Contact information support
- Thank you messaging
Strict Mode:
SLIDE closing heading: "Thank You" subtitle: "Questions & Discussion" contact: "john@company.com"Flex Mode:
---layout: closing---
# Thank You## Questions & Discussion
**Contact:** john@company.com**LinkedIn:** /in/johnsmithValidation Rules:
- Should contain simple, conclusive content
- Maximum 3 elements
- Avoids complex elements
Layout Validation
Section titled “Layout Validation”ZiraDocs automatically validates slide content against layout requirements:
Validation Rules
Section titled “Validation Rules”Each layout includes specific validation rules:
- Element restrictions - Some layouts forbid certain element types
- Minimum/maximum elements - Controls content complexity
- Required properties - Ensures essential information is present
- Content appropriateness - Validates content matches layout purpose
Validation Messages
Section titled “Validation Messages”The linter provides specific guidance when validation fails:
# Example validation messagesLAYOUT001: Title slides must have a 'heading' propertyLAYOUT003: Content slides must have a 'title' propertyLAYOUT011: Timeline slides should have at least 2 temporal eventsLAYOUT015: Feature showcase slides should highlight at least 2 featuresMode Differences
Section titled “Mode Differences”Layout Specification
Section titled “Layout Specification”Strict Mode:
- Layout specified in slide declaration:
SLIDE layout_name - Example:
SLIDE title,SLIDE comparison
Flex Mode:
- Layout specified in frontmatter:
layout: layout_name - Can be auto-detected based on content patterns
Syntax Comparison
Section titled “Syntax Comparison”Code Example in Strict Mode:
SLIDE code_example title: "My Code" CODE python print("Hello world") POINTS - Important pointSame Content in Flex Mode:
---layout: code_example---
# My Code
```pythonprint("Hello world")- Important point
### Automatic Detection (Flex Mode Only)
Flex Mode can automatically detect layouts based on content:
```slidelang# Welcome to Our Product## Revolutionizing the industry
Automatically detected as ‘hero’ layout
| Feature | Basic | Pro ||---------|-------|-----|| Users | 5 | 50 || Storage | 1GB | 100GB |Automatically detected as ‘comparison’ layout
CSS Styling
Section titled “CSS Styling”Each layout includes specialized CSS styling:
- Typography adjustments for content type
- Layout grids optimized for content structure
- Color schemes appropriate for layout purpose
- Responsive design for all screen sizes
- Animation effects for visual enhancement
Best Practices
Section titled “Best Practices”- Choose appropriate layouts - Match layout to content type
- Follow validation rules - Address linter warnings promptly
- Keep content focused - Respect element limits for clarity
- Test responsiveness - Verify layouts work on all devices
- Use consistent styling - Leverage layout-specific CSS
- Validate regularly - Run linter during development
CLI Integration
Section titled “CLI Integration”Layout validation works seamlessly with ZiraDocs CLI:
# Validate layouts during buildslidelang build presentation.slidelang
# Lint-only mode for layout checkingslidelang build --lint-only presentation.slidelang
# Debug layout detectionslidelang build presentation.slidelang --log-level debugCommon Patterns
Section titled “Common Patterns”Progressive Presentation Structure
Section titled “Progressive Presentation Structure”SLIDE title # Presentation introductionSLIDE section # Section introductionsSLIDE content # Main content slidesSLIDE comparison # Feature/option comparisonsSLIDE stats # Supporting dataSLIDE call_to_action # Drive user actionSLIDE closing # Conclusion and thanksTechnical Documentation Flow
Section titled “Technical Documentation Flow”SLIDE title # API/Product introductionSLIDE section # Getting started sectionSLIDE code_example # Implementation examplesSLIDE dashboard # Usage metrics/monitoringSLIDE feature_showcase # Key capabilitiesSLIDE pricing # Plans and pricingSLIDE closing # Contact and next stepsMarketing Presentation Flow
Section titled “Marketing Presentation Flow”SLIDE hero # Eye-catching introductionSLIDE feature_showcase # Product highlightsSLIDE testimonial # Social proofSLIDE before_after # Transformation storiesSLIDE pricing # Plans and offersSLIDE call_to_action # Drive conversionSLIDE closing # Thank you and contactRelated Documentation
Section titled “Related Documentation”- Strict Mode Syntax - Using layouts in Strict Mode
- Flex Mode Syntax - Using layouts in Flex Mode
- FrontMatter Configuration - Layout configuration options
- Advanced Elements - Complex content elements
- Themes & Styling - Visual customization
Examples
Section titled “Examples”See the Specialized Layouts Examples directory for complete working examples of all layout types in both Strict and Flex modes.
💡 Pro Tip: Start with basic layouts (title, content, section) and gradually incorporate specialized layouts as your presentation complexity grows.