lets talk task groups, not roles and certainly not personas in this context
A late summary of one of the two BoFs on Drupal admin UI improvements that we held at Drupalcon Vienna. An inventory of tasks for three main task domains: create/manage content, build structure/configure functionality and build functionality. Yes, these domains map to the types of roles we often use: content creator, site builder, developer. Problem with that is those role based labels make it too easy to forget that the same person often switches between multiple roles. Somebody who’s developing part of a content API will build a content type and create content in order to check their work.
Not complete and not in any particular order:
Create and manage content
- View content
- Review content
- Inline editing
- Schedule content
- Create revisions
- Link to external media
- Publish
- Search content
- Content relations
- Layout content
- Update site content
- Translate content
- Optimise SEO
- Revert a revision
- Delete content
- View content in context
- Import/export content
- Manage revisoins
- Moderate content
- Edit media
- Choose layout template
- Upload media
- Manage menu
- Manage content structure
Build structure and configure functionality
- Create entity types for information architecture
- Structure each entity type
- Define display options, globally
- Define display options, individually
- Create content curation(?) - views, lists, blocks
- Configure language options for translations
- Prepare site for themer/frontender
- Provide/improve user interface for other users
- Create roles
- Create permissions
- Access & read help/documentation
- Access reports
- Debugging
Building functionality
- Build the business logic
- Build integrations
- Create layouts
- Build data structures
- Provide APIs
- Write documentation
- Define permissions
- Provide configuration options
- Create forms
- Define lists of components
- Migrate content
- Fix bugs
- Update code/features
- Deploy
- Define cache rules
- Extend functionalities
Tags