Improving the usability between "custom block" and "content"

Created on 21 May 2011, over 13 years ago
Updated 19 June 2023, over 1 year ago

Updated: Comment #51

Problem/Motivation

This issue was filed after usability testing at UMN2012. When the participants where asked to create a sidebar block they went to "Create content". They created their content in a 'Basic Page', and were subsequently disappointed that they couldn't move or display the content in a sidebar block, without generating it again as a custom block.
See [webchick] original post below.

Proposed resolution

Note: Drupal uses a different approach between nodes based on content types and 'entities'. This discussion also uses the separation between secondary and primary content. It is too late to remove the concept of custom blocks from Drupal 8 core (#47); however there are other ways to improve the usability:

  • Rather than changing the idea of custom blocks, we could improve the usability around block management.
    e.g. moving access to the custom blocks as a tab "blocks" to the /admin/content tabs (between Content and Files) #50.

Further

  • Consider a '"Content" entity that can encompass functionality of both blocks and nodes'.
  • Enable displaying a node as a block #29

Potential Workaround

In many cases this might be a 'training issue' or a 'content strategy' issue, so define website specific business rules for when to use block and when to use nodes.

Also look into:

Related

  • Pages and Components paradigm here: Core Context UX: Page & Component library. (#22)

Remaining tasks

  • decide on approach, and list implementation tasks
  • consolidate with related issues and discussions

User interface changes

- To be determined (see above)

API changes

- To be determined (see above)

Original report by [webchick]

Without fail, every. single. person who participated in usability testing at UMN went to "Create content" when asked to create a sidebar block. They were subsequently disappointed that they couldn't take the "basic page" they'd just created and move it into the sidebar block, but had to type it all over again once they called the helpdesk and were pointed to the right place.

Possible solutions we discussed:
- Remove the concept of "Blocks" entirely; simply allow any piece of content to be exposed as blocks are now.
- Make Block a content type.

πŸ“Œ Task
Status

Closed: outdated

Version

11.0 πŸ”₯

Component
Block contentΒ  β†’

Last updated 20 days ago

Created by

πŸ‡¨πŸ‡¦Canada webchick Vancouver πŸ‡¨πŸ‡¦

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Most of the issues from the meta were resolved. More importantly moving custom block library to under content and renaming to just block content.

    If still more to be done please reopen.

Production build 0.71.5 2024