This example demonstrates all key Iris features for internal tool teams:
- Multiple pages with client-side routing
- Auth-protected sections with route guards
- Reactive data display with signals
- Form inputs (text, checkbox, slider, select)
- Component composition with reusable layouts
Test credentials: admin/admin (full access) or user/user (limited access)
Closes#8
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Documents the host package covering:
- Basic server setup with code example
- Directory structure for WASM apps
- Static file serving and SPA fallback
- WASM MIME type configuration
- Automatic gzip compression
- Development vs production considerations
Closes#3
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Minimal Iris application demonstrating:
- Signal creation with NewSignal
- Reactive text rendering with TextFromFunction
- Auto-incrementing counter to show reactivity
Closes#2
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add explicit mkdir -p public before wasm_exec.js copy
- Specify to save app code as main.go
- Specify to save server code as server.go
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Provides a complete getting-started guide covering prerequisites,
app creation, HTML host setup, build commands, and running the app.
Closes#1
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Remove test step from CI (WASM-only code can't run native tests)
- Update manifesto links to use absolute Gitea URLs
Co-Authored-By: Claude <noreply@anthropic.com>
