🚀 𝗕𝘂𝗶𝗹𝘁 𝗮𝗻 𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝘃𝗲 𝗖𝗮𝗹𝗲𝗻𝗱𝗮𝗿 𝘄𝗶𝘁𝗵 𝗥𝗮𝗻𝗴𝗲 𝗦𝗲𝗹𝗲𝗰𝘁𝗶𝗼𝗻 & 𝗡𝗼𝘁𝗲𝘀 I recently worked on a frontend challenge where the goal was to turn a static wall calendar design into a fully interactive component — and I took it as an opportunity to focus on both functionality and product experience. 🔹 Key features: • 📅 Dynamic month navigation with smooth animations • 🎯 Date range selection (with reverse handling & hover preview) • ✍️ Notes system attached to selected date ranges • 💾 Persistent data using localStorage • 🖼 Dynamic hero images for each month • 🎨 Clean, responsive UI inspired by real wall calendars Instead of over-engineering, I focused on: → Clean architecture using custom hooks → Avoiding unnecessary state libraries (kept it simple & scalable) → Improving UX with small but impactful details 🔗 Live Demo: https://lnkd.in/gwfBCZw4 💻 GitHub: https://lnkd.in/gTPyR8zm Would love to hear your feedback! #react #frontend #javascript #webdevelopment #tailwindcss #framerMotion #uiux
More Relevant Posts
-
🧮 𝑆𝑖𝑚𝑝𝑙𝑒 𝐶𝑎𝑙𝑐𝑢𝑙𝑎𝑡𝑜𝑟 | 𝐹𝑟𝑜𝑛𝑡-𝐸𝑛𝑑 𝑃𝑟𝑜𝑗𝑒𝑐𝑡 Excited to share a project I recently built using 𝐇𝐓𝐌𝐋, 𝐂𝐒𝐒, and 𝐉𝐚𝐯𝐚𝐒𝐜𝐫𝐢𝐩𝐭 — a modern, responsive calculator designed with a strong focus on clean UI, usability, and smooth user experience. 🔹 Implements core arithmetic operations with real-time calculations 🔹 Built using DOM manipulation to handle interactive button inputs 🔹 Fully responsive design that works across different screen sizes 🔹 Lightweight and fast performance with clean code structure Through this project, I strengthened my understanding of JavaScript logic, event handling, and dynamic UI updates, while also improving my front-end development skills. I also explored how small UI decisions can significantly improve user experience and interaction flow. 🌐 Live Demo: https://lnkd.in/gcsCzzTa 💻 GitHub: https://lnkd.in/gDZetHBU Looking forward to enhancing this project further with features like: 🕘 History tracking 🌙 Dark mode ➗ Advanced operations 🎨 UI animations Always learning, always building 🚀 #FrontendDevelopment #JavaScript #WebDevelopment #HTML #CSS #StudentDeveloper #Projects #BuildInPublic
To view or add a comment, sign in
-
Trying out the latest shadcn/ui lately and it just feels different. Most UI libraries box you in. This one doesn’t. You get clean components, full control over styling, and since it’s built on Tailwind, everything feels natural. What stood out while working with shadcn/ui: – Clean, minimal, and modern design out of the box – Fully customizable (colors, variants, layouts no limits) – Built on top of Tailwind, so styling feels natural and fast – No unnecessary abstraction you understand what you build – Perfect fit for dashboards and data-heavy interfaces Used it recently while working on PrepMate’s dashboard: • showing enrolled exams • weekly progress • phase-wise tracking If you’re building dashboards or any modern UI, shadcn/ui is definitely worth it. #shadcn #NextJS #TailwindCSS #Frontend #BuildInPublic
To view or add a comment, sign in
-
-
📸 "𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝘃𝗲 𝗶𝗺𝗮𝗴𝗲𝘀" 𝗺𝗶𝗴𝗵𝘁 𝗯𝗲 𝗴𝗼𝗶𝗻𝗴 𝗮𝘄𝗮𝘆. Not because they failed... but because we don't need them anymore. 🧠 𝗧𝗵𝗲 𝗼𝗹𝗱 𝘄𝗮𝘆 We used: 🔹 `srcset` 🔹 `sizes` 🔹 `<picture>` To guess which image a device needed. ⚠️ 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 🔹 Complex markup 🔹 Multiple image versions 🔹 Hard to maintain 👉 We were solving a platform problem manually. 🚀 𝗪𝗵𝗮𝘁'𝘀 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 🔹 Modern CSS (container queries, fluid layouts) 🔹 Smarter browsers 🔹 Image CDNs 👉 The platform now knows: 🔹 How big your image is 🔹 What resolution is needed 🔹 What to load 🧩 𝗧𝗵𝗲 𝘀𝗵𝗶𝗳𝘁 From: "Optimize images for devices" ➡️ to: "Let layout + browser handle it" 🧠 The real insight: Frontend evolution always follows the same pattern: 👉 We hack solutions 👉 The platform catches up 👉 Complexity disappears 🚀 The takeaway: 👉 The code you don't have to write anymore. 🔗 Source: https://lnkd.in/dwWHWCcb #Frontend #WebDevelopment #CSS #WebPerformance #UX
To view or add a comment, sign in
-
-
Can we actually build a <Popover /> component just like shadcn/ui from scratch? Yes — and it's easier than you might think. A few weeks ago, I was struggling with the usual popover headaches: - Z-index conflicts - Positioning issues inside deeply nested containers - Content getting clipped by parent elements with overflow: hidden Then I discovered (and truly understood) ReactDOM.createPortal. Here's the game-changer: By using a portal, we can render the PopoverContent outside the normal DOM tree — directly into the <body> (or a dedicated portal container). This instantly solves: - Z-index battles - Clipping and overflow problems - Complex positioning issues But I didn't stop there. I also added smart positioning logic (inspired by how shadcn + Radix UI works): → When the PopoverContent doesn't have enough space at the bottom, it automatically flips and appears on top of the trigger. → Same for left/right sides. The result? A clean, smooth UX that feels premium — exactly like shadcn/ui's popover. This small deep dive into frontend system design taught me something important: The real skill upgrade doesn't come from just copying components. It comes from understanding why they work the way they do — and then building them yourself. Portals + floating UI logic = powerful mental model for any overlay (tooltips, dropdowns, modals, etc.). Have you built your own popover or tooltip from scratch? Or are you still fighting z-index wars in your projects? 😅 Drop a comment — I'd love to hear your experience (and any tips you have!). #React #Frontend #WebDevelopment #JavaScript #SystemDesign #shadcn
To view or add a comment, sign in
-
“In my initial days of working with Three.js…” 😅 Mistakes I made while building real-world 3D systems (so you don’t) After working on dashboards + real-time environments, I realized — most issues weren’t visual… they were architectural 👇 ❌ Treating Three.js like a UI library 👉 Result: Messy structure, hard-to-scale code 👉 Instead: Separate scene logic, rendering, and state management ❌ Uncontrolled re-renders with React 👉 Result: FPS drops, unnecessary updates 👉 Instead: Use refs + isolate Three.js from React render cycle ❌ No optimization strategy 👉 Result: Performance bottlenecks at scale 👉 Instead: • Instancing • Frustum culling • Geometry merging ❌ Ignoring camera as UX 👉 Result: Confusing navigation 👉 Instead: Design camera like interaction system (OrbitControls, transitions, focus states) ❌ Heavy real-time updates without control 👉 Result: Lag in dashboards / live systems 👉 Instead: Throttle updates + batch state changes ❌ Poor resource management 👉 Result: Memory leaks in long sessions 👉 Instead: Dispose geometries, materials, textures properly ❌ No abstraction layer 👉 Result: Repeated logic, hard maintenance 👉 Instead: Create reusable hooks / controllers for scene logic 💡 Biggest lesson: Three.js is not about rendering objects. It’s about managing systems in real-time. 👉 The challenge is no longer visuals 👉 It’s performance, architecture, and experience 💬 What challenge did YOU face while scaling Three.js apps? #threejs #webgl #frontenddevelopment #3dweb #javascript #realtime #softwarearchitecture #reactjs
To view or add a comment, sign in
-
-
🚀 Built a Contact Form UI using HTML, CSS, and JavaScript Designed a responsive Contact Us section featuring input fields for name, email, subject, and message along with a Google Maps location embed. Added a clean layout, icons for contact details, and a styled “Send Message” button for better user interaction. This frontend focuses on usability, modern design, and responsive structure. #website_of_contact_form.
To view or add a comment, sign in
-
-
High-end Frontend Engineering with Next.js & Framer Motion Creating a premium digital experience requires more than just good design—it requires precise engineering. For this build, my focus was on: 🔹 Architecture: Leveraging Next.js for a scalable and performant foundation. 🔹 Fluidity: Orchestrating complex UI transitions with Framer Motion at 60fps. 🔹 Precision: Implementing a strict, minimalist design system using Tailwind CSS. It’s all about the intersection of clean code and high-end aesthetics. Live link: scarpa.pk Portfolio: shezardev.vercel.app #NextJS #FrontendEngineering #WebDevelopment #TailwindCSS #FramerMotion #SoftwareArchitecture #ShezarDev #UIUX
To view or add a comment, sign in
-
I just put Cursor’s new Design Mode to the test on my latest project, Nexus Strategy, and the results are honestly incredible. I managed to build out a Figma-style UI design and have it fully implemented in just 2 minutes. What used to take an hour of tweaking CSS and adjusting layouts is now handled through a visual-first workflow. It’s a complete game-changer for moving fast without sacrificing UI quality. Check out the repository here to see the implementation: https://lnkd.in/g35MWHtp If you’re a developer looking to bridge the gap between design and code, this update is a must-try. #CursorAI #WebDevelopment #SoftwareEngineering #NextJS #OpenSource #Productivity
To view or add a comment, sign in
-
📌 Understanding CSS Display Property The display property controls how elements are rendered on a webpage — making it one of the most important concepts in CSS layout. 🔹 display: none → Removes element completely 🔹 display: inline → Stays in same line 🔹 display: block → Takes full width 🔹 display: inline-block → Inline + supports width/height 🔹 display: flex → Modern layout system 💡 Key Insight: Choosing the right display type helps build clean, responsive, and structured UI. Currently exploring frontend concepts step by step and applying them in real projects. 👉 Which display type do you use the most? #CSS #WebDevelopment #Frontend #UIUX #Coding
To view or add a comment, sign in
-
-
The first question I ask on any project isn't about colors, fonts, or layout. It's this: what is the user trying to accomplish, and what is actively getting in their way right now? Everything I build flows from that answer. Navigation, hierarchy, interactions, error states. My job is to remove the obstacle, not add more decisions. Most UI problems aren't design problems. They're clarity problems. The moment an interface makes a user stop and think instead of act, it's failed. That's the difference between frontend that looks good and frontend that actually works. #FrontendEngineering #UserExperience #ProductDevelopment #ReactJS #WebDev
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development