> ## Documentation Index
> Fetch the complete documentation index at: https://docs.obvlo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Engine Features

> Automated content generation system with AI-powered curation, classification, and quality assessment.

# Content Engine

> [!NOTE]
>
> Use [Content Engine](/product/creation/content-engine) for implementation overview. Use this page for detailed feature reference.

The Content Engine is the core automated content generation system. It taps multiple third-party data sources, curates results, classifies findings into a standardised content schema, generates editorial copy and AI imagery, and then assesses all output against quality standards before making it available.

## Features

| Feature | What It Does | Key Capabilities |
| - | - | - |
| **Brand Configuration** | Define brand rules applied to all generated content. | Vocabulary, sentence structure, and tone rules; Brand Tone (emotional register); Brand Voice Guidelines; Image Guidelines (mood, composition, colour palette); Brand assets (colours, logos, typography); Reusable across multiple destinations |
| **Template Configuration** | Define what content gets created, for which audience, with what personalisation mappings. | Set content types and categories per destination; Map personalisation criteria (traveller type, interests, trip type); Set seasonal rules and content source requirements; Universal templates available for immediate use |
| **Localisation** | Generate content natively for 60+ locales, not translated. | Native generation per locale (not machine translation); Language variants treated as distinct (e.g. pt-BR vs pt-PT); Currency, date formats, and units adapted per locale; Pre-localised copy served to travellers |
| **Job Execution** | Schedule and run all content creation tasks concurrently for a destination. | All content types run in parallel (not sequentially); Full job tracking (queued, running, completed); Failed jobs flagged with reason and can be re-queued; Single job covers: crawl, classify, generate, assess |
| **AI Judge** | Automatically review every piece of content against brand standards and use-case criteria. | Brand and use-case criteria applied to evaluate tone, accuracy, quality per output type; Different evaluation rules per use-case (guides vs listings); Full decision log per content item (pass/fail and reason); Failed content automatically reprocessed |
| **Custom Database** | Isolated, structured content database per organisation. | Each organisation has isolated database (no content shared); Standardised schema across all records for reliable API access; Automatically updated when new fields or features added to Obvlo |
| **Content Outputs** | Content types generated and packaged by the Content Engine. | Area Guides, Thematic Guides, Listings (POI, Bookable Tours, Live Events), Itineraries, AI-generated imagery, Weather data; POI/event/review data re-queried on each job run |

***

## Future Updates

When a new feature is released to the Content Engine, simply add a new row to the table above. No file restructuring needed.

## Related

* [Portal Features](/product/management/portal-features) — Configure and manage Content Engine settings
* [Web App](/product/delivery/web-app-features) — Deliver generated content to travellers
* [Reporting](/product/insights/reporting-features) — Track content performance


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.