Standard Markdown Support
Directify fully supports all standard markdown syntax including:Text Formatting
- Bold text with
**bold**
or__bold__
- Italic text with
*italic*
or_italic_
Inline code
with backticksStrikethroughwith~~text~~
Headers
Lists
Links and Images
Code Blocks

Enhanced Syntax with ::: Components
Directify extends markdown with custom components using the::: @component :::
syntax. These components provide rich functionality beyond standard markdown.
Video and Media Embedding
@iframe Component
Embed any iframe content including YouTube, Vimeo, and other multimedia:Syntax
Supported Platforms
- YouTube: Use embed URLs from YouTube
- Vimeo: Direct embed URLs
- Google Maps: Embed map iframes
- CodePen: Interactive code demonstrations
- Slides: Google Slides, SlideShare presentations
- Forms: External form embeds
- Any iframe content: Custom widgets, tools, etc.
Examples
YouTube Video:Technical Details
- Responsive: Automatically sized to full width (
w-full h-96
) - Secure: Includes proper security attributes
- Optimized: Includes performance optimizations for media playback
- Accessible: Proper iframe labeling and keyboard navigation
Always use embed URLs from trusted sources. Avoid direct links to video files - use platform-specific embed URLs instead.
FAQ Components
Create structured FAQ sections with automatic schema markup for SEO benefits:Basic FAQ Syntax
Multiple FAQ Sections
FAQ Features
- Automatic Schema: SEO-optimized FAQ schema markup
- Collapsible Design: User-friendly accordion interface
- Search Friendly: Properly structured for search engines
- Mobile Optimized: Responsive design for all devices
Call-to-Action (CTA) Components
Add compelling call-to-action sections to drive user engagement:CTA Syntax
- Eye-catching design matching your directory theme
- Strategic placement within content flow
- Mobile-responsive layout
- Conversion-optimized styling
CTA components use your directory’s configured call-to-action content and styling. Customize the CTA design in your directory settings.
Best Practices for Enhanced Markdown
Content Structure
- Use Headers Hierarchically - Maintain proper H1, H2, H3 structure
- Break Up Text - Use components to create visual breaks
- Balance Content - Mix text with multimedia for engagement
- Mobile-First - Consider how content appears on mobile devices
SEO Optimization
- FAQ Schema - Use FAQ components for common questions
- Descriptive Alt Text - Always include alt text for images
- Internal Linking - Link to related content within your directory
- Header Optimization - Use descriptive, keyword-rich headers
User Experience
- Progressive Disclosure - Use FAQs to reveal information gradually
- Visual Breaks - Embed videos and media to break up text
- Clear CTAs - Strategic placement of call-to-action components
- Readable Formatting - Proper use of lists, headers, and emphasis
Component Combinations
Rich Content Example
Technical Implementation
Where Components Work
Enhanced markdown syntax is available in:- Listing Content - Rich descriptions with multimedia
- Article Content - Blog posts with embedded media
- Category Descriptions - Detailed category explanations
- Custom Pages - Landing pages and informational content
- Directory Descriptions - About pages and site descriptions
- Ad Content - Rich advertising content
Processing Order
- Standard Markdown - Converted to HTML first
- @iframe Components - Processed and embedded
- FAQ Components - Structured with schema markup
- CTA Components - Rendered with directory styling
- Cleanup - Remaining syntax markers removed
Performance Considerations
- Lazy Loading - Iframes load efficiently
- Schema Caching - FAQ schemas cached for performance
- Mobile Optimization - All components responsive
- SEO Benefits - Enhanced search engine visibility
Troubleshooting Common Issues
Iframe Not Loading
- Check URL: Ensure you’re using embed URLs, not direct links
- HTTPS Required: Some platforms require secure connections
- Platform Restrictions: Some sites block iframe embedding
FAQ Not Displaying
- Header Format: Ensure questions use
###
(H3) headers - Content Structure: Place content directly after question headers
- Proper Syntax: Check opening and closing
:::
markers
Syntax Not Processing
- Exact Format: Use exact
::: component :::
syntax - No Extra Spaces: Avoid extra spaces in component declarations
- Case Sensitive: Component names are case-sensitive
Migration from Standard Markdown
If you have existing markdown content:- Backup Content - Save original markdown files
- Gradual Enhancement - Add components incrementally
- Test Thoroughly - Preview content before publishing
- Update Links - Ensure all embedded content works
- Monitor Performance - Check loading speeds after updates
Start with one component type (like @iframe) and gradually incorporate others as you become comfortable with the enhanced syntax.