Server-side rendering for each route

After preparing the Consumer class to change pages dynamically, we are going to incorporate a trivial system with Django for the management of routes and the rendering of each page without depending on Channels, so that crawlers can index the content. We’ll define three templates (home.html, login.html, and signup.html).

The content of app/app_template/templates/pages/home.html will be a few lines of HTML:

<section>
    <h1>Welcome to an example of browsing with WebSockets over the Wire.</h1>
    <p>You will be able to experience a simple structure. </p>
</section>

Then, on the second page, representing a login form, we will use a form object to list all the fields and then validate. This will be an argument that we will pass when rendering the template.

We write the following code in app/app_template/templates/pages/login.html:

<h1>Login<...