Models
Organize model capabilities by modality. Exact availability depends on your deployment configuration.
Overview
Hopola can work with different model modalities depending on what your backend enables. This docs section helps you think in capabilities (text, image, audio, video) rather than specific providers.
Modalities
- Text: copywriting, outlines, structured briefs, QA checklists.
- Image: visual directions, references, image understanding workflows.
- Audio: transcription, voice notes, audio-to-text workflows.
- Video: storyboard support, scene descriptions, video-to-text workflows.
Capability matrix
To keep this section deliverable-focused, map modalities to inputs, outputs, and the assets you ship. Use this table as a baseline and customize it to your actual integrations.
| Modality | Typical inputs | Typical outputs | Best deliverables |
|---|---|---|---|
| Text | Briefs, constraints, asset lists, references | Structured outlines, copy packs, QA checklists | Deck outlines, detail-page structure, handoff notes |
| Image | References, screenshots, style keywords | Visual directions, layout guidance, issue spotting | Hero-image direction, design review recommendations |
| Audio | Meeting recordings, voice notes | Transcripts, key points, actionable revision items | Review summaries, revision task lists |
| Video | Footage, script ideas, platform constraints | Storyboard tables, shot descriptions, asset lists | Short-form storyboards, subtitle/cover/thumbnail requirements |
Integration checklist
Regardless of provider, align on “deliverable quality” before wiring anything into production:
| Item | Recommendation | Why it matters |
|---|---|---|
| Capability boundaries | List what’s enabled/disabled by modality (text/image/audio/video). | Avoid promising features that aren’t actually available. |
| Output contracts | Prefer structured outputs (tables/JSON/checklists) with fixed fields. | Easier automation and regression testing. |
| Quality bar | Define acceptance criteria: readability, alignment, compliance, naming. | Consistent review and handoff standards. |
| Degradation | Fallback to templates/rules or guide users to manual steps when models fail. | Prevents critical workflows from getting blocked. |
Notes
- Keep sensitive keys and provider settings on the backend only.
- Prefer modality-appropriate prompts: describe constraints, formats, and output structure.
- For predictable results, pair models with reusable skill workflows.