Actions
User story #17908
openGet started guide to introduce user to technique editor workflow
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Medium
Name check:
To do
Fix check:
To do
Regression:
Description
This guide aim to present the different parts of the technique editor (resources, parameters, generic methods) the user may be able to trigger the guide with a button.
Ideally we should create a simple technique in the same time, for instance, a "Demo user" as documented, but some case must be considered :
How to deal if the technique already exist (same name) ?
Ideas:
- Provide a "Demo user" technique on the install
- Reserve the name => ok but what if the technique exists but with other methods ?
- Increment a number in the name (I.E "Demo user X")
Actions