processwire/processwire-requests

Edit Template: Reuse template label on the Content tab #usability

Opened this issue · 2 comments

klor commented

Short description of the enhancement

How might we make it more visible to users which template their current page is using? Here is one suggestion:

Steps that explain the enhancement

When editing a template (/processwire/setup/template/edit?id=123), I want to reuse the template label as "Label for Content tab" so users see which template their current page is using (by seeing the word "Article" in the Content tab).

Current vs. suggested behavior

Current workflow: (for admin)

  1. Edit template
  2. Enter label "Article" (Basics tab)
  3. Go to Advanced tab
  4. In "Label for Content tab", enter "Article"

Better workflow: (for admin)

  1. Edit template "Article"
  2. Enter label "Article" (Basics tab)
  3. Click "[x] Use label for Content tab" (Basics tab)
  4. (Advanced users can still enter "Label for Content tab" on the Advanced tab)

Why would the enhancement be useful to users?

To make it (more) obvious to Editors which template, the current page is using.
Without this, an Editor would have to

Consider the workflow for an Editor without having "Template Label for Content tab":

  1. Edit Page
  2. Click Page Settings to view the current Template name
  3. Click Content, to go back to do your thing

Optional: Screenshots/Links that demonstrate the enhancement

Edit Template: Basics tab
image

Edit Template: Advanced tab
image

@klor The labels for both 'Content' and 'Children' tabs are already a configurable setting with the template, they appear on the Advanced tab when editing a template.

klor commented

@ryancramerdesign Thanks, I am aware of this. The purpose of my request is to get a small usability enhancement that makes life easier for Admin.

  • I was trying to emphasize this by writing:
    • "Better workflow: (for admin)" - and:
    • "To make it (more) obvious to Editors which template, the current page is using."

PS: If there is no time for small usability enhancements, then I fully understand and suggest that this issue is closed. There are only so many hours in a day.