Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate whether to use sections in the UI Kit #16

Open
GBKS opened this issue Jan 20, 2023 · 1 comment
Open

Investigate whether to use sections in the UI Kit #16

GBKS opened this issue Jan 20, 2023 · 1 comment

Comments

@GBKS
Copy link
Owner

GBKS commented Jan 20, 2023

Sections are intended as helpful organizational tools to split a big page visually into different areas. Helpful, but may also lead to super gigantic pages. Is it better to have more pages that are each more focused? Or are there other ways to use sections? Let's discuss and use them if they are helpful.

@chrislueders
Copy link

I think it doesnt need to lead to huge pages.
For Design Systems my structure is as follows:

  • Page = Component (ex. Button)
  • 4 Sections for each component/page:
  1. Documentation
  2. Figma Components
  3. Local assets of the component
  4. Examples (if there are a lot of optional properties)

But of course this is a bit different, if we have pages for user flows etc. with a lot of screens, but even that is great for prototyping, because you can use the sections to "save states" or "state management" in prototypes, see: https://youtu.be/Ohcvb3PPSE8?t=323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants