@Mandy_Kerr @b_e_n_t_e_n @mattaningram@Hicksyfern@hankchizljaw It's not that simple. Knowledge of a technology like tailwind is different that knowledge of how *this* particular project's CSS is written and organized. One is obviously more general and transferable.
@Myotherpants@carolstran@sarah_edo At the very least, use <nav>. It makes it so much easier for vision impaired users to jump straight to your navigation
@Myotherpants@carolstran@sarah_edo It's not about websites vs. web apps. It's about accessibility. Try using a screen reader on a web app with semantic html vs. one with all divs, and you'll see the difference.
@Myotherpants@carolstran@sarah_edo I still don't have a great feel for when to use <article>, so I don't use it too often. I use <section> anytime I have a section of content with some kind of heading. So on a dashboard, I would say each panel or card could be a section?