flutter
Help surface layout widgets for multiple different design languages
What information needs to be added?
A quick look at this page (https://docs.flutter.dev/ui/widgets/layout) seems to show that it is largely design language independent layout options. (modulo Carousel, which is from the Material library)
If there are Cupertino-specific layout widgets/options, we should consider:
- Adding a Cupertino Layout catalog somewhere on the site
- Adding a Material Layout catalog somewhere on the site
- Making https://docs.flutter.dev/ui/widgets/layout clear that it is design language independent layout options
- Cross link all these catalogs (if you are looking at generic layout options, you can learn that there are other layout options over in other design language catalogs)
Where should this new content appear?
No response
I would like to fix this problem.
- [ ] I will try and fix this problem on docs.flutter.dev.
@Piinks can you recommend someone to help assess if there are "Cupertino Layout Widgets" that we'd want to better surface somehow? Thank you!
Drive by comment. I'm not sure if there are any Cupertino widgets that would fit perfectly, but two that comes to mind are: CupertinoListSection and CupertinoFormSection
They layout their children into a iOS styled list or form respectively, but both ask that you use specific widgets as children to get right native look, so I'm not sure if they are composable as the rest of the widgets on that page.
We may have some new ones to add as a result of the work we are doing now. Is this looking for 'the state of right now' updates? Or organizing updates for the future after we've completed some of our work?
Good question. I think "right now" would be sufficient. Once we have the few we have now onto the Layout page, we can always keep adding to it.
Reviewing this, I wonder if we need a design language section on the layout page? All the widgets there (yes, modulo carousel) are basic building blocks from the widgets layer.
If we add a section for cupertino, does that mean we will add a section for material? And if so, do we run the risk of conflating basic building blocks with design languages?
Good question! I could definitely see /ui/widgets/layout evolving to just "basic building blocks from widgets layer" and then other pages like /ui/design-languages/cupertino/layout and /ui/design-languages/material/layout
Evolving to something like that?
(if that's the aligned direction, I'll be happy to rejigger this issue's title and purpose)
Sure! Is there an action item right now then?
docs.flutter.dev is not managed by the framework team. cc @sfshaza2
Action Item now would be work with Tech Writers to solve for:
- making space for various design language's layout options (material, cupertino)
- make the current Layouts page more clear that it's generic and not affiliated with a specific design language
- update the title of this issue :)