-
Setup a basic **directory structure** adhering to the intended information-architecture as per Gatsby requirements.
**Information segmentation**
![FabricJS information segmentation](https://user…
-
As the library has grown, our information architecture for the API docs has become somewhat hard to navigate. Opening this issue for discussion on how we can improve it.
Questions:
* How to split …
-
Topics:
- introduce a proper owner stack
- introduce context node objects
- rely on the owner aware interface
See also: #6290
-
Following discussion of @dbuenzli feedback:
- Rather than recommend building `mirage-www` as part of tutorial, perhaps building a personal site would be more engaging?
- We should not hide how to repo…
-
as titled.We need to consider the sub-groups of GraphScope. Based on the features of engines like GIE, GAE, and GLE, design the shortest product interaction paths that cater to the target audience and…
-
- Map the current architecture for authed and un-authed users
- Identify inconsistencies and user experience issues with the URL and menu structure
-
Rather than displaying one of the reports, the landing screen should provide an at-a-glance overview of the entire dashboard. This means, at a minimum, links with explanations, to all the screens, or,…
-
We will be publishing new content on the Salt website, so need to revisit our IA and top-level site navigation to ensure we can accommodate that new content.
Obviously, we want our IA to be reasona…
-
- Organise info into tabs
- Create list view for merchants
- Charts, Supertaggers and similar info contained in the Stats tab
See images below as example:
![Desktop - Light 1](https://user…
-
I believe we need a section providing solutions or principles with proper reasoning on page layouts and flows.
Examples include:
- A dashboard page or hub page
- Flow when interacting with a thin…