Gamify and clarify the steps of the authoring process #11
ntnsndr
commented
Owner
- Make the outline more persistent and visible during authoring, as progress
- Highlight one Component at a time
- Use a visual metaphor like a traveling honeybee or something, someone building
- Gamification! Celebrate users for their progress.
- Encourage focus and attention on each step in relation to appropriateness to community
- Hide the formatting tips unless users want them, make them always available
- Add self explanatory Components---tooltip for questions
- Formatting tools should be clearer about Header recommendations
- Maybe have an edit button to edit the fields. Edit the fields one at a time
- Make clearer that Assessment and Deliberation are a loop, avoid redundancy
- Make the outline more persistent and visible during authoring, as progress
- Highlight one Component at a time
- Use a visual metaphor like a traveling honeybee or something, someone building
- Gamification! Celebrate users for their progress.
- Encourage focus and attention on each step in relation to appropriateness to community
- Hide the formatting tips unless users want them, make them always available
- Add self explanatory Components---tooltip for questions
- Formatting tools should be clearer about Header recommendations
- Maybe have an edit button to edit the fields. Edit the fields one at a time
- Make clearer that Assessment and Deliberation are a loop, avoid redundancy
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: dispute-protocol/builder-prototype#11
Reference in New Issue
Block a user
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?