3-step moderator onboarding process #59
Labels
No labels
bug
enhancement
good first issue
halted
help wanted
security
wait for upstream
wait to be tested
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: b3yond/ticketfrei#59
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Author: @b3yond Posted at: 26.10.2018 18:13
Is your feature request related to a problem? Please describe.
When we are generating the default markdown texts for the settings page, we don't have things like twitter username, mastodon username, telegram username yet. So we only ask the user to manually exchange links with the actual accounts they want to register.
Describe the solution you'd like
If we had a 3-step moderator onboarding, we could first ask the mod to connect their accounts, then to specify good- and blocklist, and then to change the city and mail subscription page.
This would also provide a better user experience - more steps in which we can tell the mod what to do when. We would need less cryptic hard-to-find explanation text, and had more clear recommendations/commands.
Describe alternatives you've considered
I only considered the status quo. It's suboptimal.
Additional context
If we had a mockup we could make some screenshots...