Today I explored " Templates " in Django and understood why they are important. In the MVT architecture, T stands for Template. When a user enters a URL: The request goes to the View The View interacts with the Model (if data is needed) Finally, the response is displayed using a Template (HTML page) Templates help us separate frontend (HTML) from backend logic, which makes the project more organized. Changes in settings.py for Templates To configure templates, we need to update the TEMPLATES section in settings.py and mention the templates directory path using BASE_DIR. i.e   'DIRS': [os.path.join(BASE_DIR,'templates')], After adding the correct path, Django can locate our HTML files.  Ways to Create Template Folder :- I understood there are two common approaches: 1:- Create a common templates folder in the main project and inside it create separate folders for each app.  2:-Create a templates folder inside every individual app. Both approaches work. It depends on how we want to structure the project. Today’s learning helped me understand how Django connects views and HTML pages properly. Slowly the architecture is making more sense. #Django #Python #WebDevelopment #BackendDevelopment #LearningJourney

🚀 Built a Weather Forecast Web App using Django! I recently worked on a small project where I built a Weather Forecast Web Application using Django and integrated it with the OpenWeatherMap API to fetch real-time weather data. This project helped me understand how to consume external APIs, process JSON responses, and dynamically render data in Django templates. 🔹 Key Features: 🌍 Search weather by city name ☁️ Displays temperature, weather description, and weather icons 📅 Shows the current date dynamically ⚡ API integration using Python requests library 🧠 Error handling for invalid city names or API issues 🖥️ Clean rendering of weather data using Django templates 💡 Tech Stack: Python Django HTML / CSS OpenWeatherMap API Requests Library Projects like this are a great way to practice backend development, API integration, and building real-world applications with Django. 🔗 GitHub Repository: 👉 https://lnkd.in/dSGn7QC4 I’m continuously exploring and building more projects to strengthen my Python & backend development skills. #Django #Python #WebDevelopment #BackendDevelopment #APIs #OpenWeatherMap #Coding #Programming #SoftwareDevelopment #BuildInPublic

Leveling up JavaScript skills with Data Mastery 💻✨ Today’s focus was on working with data in a smarter and cleaner way using: ✔ map, filter, reduce ✔ Object properties & this keyword ✔ Destructuring, spread & rest operators ✔ Shallow copy vs deep copy Learning how to write optimized and professional code instead of messy loops. One step closer to becoming a better developer 🚀 #learning #javascript #frontend #webdevelopment #programming #developerlife #logicbuilding #techskills

Exploring Flask for Full-Stack Development! After working with the MERN stack, I recently built my first full-stack project using Python (Flask) as the backend — a Grocery Management System. The goal of this project was to understand how Flask can be used to build APIs and connect a frontend with a database in a real application. 🔹 Tech Stack • Frontend: HTML, CSS, JavaScript • Backend: Python (Flask) • Database: SQLite 🔹 Features • Add, edit, and delete grocery items (CRUD operations) • REST API built with Flask • Dynamic product listing using JavaScript Fetch API • Low-stock alert for inventory monitoring • Simple dashboard-style UI This project helped me strengthen my understanding of API development, frontend–backend communication, and database integration using Flask. 📂 GitHub Repository: https://lnkd.in/gb8qspEg #Flask #Python #FullStackDevelopment #WebDevelopment #JavaScript #GitHub #LearningByBuilding

Day 58 of #90DaysOfCode Today I built a personal portfolio website using Flask, integrating backend logic with a fully designed frontend template. The application renders an HTML template and serves static assets such as CSS, images, and JavaScript, creating a complete web experience powered by a Python backend. How the application works • Uses Flask to handle routing and server logic • Renders HTML templates using render_template • Serves static files including CSS, images, and scripts • Displays a responsive and structured portfolio layout Key concepts explored • Template rendering using Flask and Jinja • Project structuring with templates and static folders • Integrating frontend UI with backend frameworks • Building complete web applications using Python This project helped me understand how backend frameworks can power full web applications beyond APIs. GitHub Repository https://lnkd.in/gnMWPqsr #Python #Flask #WebDevelopment #FullStack #SoftwareEngineering #90DaysOfCode

Today I learned about static files in Django. In a Django project, the static folder is used to store files like CSS, JavaScript, and images that help with the design and functionality of the website. To use static files, we need to configure them in the settings.py file: STATIC_URL = '/static/' STATICFILES_DIRS = [ os.path.join(BASE_DIR, 'static') ] After setting this up, we can easily load CSS, JS, and images in our templates. Slowly building my understanding of Django step by step. #Django #Python #WebDevelopment #Fullstackdeveloper

🚀 Breaking down the backend behind Codora In this short video I’m showing how the backend logic works using Django + Django REST Framework. The API handles: • Project listing • Database queries • Serialization of project data • API responses for the frontend This backend powers the Codora platform I recently launched. 🌐 Live platform: https://lnkd.in/gi77zPcR Tech stack used: Python Django Django REST Framework PostgreSQL React (Frontend) Still improving the platform and adding more features. Would love feedback from fellow developers 👇 #django #python #backenddevelopment #webdevelopment #buildinpublic

💠 Built a full-stack blog application called InkNest to strengthen full-stack development skills. InkNest allows users to create, update, and manage blog posts through a clean and secure system with authentication. Highlights - • Designed and developed a full-stack blog platform with user authentication and post management • Built the backend using Django, implementing efficient database operations with Django ORM • Implemented image optimization using lazy loading to enhance page performance • Debugged backend and API-level issues by analyzing error logs and request-response flows to improve stability during development Tech Stack: Python, Django, MySQL, HTML, CSS, Tailwind CSS, JavaScript, React.js, REST APIs. Building this helped me understand debugging APIs and optimizing database queries much better. #Python #Django #FullStackDevelopment #WebDevelopment #BackendDevelopment

Python is an easy choice. Deciding between Flask and Django is where it gets messy. Flask gives you a lightweight, flexible core you can shape however you want. Django arrives with batteries included: ORM, admin, auth, and a strong “this is how we build” philosophy. In this guide from AppMakers USA, Aaron Gordon compares Flask vs Django across project size, team structure, performance, ecosystem, and long-term maintenance—plus where each framework has worked well in real-world products. If you’re planning a new web app, SaaS product, or internal tool in Python, this will help you pick a framework that matches your reality instead of guessing. 👉 Read the full article here: https://lnkd.in/gRFrc3TU #Flask #Django #Python #WebDevelopment #AppMakersUSA

Day 7: Don’t Let Broken Images Kill Your App! 🖼️ Mastering Static vs. Media Files Today is Day 7 of my 30-Day Django Mastery journey, and I’m closing out Week 1 by tackling one of the most common stumbling blocks in web development: Managing Assets. In Django, there is a strict "separation of concerns" between files you provide (CSS/JS) and files your users provide (Profile pictures/Resumes). The Key Difference: 1. Static Files (STATIC): These are the assets that make your site look good—your CSS, JavaScript, and Brand Logos. These are part of your source code. 2. Media Files (MEDIA): These are user-generated. Think of a candidate's profile picture or an uploaded PDF. These are dynamic and live outside your code logic. The Pro Configuration: To handle these like an engineer, you need to tell Django exactly where these live in your settings.py. Python # settings.py # For your CSS/JS/Logos STATIC_URL = 'static/' STATICFILES_DIRS = [BASE_DIR / 'static'] # For User Uploads (e.g., Profile Pics) MEDIA_URL = 'media/' MEDIA_ROOT = BASE_DIR / 'media' The "Production" Secret: collectstatic During development, Django’s runserver handles these easily. But in production (AWS, DigitalOcean, etc.), Django is not meant to serve files—it's too slow. We use the python manage.py collectstatic command to gather every single static asset into one folder so a high-performance web server (like Nginx or WhiteNoise) can serve them to users instantly. The Result? A lightning-fast application where images never break, and your backend stays focused on what it does best: processing data. Question for the community: What’s your preferred way to store media files in production? Amazon S3, Cloudinary, or local storage? Let’s talk strategy below! 👇 #Django #Python #WebDevelopment #30DaysOfCode #BackendEngineering #WebPerformance #FullStackDeveloper #CodingLife