A dropdown nest
Podcast |
Frontend First
Publisher |
Sam Selikoff, Ryan Toronto
Media Type |
audio
Podknife tags |
Design, 
Technology, 
User Experience, 
Web Development
Categories Via RSS |
Technology
Publication Date |
Oct 30, 2018
Episode Duration |
00:55:35

Sam and Ryan talk about the challenges of building nested dropdowns, whether a component reading data from its children is an anti-pattern, how angle-bracket syntax encourages new components, and whether “CSS best practices” exist.

Topics include:

  • 00:40 – Thinking through a nested drop-down navigation menu
  • 35:15 – Building an component & angle-bracket syntax
  • 45:00 – Layout UI primitives
  • 46:35 – What are CSS best practices? How might Tailwind encourage these?
  • 52:17 – "Semantic" classes. Should developers have to name every UI element, if designers don't?
Sam and Ryan talk about the challenges of building nested dropdowns, whether a component reading data from its children is an anti-pattern, how angle-bracket syntax encourages new components, and whether “CSS best practices” exist.

Sam and Ryan talk about the challenges of building nested dropdowns, whether a component reading data from its children is an anti-pattern, how angle-bracket syntax encourages new components, and whether “CSS best practices” exist.

Topics include:

  • 00:40 – Thinking through a nested drop-down navigation menu
  • 35:15 – Building an component & angle-bracket syntax
  • 45:00 – Layout UI primitives
  • 46:35 – What are CSS best practices? How might Tailwind encourage these?
  • 52:17 – "Semantic" classes. Should developers have to name every UI element, if designers don't?

This episode currently has no reviews.

Submit Review
This episode could use a review!

This episode could use a review! Have anything to say about it? Share your thoughts using the button below.

Submit Review