Conversation
| alt_translation_key: tour.image.alt | ||
| - type: video | ||
| params: | ||
| # 'Big Buck Bunny' licensed under CC 3.0 by the Blender foundation. Hosted by archive.org |
There was a problem hiding this comment.
| "ibexa/share": "~4.6.x-dev", | ||
| "ibexa/phpstan": "~4.6.-dev" | ||
| "ibexa/phpstan": "~4.6.-dev", | ||
| "ibexa/integrated-help": "dev-dev as 4.6.x-dev" |
There was a problem hiding this comment.
TMP branch to make PHPStan happy
| With the following example, the scenario is modified to trigger only when certain conditions are matched. When the current user has a pending [notification]([[= user_doc =]]/getting_started/notifications/), a custom onboarding scenario is triggered. | ||
|
|
||
| First, define a custom product tour scenario. | ||
| It contains a placeholder step with a single block. |
There was a problem hiding this comment.
A scenario MUST have at least one step, with at least one block - that's why I need to add a placeholder step in Yaml and remove all of them in PHP code
code_samples/ change report
|
|
|
|
||
| Clickable and draggable modes are designed for single actions only (buttons, links). | ||
| You can't select an entire form. | ||
| If the interaction with the highlighted element results in redirection to a new page or opening a modal window where the previous target element can't be found, the "Previous" navigation step will be disabled. |
There was a problem hiding this comment.
the "Previous" navigation step will not be disabled.
| Embed images with alternative text: | ||
|
|
||
| ```yaml | ||
| [[= include_file('code_samples/back_office/product_tour/config/general_scenario.yaml', 21, 25) =]] |
There was a problem hiding this comment.
wouldn't be better to give a example with asset added to public folder. Before block give example that 'I add a photo public/img/welcome.jpg and in config put img/welcome.jpg
| ``` yaml | ||
| ibexa: | ||
| system: | ||
| default: |
There was a problem hiding this comment.
I think here can also be changed to admin_group
| @@ -0,0 +1,39 @@ | |||
| ibexa: | |||
| system: | |||
| default: | |||
There was a problem hiding this comment.
I think here can also be changed to admin_group
| @@ -0,0 +1,39 @@ | |||
| ibexa: | |||
| system: | |||
| default: | |||
There was a problem hiding this comment.
I think here can also be changed to admin_group
|
|
||
| For **general scenario**, the scenario appears at the earliest opportunity (on any page after logging in), with an exception of the user settings area. | ||
|
|
||
| For **targeted scenarios**, the scenario begins if the target element is found in the DOM. |
There was a problem hiding this comment.
Here too, with the exception of the user settings area.
| The steps building the scenario support three interaction modes: | ||
|
|
||
| - Standard - Users navigate between steps using "Previous" and "Next" buttons | ||
| - Clickable - Users must click the highlighted element to proceed to the next step |
There was a problem hiding this comment.
Just an idea: we can mention, that if someone would want to go to prev step in clickable or draggable mode it is possible only by restarting tour (for example via user setting after finishing tour)



Target: 4.6, 5.0
Documentation for the Product Tour feature - an extension of Integrated Help.
Contains still some TODOs, but initial feedback is welcome.
User doc PR: ibexa/documentation-user#390