How indaco/teseo works
Main Components Structure
a) Core SEO Components Layer:
• Schema.org Components (schemaorg/)
• OpenGraph Components (opengraph/)
• Twitter Cards Components (twittercard/)
b) Rendering Layer:
• Templ Component Renderer
• HTML Template Renderer
c) Utilities Layer:
• URL Helpers
• Common Types
• Conversion Utilities
Component Relationships
a) Use a top-down approach with three distinct sections:
[Consumer Applications]
• ↓
[Teseo Library Core]
• ↓
[Output Formats]
• Blue: Core SEO component types
• Green: Rendering components
• Orange: Utility functions
• Gray: External dependencies
• Purple: Output formats
Detailed Component Breakdown
┌─ Schema.org Components ─────┐ ┌─ OpenGraph Components ────┐ ┌─ Twitter Card Components ─┐
• Article │ │ - Article │ │ - Summary Card │
• BreadcrumbList │ │ - Audio │ │ - Summary Large Image │
• Event │ │ - Book │ │ - App Card │
• FAQPage │ │ - Business │ │ - Player Card │
• LocalBusiness │ │ - Event │ └─────────────────────────┘
• Organization │ │ - Music* │
• Person │ │ - Place │
• Product │ │ - Product │
• SiteNavigationElement │ │ - Video* │
• WebPage │ └─────────────────────────┘
• Website │
• ┘
Integration Flow
[Input Data] → [Component Creation] → [Rendering Methods] → [Output Formats]
• ↓ ↓ ↓
• (Struct/Factory) (ToJsonLd) (JSON-LD)
• (ToMetaTags) (Meta Tags)
• (Sitemap XML)
Implementation Details
Technical notes:
• Go version compatibility
• templ dependency
• File structure organization
• Configuration options
[Web Application] → [Teseo Component] → [Generated SEO Output]
• (templ) (Article) (JSON-LD + Meta Tags)
The extensibility of the system
Remember to include notes about the demo application structure as a reference implementation, showing how all components can be used together in a real-world scenario.