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.
composer.json
Outdated
| "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
|
|
||
| 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. |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| 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: |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| @@ -0,0 +1,39 @@ | |||
| ibexa: | |||
| system: | |||
| default: | |||
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| @@ -0,0 +1,39 @@ | |||
| ibexa: | |||
| system: | |||
| default: | |||
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
|
|
||
| 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. |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| 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)
| Users can complete a tour with one of the following actions: | ||
|
|
||
| - by finishing all steps | ||
| - by skipping it with the **Exit tour** button |
There was a problem hiding this comment.
This button differs depending on the tour type. Target tour has "Exit tour" button but general tour exit button has "Skip" label.
| ``` | ||
|
|
||
| The product tour scenarios are meant to be translatable. | ||
| It's recommended to use translation keys instead of literal values in the YAML configuration, and provide the translations separately. |
There was a problem hiding this comment.
How about "Ibexa recommends..."? I don't like "we recommend", which prevails in our doc, but would suggest trying to eliminate passive voice
Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com> Co-authored-by: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com>
code_samples/ change report
|
|



Target: 4.6, 5.0
Documentation for the Product Tour feature - an extension of Integrated Help.
TODO: screenshots are missing in indicated places
User doc PR: ibexa/documentation-user#390
Covers https://github.com/ibexa/integrated-help/pull/59 and https://github.com/ibexa/integrated-help/pull/58 as well