Drupal is a registered trademark of Dries Buytaert
drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)! drupal 11.3.6 Update released for Drupal core (11.3.6)! drupal 10.6.6 Update released for Drupal core (10.6.6)! cms 2.1.0 Update released for Drupal core (2.1.0)! bootstrap 8.x-3.40 Minor update available for theme bootstrap (8.x-3.40). menu_link_attributes 8.x-1.7 Minor update available for module menu_link_attributes (8.x-1.7). eca 3.1.1 Minor update available for module eca (3.1.1). layout_paragraphs 2.1.3 Minor update available for module layout_paragraphs (2.1.3). ai 1.3.3 Minor update available for module ai (1.3.3). ai 1.2.14 Minor update available for module ai (1.2.14). node_revision_delete 2.0.3 Minor update available for module node_revision_delete (2.0.3). moderated_content_bulk_publish 2.0.52 Minor update available for module moderated_content_bulk_publish (2.0.52). klaro 3.0.10 Minor update available for module klaro (3.0.10). klaro 3.0.9 Minor update available for module klaro (3.0.9). layout_paragraphs 2.1.2 Minor update available for module layout_paragraphs (2.1.2). geofield_map 11.1.8 Minor update available for module geofield_map (11.1.8).

Overview

With Site Assistant you can create assistants that can help your users navigate better, faster and more targeted on your website.

Assistants basically consist of two fields. One is the content field where you can place an unlimited amount of assistant list entries. And the other field "Visibility conditions" is where you configure the conditions when the assistant should be used. (See: Condition plugin system)

Assistant list entries are content entities that come in different shape and functions. They vary from very simple "Headline" to more complex "Subpage". You can even define your own assistant list entry type.

Assistant library items are content entities that are design to be reused over multiple assistants. They basically are a collection of assistant list entries.

Use cases

Example 1 - Public relations

You have an area on your website that is dedicated to journalists. All content in this area is located under http://example.com/public-relations.
So you create an assistant that is targeting journalists by using a path condition public-relations/*.
The assistant is filled with useful information for your target group, like "how to get accredited" or "access to our pr material" or "contact our pr manager".

Example 2 - Customer

You run an online shop and want to support your customers based on their needs.
Customers that are not logged in yet should see an assistant that helps them find the products they need and customers that are logged in should see an assistant that helps them with their existing order.
So you create two assistants, number on is targeting anonymous users to you use the user role condition and set it to anonymous. The other assistant is targeting logged in users so you use the user role condition set to role "customer".
Each assistant can have its own content, but for shared content, like general information, you can use the assistant library item and share the content across both assistants.

Dependencies

Blog posts

Activity

Total releases
2
First release
Dec 2025
Latest release
4 months ago
Release cadence
0 days
Stability
0% stable

Releases

Version Type Release date
2.0.x-dev Dev Dec 4, 2025
2.0.0-alpha1 Pre-release Dec 4, 2025