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
I am now working on the products page in https://buildinframe.com (WIP)
Each plugins, components from me now has a page to explore.
leaderboard also stays.
This is a smart way to turn the plugin library into a product experience—the dark UI and focused blue CTA make the catalog feel cohesive. I’d consider giving the filter and search states a little more visual hierarchy as the collection grows.
Thanks you Rohan ❤️
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
Related posts
A focused landing page helps visitors understand the product and explore the offer without unnecessary distractions.
For this project, the landing page presents the product through a dedicated shopping experience.
When building landing pages, I focus on the offer, page structure, product information, visual hierarchy, and clear calls to action.
Check out the landing page here:
https://lovenood.com/pages/landing-page-psk
Need a dedicated landing page for your product or campaign? Let's discuss it.
#LandingPageDesign #Shopify #EcommerceDesign #ConversionFocusedDesign
The four icon benefits next to the photo are easy to scan, and the ELLE and GLAMOUR badges add quick trust. Does the Add to Bag button stay sticky on mobile?
Pagina is live. It is a portfolio website template for product and brand designers and small studios, with nine page types, light and dark mode, and layouts for desktop, tablet and phone.
It is free on Framer, and the full source code is $5. Details and live demo: https://vstd.si/templates/pagina
Not every new feature needs its own screen.
It's something worth thinking about when a digital product starts growing.
A new feature gets introduced, so a new page is created.
Then another feature arrives. Another page. Another menu item.
Eventually, the navigation starts reflecting everything the product has accumulated rather than how people actually use it.
And that's where things can become unnecessarily complicated.
When you're designing or improving an existing product, adding functionality isn't just about finding space for another interface.
It's about understanding how that functionality fits into the workflows people already have.
Imagine an invoicing platform introducing automated payment reminders.
You could create an entirely separate section for managing them.
Or you could integrate that functionality directly into the invoice workflow, where users already have the relevant context.
Both approaches can make sense.
If the feature involves complex configurations, reporting, or needs to be managed independently, a dedicated section might be justified.
But if it's something people naturally need while completing another task, moving them to a separate screen could introduce unnecessary steps.
I think this is particularly important with established products.
Every new feature affects more than the area where it appears.
It can change navigation, information hierarchy, existing user habits, and the overall complexity of the experience.
And the more a product grows, the more important those decisions become.
Sometimes introducing a new capability means creating an entirely new experience.
Other times, the stronger solution is making that capability feel like it has always belonged there.