The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
CMS-powered sound system in an AI template.
Built with Framer
Turn sound on 🔊
Using Framer CMS to drive sound entries is a smart architecture. Each sound as a CMS item means the library scales without touching the component.
The CMS-powered approach is smart here. Sound libraries in Framer templates usually feel like afterthoughts, but this actually looks structured and usable.
Good work
Thank you Rasel 🙌
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
I usually don't stop at 3 breakpoints when building a website.
Most people think about: Mobile, Tablet, Laptop
I like adding one more: Desktop
Because what looks great at 1440px can feel completely different at 1920px...
- The layout gets too wide.
- Spacing starts feeling off.
- Content loses its balance.
So I like testing the system across: Mobile → Tablet → Laptop → Desktop
Not because every website needs exactly 4 breakpoints. But because responsive design isn't about making a few screen sizes work.
It's about making the whole system work.
Follow Rushabh for more website fundamentals, experiments, and things I learn while building for the web.
Wide screens expose spacing issues that laptop previews can hide.
cool
A calm interface doesn't have to feel static.
With RISE, the interactions are deliberately restrained.
A subtle hover gives just enough feedback to make the interface feel responsive, without breaking the slower, more considered visual language.
No big effect.
Just a small response at the right moment.
Restraint like this is way harder to pull off than a flashy effect, most sites can't resist doing too much. Was there an interaction you built and then cut because it felt like it was showing off?