Configuration¶
AI provider¶
The review workflows call the site's default chat model. When you apply the recipe:
- Enter a key to set that provider up. The key is stored encrypted by Easy Encryption, and the provider's models become the default for each operation that has none yet.
- Leave both keys empty on a site that already has an AI provider. The recipe keeps it.
- Leave both keys empty on a site with no provider, then configure one with a default for the Chat operation. Reviews fail until then.
What a review reads¶
When a review runs, it sends the AI model:
- The content's type, bundle and title.
- Every text field the person running the review can view. Plain and formatted text fields are sent as stored: the text and HTML an editor entered, not the rendered page. A field with several items sends each item on its own, and an empty field is sent marked as empty.
Nothing else about the content is sent: no other fields, no referenced content and no page layout. An image or media item embedded in a formatted text field is sent as a placeholder token, not as the file. Display settings and Drupal Canvas content templates do not change what is sent. Besides the content, the model gets the review's guidelines and the rule's scored examples.
Note
A review result does not list the fields it read yet. See #3585901.
Fields that hold numbers, lists, references, media or paragraphs are not read.
Note
A content type without any text field sends only the title.
The recipe creates no content types and adds no fields. On a site whose content types have no text fields, such as a bare install from the minimal profile, add them first. For example, apply core's article content type recipe:
ddev drush recipe core/recipes/article_content_type