Content
View differences
Updated by Henriette Darge over 7 years ago
The onboarding tour reveals several unsatisfying truths, which might increase the frustration.
This was taken from https://github.com/opf/openproject/pull/6743#issuecomment-432965149
### Separation of concerns
* We have a project seeder for a Scrum project within the core(!), although the core should not know anything about the backlogs plugin.
* The tour (also part of the core) relies on the presence of the backlogs project as well.
To clean this up, we could move all project seeders and the tour to a new plugin, let's say `openproject-guides` with dependencies to all plugins that the tour assumes to be present.
If we do that, we would also need to move the toggling of the setting `demo_projects_available` (deactivation of the tour when demo projects are not available) into that plugin.
In case we unify the plugin situation in the future we should think of this, too.
### Static seed texts for things that are dynamic
We lose control over the tour when people change/modify/delete
1. the demo projects data, or
2. the demo projects modules, or
3. the project overview pages
4. the home page
We already have real issues for 4.
* We link to admin/project-admin-only features, not in the tour but in seeded data, and show that link to everybody (so without the correct permissions). Here we could simply add hints that it is a admin-only links.
For fixing 1. and 2. we probably would need to distinguish between **tour projects** and **play around projects** and stop mixing those two up. **Tour projects** would only be visible from within a tour so that people cannot modify it (providing the tour does not change the data).
I am not sure, what to make with these truths now. Use more videos instead of interactive tours? They would be a pain to keep up to date, too. Or simply live with these issues saying "works out of the box" but breaks if you touch anything? This is OK, as long the tour focusses on the very first user, the admin. But that is not optimal as many subsequent users need a tour, too.
This was taken from https://github.com/opf/openproject/pull/6743#issuecomment-432965149
### Separation of concerns
* We have a project seeder for a Scrum project within the core(!), although the core should not know anything about the backlogs plugin.
* The tour (also part of the core) relies on the presence of the backlogs project as well.
To clean this up, we could move all project seeders and the tour to a new plugin, let's say `openproject-guides` with dependencies to all plugins that the tour assumes to be present.
If we do that, we would also need to move the toggling of the setting `demo_projects_available` (deactivation of the tour when demo projects are not available) into that plugin.
In case we unify the plugin situation in the future we should think of this, too.
### Static seed texts for things that are dynamic
We lose control over the tour when people change/modify/delete
1. the demo projects data, or
2. the demo projects modules, or
3. the project overview pages
4. the home page
We already have real issues for 4.
* We link to admin/project-admin-only features, not in the tour but in seeded data, and show that link to everybody (so without the correct permissions). Here we could simply add hints that it is a admin-only links.
For fixing 1. and 2. we probably would need to distinguish between **tour projects** and **play around projects** and stop mixing those two up. **Tour projects** would only be visible from within a tour so that people cannot modify it (providing the tour does not change the data).
I am not sure, what to make with these truths now. Use more videos instead of interactive tours? They would be a pain to keep up to date, too. Or simply live with these issues saying "works out of the box" but breaks if you touch anything? This is OK, as long the tour focusses on the very first user, the admin. But that is not optimal as many subsequent users need a tour, too.