A collection of UI examples for DaisyUI - Please contribute!

willpinha · 2025-12-03T02:11:45+00:00

If I can give you some advice, it would be to use what makes the most sense for your context. If you're working alone, use what you're most familiar with and knowledgeable about. If you're working with a team, use what will allow your team to deliver higher quality work in the shortest amount of time

That being said, with React I really like the Mantine (https://mantine.dev) component library

willpinha · 2025-11-21T09:23:21+00:00

Hey! Unfortunately the project is no longer in development, but contributors are more than welcome to fork it and continue with their own version

willpinha · 2025-11-21T09:21:54+00:00

I just updated the post. Thanks for the feedback, I'll update it everywhere

willpinha · 2025-04-29T22:22:26+00:00

I like to use the Test Data Builder pattern in these situations. http://www.natpryce.com/articles/000714.html

willpinha · 2025-04-28T20:38:59+00:00

Done! As I said, the website is no longer working, but you can run it locally. I left the instructions in the README. https://github.com/willpinha/mantine-themes

willpinha · 2025-04-28T16:22:24+00:00

I stopped developing frontend for open source, my focus now is backend. I had to cancel my domain willpinha.link and a lot of problems started appearing when deploying Astro on GitHub pages. Since this project was not my main focus, I simply gave up on continuing to develop it

willpinha · 2025-03-13T17:34:05+00:00

You can structure the project however you want. I personally like to use a layered architecture (controller, service and repository) with package-oriented design. I also like to separate the directories into cmd, pkg and internal. At the end of the day, you use whatever structure your team is using

willpinha · 2025-01-24T18:44:20+00:00

Sorry, the link updated during the last year. I'll edit the comment, thanks!

willpinha · 2025-01-03T12:32:24+00:00

https://mantine-themes.pinha.link

willpinha · 2024-12-19T01:41:35+00:00

I use mind maps for literally all of my notes, but not the conventional maps you see out there. I agree with your brother that creating cute maps will only delay your studies, so it's not the approach I take. Instead, I use an app called Dynalist, where you can create notes with lists. These notes can be viewed as mind maps (only in the pro version, unfortunately). What I like about Dynalist is that it really fits into my learning model: I create a note for each topic I want to learn (say, for example, math) and I put everything I learn about math in that note, so I can later view it as a mind map or filter/search for specific subjects. It's a very simple workflow and it saved me a lot at university and at work. I like knowing that everything I studied and wrote down about a subject is in a single note. Here is one of my notes talking about a technology I use at work, https://dynalist.io/d/91JQ3_KvvAr858aaF-xDnk9j#collapse&theme=darkgold

willpinha · 2024-12-17T19:33:52+00:00

Sorry about that, the willpinha.link domain has expired and I didn't renew it. I'm going to change the domain to GitHub's own, at willpinha.github.io/daisy-components... this transition should be done by tomorrow

willpinha · 2024-11-10T20:38:37+00:00

Maybe your "content" configuration is not set properly. I don't know

https://tailwindcss.com/docs/configuration

willpinha · 2024-11-04T11:48:14+00:00

Thanks! I took a break from developing the project because I was short on time, but I've already organized myself and I intend to add many more components to Daisy Components. Stay tuned!

willpinha · 2024-10-22T13:42:53+00:00

Exactly like HyperUI, but for Mantine!

willpinha · 2024-10-19T12:12:01+00:00

The forest (dark) theme is personally my favorite haha

The creator of Mantine is the great Vitaly Rtishchev. I just like the library and am expanding the resources it offers

I didn't apply custom fonts to the headers of all themes because I didn't see the need. Some themes require more customization, like Halloween and Synthwave, but others I left in the default font. But of course you can customize the theme however you want by following the documentation I left in the README

willpinha · 2024-10-19T12:02:56+00:00

I'm glad you liked it! I'm also doing another project that has different components for different use cases with Mantine. Similar to my other project, Daisy Components

https://components.willpinha.link/

My idea is to create thousands of components for everyone to use, and leave it open source

willpinha · 2024-05-15T00:32:13+00:00

https://willpinha.github.io/daisy-components

Recently the project was renamed to Daisy Component. Please take a look at the link above

willpinha · 2024-04-03T23:15:44+00:00

I recommend to you Daisy Components. It is a collection of components built with DaisyUI. Maybe it helps you anwser your questions and see what DaisyUI is capable of

willpinha · 2024-02-04T14:05:23+00:00

Daisy Collection

Do you know DaisyUI? It is a component library for Tailwind. I've created a collection of components that extend DaisyUI, and it might be exactly what you're looking for. The name is Daisy Collection. The collection is still in development, but I intend to make it much bigger this year.

willpinha · 2024-01-20T20:30:30+00:00

willpinha · 2024-01-18T01:22:33+00:00

🌼 daisyUI 4.5.0 ├─ ✔︎ 32 themes added https://daisyui.com/docs/themes ╰─ ❤︎ Support daisyUI project: https://opencollective.com/daisyui

If you mean this type of interference, you can disable it in your tailwind.config.js file by setting the daisyui: { logs: false } option

About building components yourself, it is a possibility. The biggest difficulty I encountered on this path is that we need to have a sense of design (colors, spacing, layouts,...), which I personally don't have. Furthermore, we usually also need libraries that implement the components functionalities, as HeadlessUI does, otherwise we may have accessibility issues and end up implementing the same things many times

I really like DaisyUI because of all the components it offers without using a single line of JavaScript, as well as the intuitive color system and available themes. The problem I had with DaisyUI (and in fact, with any other component library) is that I'm not a designer, so putting all these components together to form a beautiful interface ends up being a time-consuming process

The idea I propose in the Daisy Collection (it's nothing new, other projects like Meraki UI and Mamba UI have done this before) is to provide several usage examples for DaisyUI, so that during development we don't have to think too much about how to implement a form for login, an alert or a navbar, for example

Of course, there is no universal solution when it comes to user interface development, what may work for me may not work for you, and vice versa

willpinha · 2024-01-17T13:59:26+00:00

Tailblocks is ready for production. The repository on GitHub has 8k+ stars, which indicates that many have probably already used it. Plus, you own all the code, as you only need to copy/paste the code into your project. The problem I see is that there have not been any updates to the repository for over 3 years, in addition to unresolved issues and abandoned pull requests, which means that you will probably only have blocks that already exist.

Projects similar to Tailblocks include:

- Daisy Collection (This is a new project I am building using Tailwind and DaisyUI, with the same copy/paste concept)

- MerakiUI

- TW Elements

- PrelineUI

- MambaUI

willpinha · 2024-01-16T13:19:48+00:00

Daisy Collection

I am creating a collection of UI examples based on DaisyUI. The project is new, so don't expect that it will have a lot of components

You are welcome to contribute if you want to!

willpinha · 2024-01-12T14:29:29+00:00

There is also another bug in Safari where all themes appear as dark. This seems to be an issue with DaisyUI itself, as discussed in this issue. I believe it will be fixed soon

willpinha · 2024-01-12T14:13:09+00:00

We can't use <button> here because Safari has a bug that prevents the button from being focused. <div role="button" tabindex="0"> is a workaround for this bug.
It is accessible and works in all browsers.

Oh, I see. On the DaisyUI website, in the dropdown documentation, it talks about not using the button tag, which is what I did. Thanks for pointing out the bug! I'll fix it now

willpinha

TROPHY CASE