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
🚀 Excited to share my latest full-stack project: LUXO E-Commerce Admin Dashboard — built entirely with ASP.NET Core MVC!
This system includes:
✅ Admin Dashboard with real-time revenue & order analytics
✅ Complete Order Management (Pending → Confirmed → Shipped → Delivered)
✅ Product Catalog & Inventory Management
✅ Multi-payment method support (Credit Card, JazzCash, Easypaisa, Bank Transfer)
✅ Fully responsive design — works perfectly on all screen sizes
Working on this helped me strengthen my skills in .NET Core, MVC architecture, database design, and UI/UX implementation.
#DotNetCore #ASPNETMVC #EcommerceProject #WebDevelopment #Coding #PortfolioProject #PakistanDevelopers
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
Building a 4-role real-time SaaS taught me one uncomfortable lesson: the hard part was never the code.
I've been building RestaurantOS — one platform connecting Owner, Kitchen, Waiter, and Cashier in a single live workflow (Table → Order → Kitchen → Serve → Billing → Reports).
The tech stack was the easy part. The real challenge: keeping 4 different roles in sync in real time without any of them stepping on each other's data — a waiter updating a table while the kitchen marks an item ready while the cashier is mid-billing.
That forced decisions most tutorials never cover:
⚡ How much state should live client-side vs. source-of-truth server-side
⚡ What "real-time" actually needs to mean per role (a kitchen screen needs sub-second updates, a report dashboard doesn't)
⚡ Designing failure states — what happens when the waiter's app loses connection mid-order
Currently redesigning the UI/UX layer too (motion, better visual hierarchy) while keeping this real-time core intact.
If you've built multi-role or real-time systems — curious what broke first for you. And if you're a founder who needs something like this built, my DMs are open.
the role based flow is easy to follow. what part was hardest to keep real time?
🚀 My First Framer Marketplace Component — 3D Pill Button
I’m excited to share that my 3D Pill Button is now available on the Framer Marketplace! 🎉
I built this component to make modern CTA buttons easier to add to Framer websites — with a clean pill design, subtle 3D depth, smooth hover interactions, and customizable options.
✨ Features
3D shadow effect
Smooth hover & press interactions
Customizable colors
Native Framer font controls
Custom image or component icon
Adjustable icon size & rotation
Responsive sizing
Optional link support
Fully customizable from the Properties panel
No coding required
I’ve also made it available as a $5 one-time purchase.
🛒 Get the 3D Pill Button:
https://www.framer.com/marketplace/components/3d-pill-button/
🔗 Live Preview:
https://3dpillbutton.framer.website/
Would love to hear your feedback! If you’re a Framer designer or developer, let me know what you think and what component I should build next. 🚀
#Framer #FramerMarketplace #FramerComponents #WebDesign #WebDevelopment #UIDesign #NoCode #ProductDesign #IndieMaker
A purchase order arrives by email. 38 seconds later it's registered, stock is checked, the team is notified and the client has a confirmation. Nobody typed anything.
We filmed the PO intake agent in TechFoundry IMS end to end for the first time. Watch it here https://youtu.be/zoVYPD8qpCs
Email comes in, the agent reads the PDF line by line and matches every line to the catalog, the PO gets registered with a status timeline, and an acknowledgment goes back to the client with the same lines on it.
The boring parts are the ones that made it usable. Only approved senders get in. Every email in and out is logged. And the agent never touches stock levels, it registers and notifies, people decide.
The part that took longest wasn't the reading. It was the matching. A supplier's PDF never uses your part numbers, so "resolve to catalog" is where most of the real work sits.
If you're still keying POs in by hand, I'm curious what your inbox looks like on a Monday.
38 seconds, nobody typed anything