[MGNLUI-2353] Review proposal for app stack navigation Created: 25/Oct/12 Updated: 03/May/19 Resolved: 03/May/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
I've written a concept page on app stack navigation. Its goal is to define a way to navigate our web app in a useful and productive manner. http://wiki.magnolia-cms.com/display/UX/Navigating+the+app+stack The page defines what a location is and how it corresponds to a URL fragment. It looks at which of these locations need to be bookmarkable and which should also end up in the browser history. It also defines some cases where some specific support for the Back buttons would be desirable as well. This has been discussed with some of the dev team and reviewed with Philipp already. I've summed this all up, but also discovered some additional points we have to consider. Before implementing any changes, this concepts thus has to be properly discussed again, also because it contains a number of changes to URL fragments, which we have to verify and agree upon. |