armedin

Cheers! If there's enough demand for it, I could consider adapting

Actually the initial plan was for this to be a course of demonstrating how to build these components. Perhaps if there's enough demand, I might consider that. And I get that not everyone will agree with the approach, but I’m trying to be respectful about it.

Honestly I came up with the name pretty quickly without really thinking about how it would sound to the end user. Definitely something I'll rethink; appreciate you pointing it out.

I'm delighted to hear you like the library! The 'coming soon' components mean they haven't been packaged yet, and specifically the text-blur-reveal is tricky to do. You can, however, access the raw code on GitHub. Essentially you have 2 ways, either via the npm package, or copying the raw code. There are more components coming, one being the Matrix-like effect. I haven't worked with Astro before, so cannot give an input on that.

Did you not receive the Github invitation? If not, please go to the profile and enter your github username to send an invitation.

There are 3-4 components which haven't been synced yet (cannot copy the raw code from the site), one being DataFeedingIn component. You can still access the code through Github.

haha so true! Apparently it was meant in the bad way

Grateful for the support! Just trying to build, learn, and put something useful out there.

Thank you!

yep, not trying to ignore that. It's all written in the title, and where the inspirations are taken from are in each component page.

Thank you very much! Would love to have you onboard whenever you're ready.

Thanks for the feedback. I totally agree with you. I will revisit this part and try to make it more intuitive

That's a great question. Right now, the components serve more as fancy decoration. But making the whole library more a11y-friendly is something I plan to do.

Every modern website has similar UI patterns. This is no different. All the code is originally written from scratch. You can’t copyright style, ideas, layouts, or vibes.

True — good optimization can get you both. It used to be way less performance, I already tried to optimise (at least until my machine was running it fine), but it seems like there's still much more that can be done

Thanks for the advice, I'll look into that

Thanks for pointing out the regulations part, I didn't realise I was giving that kind of impression. To be honest, it's my first time doing something like this, and I'm going to take the necessary steps as things grow.

Exactly. Not everything has to match everyone's personal taste, and that's totally fine.

That's something I have on my backlog

Yep, although I'm seeing the "Dock" more and more being used in recent websites

Yep, I'm glad you noticed! There are bits and pieces from different sites grouped together

Haha, I'd honestly love to see a ReverseReverseUI. Appreciate the thoughtful words

I appreciate you pointing that out. That’s not quite the experience I intended. The “Login to access the code” button should’ve been clearer upfront about requiring a purchase. I assumed the CTA button in the landing page would send that message. I'm planning to add FREE components as the library grows, so this is something I will revisit again.

AI isn’t quite at the point where it can recreate high-quality UI components just from a screenshot. Everything in this library was built by hand — no AI, no copied code. Just pure design and engineering effort. There’s a lot of work you don’t see on the surface.

Thank you! That's exactly the vibe I was aiming for.

Appreciate the support! Yeah, it’s mostly the overhead of billing and managing access per component. If the library gets big enough and there's more demand for à la carte, I’d definitely consider revisiting it. Just keeping things simple for now so I can keep building.

The early 2000s was the golden era of web.

Thanks for pointing it out! I'll fix it.

Appreciate it! À la carte is something I've thought about, but wouldn't work for this case. Feel free to reach me out on X

Shoot, I forgot to add the FAQ section. Thank you! The components are built with Framer Motion and MUI (just for the sx prop). You will have access to the raw code, github repo and the npm package. If the component needs to be modified heavily, you can use the raw code. There's still more work that needs to be done to handle the full customisation via the npm package. I didn't use tailwind strictly because existing solutions all tend to use tailwind and shadcn, leaving other developers who don't use tailwind with not many options.

capitalism made me do it.