Where This Connects in the Series<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\nCreating Views And URL For That The Secound Image You Can See How We create URL IN APP level Finanly In Third Image You Can See How we Configure URL Patten in Project Level <\/p>\n\n\n\nApp Level urls.py File<\/strong><\/p>\n\n\n\nProject Level urls,py File<\/strong><\/p>\n\n\n\nWhy HttpResponse Still Works Fine Here<\/h2>\n\n\n\n HttpResponse<\/code> accepts a string, and that string can be full HTML, not just plain text. Nothing stops you from writing an entire page’s markup inside it. It gets messy once a page grows large, which is exactly the problem templates solve later on \u2014 but for a single homepage with a handful of sections, it’s a perfectly reasonable way to build something real right now.<\/p>\n\n\n\nStep 1: Write the HTML as a Python String<\/h2>\n\n\n\n Open views.py<\/code> and update your home<\/code> view. Instead of a single sentence, build the full HTML structure inside a triple-quoted string:<\/p>\n\n\n\npython<\/p>\n\n\n\n
from django.http import HttpResponse\n\ndef home(request):\n html = \"\"\"\n <!DOCTYPE html>\n <html lang=\"en\">\n <head>\n <meta charset=\"UTF-8\">\n <title>My Django Site<\/title>\n <\/head>\n <body>\n <nav>\n <a href=\"\/\">Home<\/a>\n <a href=\"\/about\/\">About<\/a>\n <\/nav>\n\n <main>\n <h1>Welcome to my site<\/h1>\n <p>This homepage is built directly inside the view, using HttpResponse.<\/p>\n <\/main>\n\n <footer>\n <p>© 2026 My Django Site<\/p>\n <\/footer>\n <\/body>\n <\/html>\n \"\"\"\n return HttpResponse(html)<\/code><\/pre>\n\n\n\nRefresh your browser and you’ll see a proper page now \u2014 a navigation bar, a heading, a footer \u2014 all without touching a single template file. The triple quotes let the string span multiple lines, which makes writing full HTML like this manageable.<\/p>\n\n\n\nStep 2: Add Some Styling Without Static Files<\/h2>\n\n\n\n Since we’re not using Django’s static file system yet either, the simplest option at this stage is a <style><\/code> block written directly inside the HTML string:<\/p>\n\n\n\npython<\/p>\n\n\n\n
def home(request):\n html = \"\"\"\n <!DOCTYPE html>\n <html lang=\"en\">\n <head>\n <meta charset=\"UTF-8\">\n <title>My Django Site<\/title>\n <style>\n body {\n font-family: sans-serif;\n margin: 0;\n padding: 0;\n }\n nav {\n background-color: #222;\n padding: 1rem;\n }\n nav a {\n color: white;\n margin-right: 1rem;\n text-decoration: none;\n }\n <\/style>\n <\/head>\n <body>\n <nav>\n <a href=\"\/\">Home<\/a>\n <a href=\"\/about\/\">About<\/a>\n <\/nav>\n\n <main>\n <h1>Welcome to my site<\/h1>\n <p>This homepage is built directly inside the view, using HttpResponse.<\/p>\n <\/main>\n\n <footer>\n <p>© 2026 My Django Site<\/p>\n <\/footer>\n <\/body>\n <\/html>\n \"\"\"\n return HttpResponse(html)<\/code><\/pre>\n\n\n\nStep 3: Making the Navigation Links Actually Work<\/h2>\n\n\n\n Notice the nav links point to plain paths \u2014 \/<\/code> and \/about\/<\/code> \u2014 written directly as strings rather than using Django’s {% url %}<\/code> tag, since that belongs to the template system we haven’t covered yet. As long as those paths match what’s defined in your urls.py<\/code>, they’ll work exactly as expected. If you followed the earlier post on views and URLs, \/about\/<\/code> should already be wired up to an about<\/code> view.<\/p>\n\n\n\nWhere This Approach Starts to Break Down<\/h2>\n\n\n\n I want to be upfront about the downside here, because it’s the actual reason templates exist as a feature at all. Every view that returns a full HTML page like this ends up repeating the same <head><\/code>, the same navigation bar, the same footer. Add a third or fourth page, and you’re copying that same block of HTML into every single view function. Change one word in your navbar, and you’d have to update it in every view manually.<\/p>\n\n\n\nThat’s not a mistake at this stage \u2014 it’s just the natural limit of this method, and it’s exactly the problem Django’s template system is built to solve. We’ll get there. For now, this is a completely valid way to build a working homepage while sticking to what the course has actually covered so far.<\/p>\n\n\n\n
A Small Practical Tip<\/h2>\n\n\n\n Keep the HTML string readable by matching the indentation of your Python code, the way I did above. It’s tempting to squeeze everything onto fewer lines once the string gets long, but readable HTML inside a Python string saves you real time the next time you need to find and fix something inside it.<\/p>\n\n\n\n
Where This Connects in the Series<\/h2>\n\n\n\n This builds directly on the views and URLs you set up in the earlier tutorial \u2014 the about<\/code> link in the navbar above assumes that view already exists. If anything about routing feels unfamiliar here, that post is worth revisiting first. For more on what HttpResponse<\/code> can actually accept as a string, the official Django documentation on HttpResponse objects<\/a> is worth a look.<\/p>\n\n\n\nYour homepage now has real structure and styling behind it, built entirely through the tools you already know. Once you feel the repetition of copying that navbar into every new view, you’ll actually understand why templates exist \u2014 which is exactly where this series picks up next.<\/p>\n\n\n\n
Our Full Course<\/a><\/p>\n\n\n\n