Hello,

I’m a Sr Dev who mostly has done back-end work but I’m “dangerous enough” in front end frameworks to get things done in my job.

I have another Sr Dev on my team who is ADAMANT on using ul/ol’s everywhere. And I mean EVERYWHERE.

Navigation menu items will get done as a list.

Say I have a list of key value pairs or tags describing an item on a page, that’s a list. If there are two sections on a page that’s also a list. Even forms are built as lists of inputs and buttons. To the point where I’m positive if I told them to recreate the google front page I’m 100% they’d make a ul and a li for the image, another for the box and a separate li for the buttons.

My frustration is that every piece of documentation regarding ordered lists and unordered lists are for literally listings out items as numbered or bulleted lists, not logically grouping things on a page. Also our code is littered with extra css to strip out the bullet points and numbers on a basic li item.

I’ve worked on several projects and this is the first time I’ve ever seen lists so overused. Is this normal on some projects? It feels wrong but I don’t know the exact terminology to use to explain why, given my inexperience in front end development.

  • autokludgeEnglish
    3•1 month ago

    Try not to look too much at what the default browser styles are, just think purpose.

    • Nav items are ultimately a list of links for other pages.
    • a list of tags for an item matches intent.
    • Form inputs: IDK, list items feels like stretching the meaning (eg https://v1.tailwindcss.com/components/forms#form-grid)
    • Sections: why not just <section>1...</section><section>2...</section><section>3...</section>

    Maybe your coworker possibly suffers from list-itis, after tying too hard to prevent div-itis?
    What do you mean about littered with css? Do you have a default reset style, or a simple util class to remove these? Or is your html littered with style=“” everywhere?