Join
3
3 Comments

5 Reasons to use headless components

by Jordie Hall

5 reasons to use headless components

Headless components reduce development time, but also open up a whole new avenue for interfaces that can be generated on cue.

getmorf.io
Avatar for Jordie Hall Jordie Hall
submitted this link on April 5, 2022
Say something nice to jordiehall…
Post Comment
  1. 1

    Interesting. Would love to see some visual examples. Have a hard time imagining what the headless components would look like.

    User Avatar finnstrand
    ·
    4 years ago
    ·
    Reply
    1. 2

      If you check out the links to Headless, Aria, and Radix UI's in the article you can get a sense of how they look. The point of using headless components is that you can style them however you want. What they give you is functionality, interaction, and accessibility that has been well tested. You can take that and dress it up how you like easily because it's not coming pre-wrapped in styles and classes that you have to undo.

      Avatar for Jordie Hall jordiehall
      ·
      4 years ago
      ·
      Reply
      1. 1

        Oh, interesting, will look further into this. Have you made you own library or are you using one of the ones you mention?

        User Avatar finnstrand
        ·
        4 years ago
        ·
        Reply
Trending on Indie Hackers
AI runs 70% of my distribution. The exact stack. User Avatar 148 comments I'm a solo founder. It took me 9 months and at least 3 stack rewrites to ship my SaaS. User Avatar 137 comments Show IH: I'm building a lead gen + CRM tool for web designers targeting local businesses without websites — starting with Spain User Avatar 79 comments I built a URL indexing SaaS in 40 days — here's the honest story User Avatar 58 comments We could see our AI bill, but not explain it — so I built AiKey User Avatar 25 comments AI coding should not turn software development into a black box User Avatar 13 comments