Page History

Might get reworked to be a full-fledged search function

Story

I can easily search for pages from anywhere while I browse the pages of a site. The search is launched against actual content of all pages as well as typical textual elements such as the page titles and name and author and group names.

...

The resulting list of pages can be additionally filtered by asset type item set (if applicable), sorted and grouped exactly as possible in a page list. Basically, a page list is transformed into a search results list using clearly different visuals (mostly colors), but offers the same functionality including commands actions and preview views.

If the query text is changed, a new search is only launched, if the user hits a "search" button. In order to quit searching, the user clicks on a "done" button and is then returned to the view he was in before he initiated the search.

...

Advanced search queries may be saved to a special shelf of the content work areawork much as item subsets and thus are added to the tabs representing them at the top of the current view. The query itself and not the results are saved. The user is asked to provide a unique name for the query and to select a default view supporting the display of search results, if multiple such views are available.

In launching a saved query again, the user simply selects it from the list of tabs containing saved searches. Magnolia displays the selected default view (usually the page list) and the advanced search settings as if the user had entered all manually, then executes the search and shows the results.

Preserving context, updating the results

If the user switches to a different menu item while a basic or advanced search view is open, the query of the search is preserved. If the user later on switches back to the menu from where the query was launched, the basic or advanced search view is shown and the query executed again to ensure that *the search results shown are up-to-date".

Mockups

Basic search

Advanced search