Skip to main content

Listen to this page

AI narration · 8 min

This film review archive is also a Drupal AI playground. The examples below use content from this site.

Start with the search examples in the first section. They do not require an account.

What a visitor sees

No account needed. These are grounded in this site's own pages: they answer from indexed content and decline when the site has nothing covering the question.

Search, with an AI answer above the results

Type any of these into the box in the header, or open /search first. The answer streams in above the classic keyword results and cites the pages it used.

A chatbot that stays inside the archive

Bottom-right of every page, or full width at its own page. It streams, it shows what it is doing while it works, and it restores your conversation if you reload.

  • How do your ratings work?

    The 10-point scale, cited to How we rate films.

  • I liked Parasite, what else should I watch?

    Recommends Get Out, reasoning from our own review. Nothing connects those two films but meaning; no shared tag, no shared genre term.

  • How much did The Godfather make?

    Declines. Box office is deliberately not on this site, and it will not fill the gap from memory.

  • I want to talk to a person.

    Links directly to the editors.

Related reading, computed from meaning

Open Se7en and look below the review: Zodiac, Why 1995 changed the thriller, Gone Girl. Not one of them shares a tag with Se7en. The block runs a vector query, not a taxonomy lookup.

A second assistant, a second body of content

Open the study programmes and the widget in the corner changes: same machinery, different corpus, different voice. It follows you across the programme pages and the student service pages, and hands back to the film assistant everywhere else. There is also a full-page version.

  • When is the deadline to pay the semester fee?

    1 September and 1 February, cited to Semester fee.

  • Can I study nursing part-time?

    Correct, and it quotes the programme's own fields back: 180 credits, part-time, application deadline.

Ask this one about films and it declines; ask the film assistant about semester fees and it declines too. Two grounded assistants on one site, neither able to reach the other's content.

What an editor sees

These need an account. The links go to the admin interface.

Fields that write themselves

Open a new film, write only the plot, then use the sparkle button beside Review, Subtitle and Summary. Spoken Summary generates an audio file from the same text. Which field derives from which is configured, not coded.

Writing tools where the writing happens

Accessibility, SEO and translation

A gate before it goes live

Everything above helps an editor write. This checks what they wrote. Publish a film review and it is screened against this site's own editorial policy first: spoilers, tone and terminology, and facts with nothing behind them.

Nothing is rewritten and nothing is blocked outright. The editor sees what was found and decides. The decision goes into the revision log with the flags it overrode, so "we published it anyway" is a recorded answer rather than a missing one.

Open a new film, put this in Plot, tick Published and save:

  • This movie is an absolute must-see masterpiece and you will be on the edge of your seat. The twist ending, where Mills finds his wife in the box, is the greatest final scene ever. It made $327 million at the box office.

    It does not save. About ten flags come back in three groups: the spoiler, then the hype and the second person and movie where the policy says film, then a box office figure that is on no field of this site. Each one quotes the phrase that triggered it. Tick publish anyway and it goes out, with the flags recorded against the revision.

Save the same text as a draft instead and nothing is screened at all. There is no model call for content nobody can read.

The gate does not care which editor wrote the text. Open a new Gutenberg page, put the same paragraph in a block, leave Published on and press Save. The page comes back with the flags in the right-hand sidebar, above the Published toggle, and the override checkbox under them. Same policy, same revision log entry.

The rules are not in the code. They are a policy item an editor can edit, the same versioned config the assistants read, and which content types are screened against which policy is configuration too.

What a site builder sees

These tools inspect and change Drupal configuration.

What a manager asks about

Logging, costs, analytics, brand rules and guardrails.

Configuration details and known issues are in AI-FEATURES.md in the repository.