jtomeck / kw-design-system Goto Github PK

The way the nav works is when you are on a top level page, the sub-nav shows up. This requires you to have too many clicks on mobile.

The current user experience of the menu is:

1. click menu
2. click top-level page
3. wait to load
4. click menu
5. click sub-level page

The user experience NEEDS to be:

1. click menu
2. click top-level page
   • click the page title to go to the page or
   • click a + or down arrow to expand sub pages list
3. If list is expanded, click sub-page

Figure out how to show various projects in portfolio as case studies and make a template for it

The way x-intersect works with threshold creates weird behaviors due to only firing the x-intersect when the threshold is met. So if I'm on step 1 and the specified threshold of step 2 enters the viewport, it highlights step 2. At this point, there is still a good chunk of step 1 visible and due to this, if I begin to scroll back up, the threshold is never detected for step 1 and therefore x-intersect is not triggered.

• Dashboard (add information for requesting help)
• Components
  • Alerts
  • ... TBD
• Guidelines
  • Color
  • Empty States
  • Hierarchy
  • Loading States
  • Motion
  • Spacing
  • Typography
  • Workflows
• Styles (TBD) - Not sure what I want this section to be. I don't want it to be a styleguide per se. Maybe a good place to add tricky css hacks and best practices? Open to ideas, or even cutting the section

If you start scrolling by swiping the header, search bar, or open menu the whole site scrolls, but the content below is hidden. If you scroll the content, just the content scrolls.

A goal I have on this project is to minimize the amount of work a user needs to do to add content. I'd like to ideally have the user not have to write any markdown or html, and I'd ideally like them to be locked to a content type/style guideline for editing (ie. the user can add a new section of content, but the structure, layout and styles are all predefined and locked).

The help section is for contacting the design team, requesting help with a ui/ux problem, creating an issue, etc.