Universal Rendering System

Automatic UI generation for every Amigos service - write logic, get interfaces free.

The Render() Paradigm

Core Concept

type Renderable interface {
    Render(path string) string
}

Every service can implement Render() to provide automatic UI across all platforms:

Terminal: ANSI colors and formatting
Web: HTML/CSS interfaces
Mobile: Responsive layouts
API: JSON/GraphQL responses

Basic Example

type TodoList struct {
    Items []Todo
}

func (t TodoList) Render(path string) string {
    switch runtime.Context() {
    case "terminal":
        return t.renderANSI()
    case "web":
        return t.renderHTML()
    case "api":
        return t.renderJSON()
    default:
        return t.renderMarkdown()
    }
}

Automatic UI Benefits

For Developers

Zero Frontend Code: Logic automatically gets UI
Platform Agnostic: One implementation, many outputs
Progressive Enhancement: Start simple, add custom rendering later
Instant Feedback: See your service visually immediately

For Users

Consistent Experience: Every service has UI
Multiple Interfaces: Use via CLI, web, or mobile
No Installation: Web interfaces work instantly
Accessibility: Automatic compliance features

Implementation Strategy

Phase 1: Basic Rendering

// Amigos provides default renderers
func DefaultRender(v interface{}) string {
    return amigos.AutoFormat(v)
}

Phase 2: Custom Renderers

// Developers can override
func (s Service) Render(path string) string {
    return customHTML(s)
}

Phase 3: Interactive UIs

// Rich interactions
func (s Service) RenderInteractive() Interactive {
    return amigos.UI().
        Form("input", s.handleInput).
        Button("submit", s.handleSubmit)
}

Path-Based Routing

The path parameter enables sub-resource rendering:

func (blog Blog) Render(path string) string {
    switch path {
    case "/":
        return blog.renderIndex()
    case "/posts":
        return blog.renderPosts()
    case matches("/post/*"):
        return blog.renderPost(extractID(path))
    default:
        return "404 Not Found"
    }
}

Format Negotiation

Automatic Detection

// Amigos detects preferred format
Accept: text/html     → HTML output
Accept: application/json → JSON output
Terminal: true        → ANSI output

Explicit Formats

service.Render("/posts.json")  // Force JSON
service.Render("/posts.html")  // Force HTML
service.Render("/posts.md")    // Force Markdown

Built-in Components

Standard UI Elements

// Amigos provides common components
amigos.UI.Table(data)
amigos.UI.Form(fields)
amigos.UI.Chart(metrics)
amigos.UI.Menu(options)

Responsive by Default

Mobile-first design
Progressive enhancement
Offline capability
Dark mode support

Developer Experience

Zero to UI

type Counter struct {
    Value int
}

// That's it! This now has:
// - Web interface at hub.amigos.dev/counter
// - CLI interface via `amigos run counter`
// - API endpoint returning JSON
// - Mobile-responsive design

Custom Styling

func (c Counter) Style() string {
    return `
        .counter { 
            font-size: 48px; 
            color: var(--primary);
        }
    `
}

Integration with Imports

When you import a service, you get its UI too:

import "hub.amigos.dev/blog"

// Your service can embed their UI
func (app App) Render(path string) string {
    if strings.HasPrefix(path, "/blog") {
        return blog.Render(path)
    }
    // ... your rendering
}