-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
UI Framework 11
-
5
User story:
My site deals heavily with assets. I want to see assets higher in results because I work with them often.
My site doesn't use Stories very often. I want to demote them in the Suggestions order.
I have a custom app Products that is very important for my users. I want to make it higher in Suggestions.
The default group ordering (MGNLUI-4728) doesn't know what is important to users on a particular site. For example, Assets are in place #5 which may be too low. Make it easier for a practitioner to change the category order through configuration, for example via YAML.
Business benefit: Relevance. Content types that are important to your daily work are listed first.
Acceptance criteria:
- A system admin can configure the group order.
- A system admin can configure the number of suggestions & results in each group.
- A system admin can configure the find bar to include/exclude specific user realms as last editors (see
MGNLUI-5523) - Configuration is in a YAML file.
- A developer can deploy new Magnolia sites with the correct group order.
- Consider making everything in the Find Bar class configurable without having to touch code.
- clones
-
MGNLUI-4728 Predictable result category order
- Closed
- depends upon
-
MAGNOLIA-6521 Module config via Light Module
- Closed
-
MAGNOLIA-7432 Draft concept for component configuration in light modules
- Closed
- is depended upon by
-
MGNLUI-4676 Find Bar search is configured by admin for groups and roles
- Closed
- relates to
-
MGNLUI-5523 Findbar queries all public users on initialization of admin central
- Closed
-
MAGNOLIA-7691 Populating the last editor filter drop down of the find bar causes performance issues with many users
- Closed
-
MGNLUI-5428 Find bar: load more results
- Closed
- to be documented by
-
MGNLUI-5547 DOC: Admincentral module (new page)
- Closed