Closed xak closed 1 year ago
@jeannewalters Here is a very high-level story that could use some input.
@LeoT7508 @Jagoooo I went through the existing demo pages and added some suggestions for additional components and pages below. These ideally should be interactive and responsive:
Launchpad - we have a bunch of examples of this so maybe we just genericize one https://app.zeplin.io/project/5af44f6dcc8449a90ddad8e8/screen/5b05b65f958189c72e949e38
Dashboard/Overview
Object detail
Object Detail - Localized
Object Detail with Read Only Detail
Table (update existing demo page) Add the following:
Tree (update existing demo page) Add the following:
Tiles (update existing demo page)
List
This is the same as a table, we don't need this.
Multi Instance page - See https://experience.sap.com/fiori-design-web/multi-instance-handling-floorplan/
@jeannewalters @Jagoooo
Looks good to me. Will there be wires? Or I'll just work from the list?
@xak @Jagoooo @jeannewalters
I made some edits to the list Jeanne made. I also need more information revolving around the Launchpad & Dashboard/Overview pages, I don't have any real data to add here and the different teams I've reached out to don't have anything for these screens yet either. So will we shelf this until we have something real to add? Or will we make up something?
Newest design sheets for Floorplans can be found here:
https://app.zeplin.io/project/5b23c972a7bb309e08b88e95/dashboard?seid=5b2d2a140473da4f369473bc
https://experience.sap.com/fiori-design-web/get-started/#layouts-floorplans-frameworks
While the library is intended to allow for flexible layouts options to create custom interfaces, there are common patterns that should be available as starter templates.
Layouts
Each layout should consider shell-level elements, fixed element options, overflow scrolling, and responsiveness.
Floorplans
Each floorplan should consider placement of navigation, actions, and responsiveness.