Part of the Site ecosystem · 38 projects
Site Assistant allows you to create helpful guides that appear on your website to assist users. You can define specific conditions for when these guides should show, and fill them with various types of content or link to library items for reuse. This is useful for providing targeted help, like a journalist-specific guide or different support for logged-in versus anonymous customers.
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
Ask your assistant about Site Assistant
Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works
Depends on
Dependencies of the latest stable release
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.
More in the Site ecosystem
Most installed first
Activity
Release Timeline
Releases
| Version | Type | Core | PHP | Release date | |
|---|---|---|---|---|---|
| 3.0.0-alpha1 | Pre-release | 11 | Jul 3, 2026 | ||
| 2.0.0 | Stable | 10–11 | Jul 2, 2026 | ||
| 3.0.x-dev | Dev | 11 | Jun 26, 2026 | ||
| 2.0.x-dev | Dev | 10–11 | Dec 4, 2025 | ||
| 2.0.0-alpha1 | Pre-release | 10–11 | Dec 4, 2025 | ||
| 10.0.x-dev | Dev | 9–10 | Oct 9, 2023 | ||
| 10.0.0-beta1 | Pre-release | 9–10 | Oct 9, 2023 | ||
| 1.1.0 | Stable | 8–9 | Aug 3, 2023 |