I have been rebuilding my understanding of JavaScript by focusing on how UI systems behave - not just how to make them work. Recently, I built two small DOM-based projects as part of a structured learning path: • Toggle Text Component • Theme Toggle System Instead of focusing on features, I focused on how UI systems behave: → State-driven UI updates → Persistent state using localStroge → Clear interaction feedback → Consistent visual behavior across components Live demo: https://lnkd.in/dt94TTW5 Code: https://lnkd.in/dDA8u28H The biggest shift for me was realizing: UI is not just HTML + CSS + JS - it is a system that reacts to state over time. I am continuing to build JavaScript projects with focus on engineering thinking, system design and user perception. #JavaScript #FrontentDevelopment #WebDevelopment #LearningInPublic
Rebuilding JavaScript with UI Systems in Mind
More Relevant Posts
-
Just built a dynamic product card using JavaScript DOM manipulation What I love about this project is how flexible it is — I can generate as many cards as I want dynamically, making it super useful for real-world applications like e-commerce or dashboards. Features: Fully dynamic card creation using DOM Clean and modern UI design Reusable component structure Easy to scale for multiple products This project helped me strengthen my understanding of how the DOM really works behind the scenes — not just static HTML, but building everything programmatically. 📂 GitHub Repository: https://lnkd.in/gwcZG2pf Would love to hear your thoughts or suggestions for improvement! #JavaScript #WebDevelopment #Frontend #DOM #Coding #Projects #Learning #100DaysOfCode
To view or add a comment, sign in
-
🚀Sharing my progress in mastering JavaScript(DOM) I built a small interactive component as part of a structured learning system — but focused on going beyond just making it work. 🔹What I worked on: ⊳ DOM manipulation and state handling ⊳ Designing clear interaction feedback (not just instant changes) ⊳ Improving UI perception using spacing, hierarchy and subtle motion 🔹Key focus: Instead of only changing text on click, I explored how users perceive state changes — adding timing and visual feedback to make interactions feel intentional. 🔹Live demo: https://lnkd.in/dt94TTW5 🔹Code: https://lnkd.in/dDA8u28H This is part of my journey building JavaScript projects from basic → advanced with a focus on engineering thinking, not just features. #JavaScript #FrontendDevelopment #WebDevelopment #LearningInPublic
To view or add a comment, sign in
-
-
I created this modern calculator UI using pure HTML, CSS, and JavaScript — without using any frameworks or libraries. ✨ Features: Basic arithmetic operations (+, −, ×, ÷) Clean dark UI design Smooth user interaction 🛠 Tech Stack: HTML CSS JavaScript (Vanilla JS) 💡 What I learned: DOM manipulation Event handling Building logic from scratch Improving UI/UX design skills This project helped me strengthen my core JavaScript fundamentals. 📸 (Check out the UI in the image below 👇) 💻 GitHub: https://lnkd.in/dWvi5iff I’d really appreciate your feedback! #JavaScript #FrontendDevelopment #WebDevelopment #Coding #Projects #Learning
To view or add a comment, sign in
-
-
JavaScript isn’t hard unclear logic is. One thing I’ve learned while building real frontend features is this: Most bugs don’t come from JavaScript itself… They come from assumptions we make while writing it. Here’s a simple rule that has saved me countless hours: Always validate your data before using it. Because in real projects, you’re not just writing code you’re handling unpredictable inputs, API delays, null values, and user behavior. A few examples that prevent 80% of silent failures: • Check if an array actually exists before mapping • Confirm API responses before rendering UI • Avoid chaining methods on undefined • Never trust user input without validation • Use optional chaining when the structure isn’t guaranteed Small checks. Big impact. Clean code isn’t about writing more it’s about writing responsibly. When your logic is predictable, your UI becomes reliable. And reliability is what users remember. #JavaScript #FrontendDevelopment #WebDevelopment #CleanCode #TechTips #UIUX #DeveloperLife
To view or add a comment, sign in
-
-
Built a Task Tracker using JavaScript. But the real learning wasn’t the UI, it was debugging real problems. This project helped me move beyond “writing code” to actually understanding how things break in real-world scenarios. Some challenges I faced: • Data not persisting correctly due to localStorage handling • Events not working on dynamically created elements • API-like behavior issues with async flow and DOM updates • UI breaking due to incorrect DOM manipulation • CSS bugs caused by specificity and layout issues Instead of patching things blindly, I debugged and fixed each issue step by step. Key things I learned: • Why JSON.parse is necessary when using localStorage • Difference between response-level errors vs data-level errors • Importance of event delegation for dynamic elements • How small DOM mistakes can break the entire UI • CSS pitfalls like flex overflow, specificity, and animation conflicts I also improved the user experience by: • Adding proper task states (pending/completed) • Ensuring smooth UI updates without reloads • Handling edge cases like empty inputs and invalid actions This project was less about building a “task app” and more about learning how to think like a developer. Project Repo: https://lnkd.in/gCgxHuWC Live Website: https://lnkd.in/gC3CJNx8 Would appreciate feedback! #javascript #webdevelopment #html #css #beginnerdev #100daysofcode #frontenddevelopment #vanillajs
To view or add a comment, sign in
-
🚀 JavaScript Project 3: Counter System Built a stste-driven counter with increment, decrement and reset actions —but this time, I focused on how engineers think, not just making it work. 🔑 Key ideas: • State is the single source of truth • UI updates are centralized ( updateUI ) • Event delegation for scalable interaction • Data-driven actions using data-* attributes • Clear UI feedback (disabled states, interaction response) 💡Biggest insight: Don't manipulate the UI directly — update state, then let the UI reflect it. 🔗 Live: https://lnkd.in/dTNy6A2M 💻 Code: https://lnkd.in/dp638D6h This is part of my journey building JavaScript systems step-by-step. More coming. #JavaScript #Frontend #WebDevelopment #LearningInPublic
To view or add a comment, sign in
-
-
I’ve been focusing on strengthening my JavaScript fundamentals and modern workflow recently. I just finished a small project called "Age Ai" to practice hand-written DOM manipulation while integrating Bootstrap 5 for a clean, responsive UI. Key features of this build: Pure JS Logic: Hand-wrote the conditional logic to handle user inputs and validation. UI/UX: Utilized Bootstrap to build a mobile-friendly, card-based interface. Version Control: Managed the project via Git and pushed it to GitHub. Deployment: Live now on GitHub Pages. Check out the live site and code here: 🔗 Live Demo: https://lnkd.in/ebtsf7WH 🔗 GitHub Repo: https://lnkd.in/erSVz7yP On to the next challenge! #WebDevelopment #JavaScript #CodingJourney #GitHub #Bootstrap #ProofOfWork #BuildingInPublic
To view or add a comment, sign in
-
-
Project 1: Private Click Counter & Theme Manager This project looks simple on the UI, but focuses on some important JavaScript fundamentals: Variable scope (global vs block scope) Closures for private state Execution context behavior Encapsulation without polluting global variables What I built: A page with multiple buttons (Like, Share, etc.), where each button maintains its own private counter. Also added a Dark Mode toggle using block scope to manage theme variables. The key idea was to ensure each button’s count stays isolated and cannot be modified from outside — similar to how real social media platforms manage interaction counts. Concepts practiced: • Closures for preserving state • Scope management • Encapsulation • Avoiding global variable pollution • Memory behavior in JavaScript RepoLink- vivek8817/javascript-adv-5project This is the first project in my JavaScript fundamentals → real projects series. Next projects will focus on async behavior, event loop, and advanced patterns. Building in public and learning by doing. #javascript #buildinpublic #webdevelopment #frontend #learning
To view or add a comment, sign in
-
🚀 Built a Realtime Search Filter in Vanilla JavaScript (No Frameworks) Most modern UIs feel fast because of instant feedback — so I implemented a real-time search system from scratch focusing on performance and clean logic. 🔍 Key Highlights: - Instant filtering as users type (no reloads) - Case-insensitive search handling - Graceful empty state (“No users found”) - Dynamic DOM rendering without libraries 🛠️ Tech Stack: HTML • CSS • JavaScript (Vanilla JS) 💡 What this demonstrates: - Strong fundamentals in DOM manipulation - Writing scalable, readable JavaScript - Handling real-world edge cases in UI logic - Thinking in terms of user experience, not just code 🔗 Live Demo: https://lnkd.in/gPtHDgud 📂 GitHub Repo: https://lnkd.in/ggvDP334 🙏 Learned core JavaScript concepts from Harsh Vandana Sharma and Sheryians Coding School — highly recommend their content for building strong fundamentals. Currently looking for opportunities to apply these skills in real-world projects and grow as a Frontend Developer. #frontenddeveloper #javascript #webdevelopment #hiring #developers #coding #buildinpublic
To view or add a comment, sign in
-
Hi! I’ve just published a new article in my 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗦𝗰𝗮𝗹𝗮𝗯𝗹𝗲 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀 series: 𝗣𝗮𝗿𝘁 𝟱 — 𝗥𝗲𝗻𝗱𝗲𝗿𝗶𝗻𝗴 𝗘𝗻𝗴𝗶𝗻𝗲𝘀: 𝗨𝗽𝗱𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗨𝗜 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁𝗹𝘆 This article explores a practical but very important question: When state changes, how does a framework decide what should actually change in the DOM? That is where rendering engines become essential. They are the part of the system responsible for deciding: • 𝘄𝗵𝗮𝘁 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝘂𝗽𝗱𝗮𝘁𝗲 • 𝘄𝗵𝗮𝘁 𝗰𝗮𝗻 𝘀𝘁𝗮𝘆 𝘂𝗻𝘁𝗼𝘂𝗰𝗵𝗲𝗱 • 𝗵𝗼𝘄 𝘁𝗼 𝗮𝘃𝗼𝗶𝗱 𝘂𝗻𝗻𝗲𝗰𝗲𝘀𝘀𝗮𝗿𝘆 𝗗𝗢𝗠 𝘄𝗼𝗿𝗸 • 𝗵𝗼𝘄 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝘀𝗰𝗮𝗹𝗲𝘀 𝗮𝘀 𝘁𝗵𝗲 𝗨𝗜 𝗴𝗿𝗼𝘄𝘀 This is also where frameworks start to diverge in a meaningful way. Some rely on rerendering and diffing. Others track dependencies more precisely. Others move more work into compilation. Different approach. Same core problem: how to keep the UI fast without turning the architecture into chaos. Once you understand the rendering engine, frameworks stop feeling like magic. You start seeing the trade-offs behind React, Vue, Lit, Solid, and others much more clearly. 👉 article link in the comments 𝗦𝗲𝗿𝗶𝗲𝘀 𝗿𝗼𝗮𝗱𝗺𝗮𝗽 • Part 1 — Building Scalable JavaScript Frameworks • Part 2 — Why JavaScript Frameworks Exist • Part 3 — Anatomy of a Modern JavaScript Framework • Part 4 — From Templates to DOM: Parsing and Compilation • 𝗣𝗮𝗿𝘁 𝟱 — 𝗥𝗲𝗻𝗱𝗲𝗿𝗶𝗻𝗴 𝗘𝗻𝗴𝗶𝗻𝗲𝘀: 𝗨𝗽𝗱𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗨𝗜 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁𝗹𝘆 (this one) • Part 6 — Reactive Systems and Data Flow • Part 7 — Designing Component Architectures • Part 8 — Routing and Application Structure • Part 9 — Performance Strategies for Large Applications • Part 10 — The Future of Frontend Frameworks #frontend #javascript #architecture #webdevelopment #innovation
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