Ticket #13152 (confirmed Feature Request)

Opened 4 years ago

Last modified 4 years ago

Improve Content Rules UI

Reported by: vangheem Owned by: vangheem
Priority: minor Milestone: 4.x
Component: User Experience and Interface Version: 4.2
Keywords: Cc: optilude

Description (last modified by vangheem) (diff)

Basic new concepts of UI are:

  • Make some of the fields less confusing
  • No more checkbox click, then action. Have edit, delete buttons beside list elements
  • Use popups forms so there are less new page loads
  • Do not use drop downs to select UI functions, should only be used for field values

Other ideas

  • Ability to assign rules via rule page
  • more information on where rules are assigned and if there are no current assignments
  • more glue between rule assignment screen and rule management screen


Content+Rules+Main.png Download (81.3 KB) - added by vangheem 4 years ago.
Content Rules Main Page
Content+Rule+-+Add+Rule.png Download (62.1 KB) - added by vangheem 4 years ago.
Adding a content rule
Content+Rules+-+Edit+Rule.png Download (130.8 KB) - added by vangheem 4 years ago.
Editing a content rule
Content+Rules+-+Add+Rule+Condition+1+of+2.png Download (113.1 KB) - added by vangheem 4 years ago.
Add content rule condition

Change History

Changed 4 years ago by vangheem

Content Rules Main Page

Changed 4 years ago by vangheem

Adding a content rule

Changed 4 years ago by vangheem

Editing a content rule

Changed 4 years ago by vangheem

Add content rule condition

comment:1 Changed 4 years ago by vangheem

  • Component changed from Unknown to User Experience and Interface

comment:2 Changed 4 years ago by optilude

Looks good!

A couple of thoughts:

  • A tickbox for "Disable content rules" is like a double negative. We should have an "Enable content rules" box that defaults to ticked instead.
  • The "row of buttons in a table" design often ends up being a bit fiddly. I think it can work here, but it may be worth considering Alice's "tile" design that we used in the new theme editor
  • On the edit screen, under "Actions", I think the second table column should be called something other than "Condition"

comment:3 Changed 4 years ago by kleist

  • Status changed from new to confirmed
  • Type changed from Bug to Feature Request

comment:4 Changed 4 years ago by vangheem

  • Cc optilude added

Martin, I've had people be confused by the current global enabled wording. Basically, they think the rules they created, without assigning them, all get applied globally or something like that.

comment:5 Changed 4 years ago by vangheem

  • Description modified (diff)

comment:6 Changed 4 years ago by thomasdesvenain

This morning at plone conf sprint we detailed some specifications


Edit, Delete and Disable are buttons (not images) Javascript Confirm when deleting Filter is done in pure javascript (no ajax reload of table when change filter options) Delete and Enable actions throw ajax. the row is updated in pure javascript (no ajax reload of the table) Add button is both on top of and at the bottom of the table (before the filter)

Disable content rules checkbox uses ajax (save button removed when we have javascript) a message notifies the user it has been saved

If some rules are enabled but not assigned anywhere, we get a warning message on the top of the page In the table, in enabled column, enabled but not assigned rules are visually marked


We click on "add a rule" we are redirected to the add form we fill at least required fields we click on save we stay on the same page wich now contains the additional fieldsets

  • the descriptions, titles and styles of the add and edit page will be made consistent


the list of conditions and actions are in a table at the bottom, assignment section is displayed event if we have no assignment (then we have "no assignment" message) if we have no assignment, a warning message at the top remains me


in condition (or action) fieldset, we have an "add" button (condition or action type selection list is removed) when we click on the button, an overlay is opened, we have the list of the condition types displayed as an accordion when we click on one of them, the accordion will open, and we get there the condition (or action) properties form


Breadcrum on a rule should display the title of the rule not ++rule++ etc thing Breadcrum on an action should display "Action 0" instead of ++action++0

Note: See TracTickets for help on using tickets.