First, we need to create a directory to store our static files in. Go ahead and create a directory called `static` inside your `djangogirls` directory.

Open up the `mysite/settings.py` file, scroll to the bottom of it and add the following lines:

Let's create a CSS file now, to add your own style to your web-page. Create a new directory called `css` inside your `static` directory. Then create a new file called `blog.css` inside this `css` directory. Ready?

static

Time to write some CSS! Open up the `static/css/blog.css` file in your code editor.

`h1 a` is a CSS Selector. Any `a` element inside of an `h1` element (i.e. when we have in code something like: `<h1><a href="">link</a></h1>`) is the tag we're applying our styles to, and we're telling it to change its color to `#FCA205`, which is orange. Of course, you can put your own color here!

<a href="http://en.wikipedia.org/wiki/Django" class="external_link" id="link_to_wiki_page">

<link rel="stylesheet" href="{% static 'css/blog.css' %}">

Your file should now look like this:

</body>

</html>


Nice work! Maybe we would also like to give our website a little air and increase the margin on the left side? Let's try this!

<h1><a href="/">Django Girls Blog</a></h1>

</div>

<div class="post">

<p>published: {{ post.published_date }}</p>

color: #000000;

}

{% for post in posts %}

<div class="post">

As you can see, we import (include) the Post model defined in the previous chapter. To make our model visible on the admin page, we need to register the model with `admin.site.register(Post)`.

http://127.0.0.1:8000/admin/

Go to Posts and experiment a little bit with it. Add five or six blog posts. Don't worry about the content - you can simply copy-paste some text from this tutorial as your posts' content to save time :).


(myvenv) ~/djangogirls$ python manage.py startapp blog

You will notice that a new `blog` directory is created and it contains a number of files now. Our directories and files in our project should look like this:

After creating an application we also need to tell Django that it should use it. We do that in the file `mysite/settings.py`. We need to find `INSTALLED_APPS` and add a line `blog` just above `)`. We should also add the `mysite` application (which was created for us when we started a new project in the last chapter). So the final product should look like this:

Let's open `blog/models.py`, remove everything from it and write code like this:

This is exactly what *views* are supposed to do: connect models and templates. In our `post_list` *view* we will need to take models we want to display and pass them to the template. So basically in a *view* we decide what (model) will be displayed in a template.

We need to open our `blog/views.py`. So far `post_list` *view* looks like this:

def post_list(request):

return render(request, 'blog/post_list.html', {})

from django.shortcuts import render

from .models import Post

Dot after `from` means *current directory* or *current application*. Since `views.py` and `models.py` are in the same directory we can simply use `.` and the name of the file (without `.py`). Then we import the name of the model (`Post`).

Post.objects.all()

return render(request, 'blog/post_list.html', {})

Please note that we create a *variable* for our queryset: `posts`. Treat this as the name of our queryset. From now on we can refer to it by this name.

In the `render` function we already have parameter with `request` (so everything we receive from the user via the Internet) and a template file `'blog/post_list.html'`. The last parameter, which looks like this: `{}` is a place in which we can add some things for the template to use. We need to give them names (we will stick to `'posts'` right now :)). It should look like this: `{'posts': posts}`. Please note that the part before `:` is wrapped with quotes `''`.

The names of some files and directories are very important for Django. You should not rename the files that we are about to create. Moving them to a different place is also not a good idea. Django needs to maintain a certain structure in order to be able to find important things.

Run on Windows:

`django-admin.py` is a script that will create the directories and files for you. You should now have a directory structure which looks like this:

└───mysite

settings.py

urls.py

Let's make some changes in `mysite/settings.py`. Open the file using the code editor you installed earlier.

You should find lines that contain `USE_TZ` and `TIME_ZONE` and modify them to look like this, substituting `Europe/Berlin` with your relevant time zone:

To print a variable in Django template, we use double curly brackets with the variable's name inside, like this:

[<Post: My second post>, <Post: My first post>]

{% for post in posts %}

{{ post }}


<div>

<h1><a href="/">Django Girls Blog</a></h1>

Lines that start with `#` are comments - it means that those lines won't be executed by Python. Pretty handy, right?

url(r'^admin/', include(admin.site.urls)),

We bet you use the Internet every day. But do you actually know what happens when you type an address like http://djangogirls.org into your browser and press 'Enter'?

As with every file, we need to store HTML files somewhere on a hard disk. For the Internet, we use special, powerful computers called *servers*. They don't have

a screen, mouse or a keyboard, because their main purpose is to store data and serve it. That's why they're called *servers* -- because they *serve* you data.

We drew you a picture! It looks like this: