Let's take a look at what all we've done so far.

We have a project with an app, we have a global project wide view, our homepage,

that renders a template.

That template also uses a master layout template.

In our app we have two models and two migrations.

We have our models registered with Django's admin and

we have a view to see all of the courses that we've created.

We've come a long way.

Great job.

Now let's go see about showing the details of a single course.

So now we have two models and our admin is set up to edit both of them pretty nicely.

So let's see about adding a view for looking at a single course as a student.

Let's get over here and let's look at views.

We have a way to view all of the courses.

We get all the course names, right?

It'd be really cool.

Let's open this up, we're going to get another.

All right, so we have our admin, we have our view, we have our editor.

A lot of tabs for editing Django sometimes.

So, anyway, it'd be nice if we could just click on, like, a course name, like, Boop!

Click on Python Basics, and go see all the steps that are in that course.

Normally we call this kind of view,

when where you're drilling into just a single item, a detail view.

Because you're viewing the details of a particular item.

So we've got views.pi open, and let's create this new view.

We don't have to import anything.

Because we've already got the render.

We've already have our course model.

We've already got that stuff.

Okay.

We do need to catch the Primary Key which is the ID field by default though.

And, I know, we didn't define one.

You remember talking about that a while ago.

Django automatically creates one for us.

So we're cool.

We're good on that.

Django saved us time.

Thanks a lot Django.

So let's say course_detail, and it of course has to take the request.

And then we'll say that it's going to take a PK as well.

Now this tells Python that we're going to have two arguments to our view.

Django's going to automatically supply the request when it calls the view function,

and we will provide the PK through our URL.

But we'll worry about that in a minute,

the rest of our view is pretty straightforward.

We need to get the course with the given PK and

then render the template, so let's do that.

Course equals course.objects.get, where PK is equal to PK and

then we're going to return render the request object.

Courses slash course detail, that HTML Course is going to equal course.

Okay.

Now we didn't define a PK attribute either.

So where did PK come from?

Well, Django knows what field is our primary

key which is what PK stands for, Primary Key.

By default, it's the ID.

So, Django's like, oh, cool.

You want the primary key, you want the ID?

Great, here you go.

Let's just go to it.

So we'll deal with what happens if the course doesn't exist,

a little bit later on.

For now, though, let's just pretend that nobody's ever going to type in a bad URL.

[LAUGH] And that reminds me, we need a URL for this.

So let's go check out our URLs.

So we need to add a new line for the next URL.

And this URL is going to be really, really similar.

So we're going to do r and a quote and then we're going to catch a PK,

with a cap P there, and then we're going to do a slash d.

And there's going to be one or more of those, and that's going to end the line.

Now it's going to go to views.course_detail and that's it.

So what does this do?

This is a named group right here, and we're going to call this group PK,

that's the name of the group, is PK.

And it's going to be one or more digits that come in the URL.

That's going to go to course detail.

All right.

But, notice that we left off the chevron.

That's because our other URLs, where are they, right here.

We have this chevron here.

So the string starts with courses.

It can't start with the vk.

Just a little bit of logic there, I guess.

All right, [LAUGH] so last piece, we need a template.

So let's get our template.

So inside of our templates directory, inside of our courses directory,

we're going to create new file and we're going to call it course detail.html and

inside course detail.html we want to extend

our layout.html.

And then we want to be able to set some stuff.

So let's set block title is equal to whatever course we're looking at.

That course is title.

All right, and then we're going to have block content.

So inside block content,

we're going to do any little bit of extra HTML just to make our designers happy.

So, we're going to have an article tag, we're going to have an H2 tag,

with the course title.

And, then let's do the course description.

And then,

we should probably also print out the name for each step in our course.

Now we can do that by looping through a new.

Let's add a couple of things here first.

So we're going to do a section so

we can loop through a special new attribute.

That's called Stepset, and

Stepset is a query set.

So it's a bunch of records.

And, since it's a query set, we can query against it.

So we're going to use all to get all of them.

And notice we don't include the parenthesis when we're inside of

Django's templates.

So inside here we have each thing called step.

And we're going to print out something.

So let's do step.title and

then let's do step.description.

So, we have our article tag.

We have an H2, we have a description.

We have our section tag.

Inside here, we have an H3 and a description.

We end our section, we end our article.

Pretty simple HTML, yeah?

So let's see how it renders.

So, we can't get to it from here.

But let's go.

We know that Python Basics is number one.

And we forgot to close something.

We did. This should be endfor not endblock.

Endfor.

Refresh.

There we go.

Python Basics is the title of our course.

Learn the basics of Python.

And then What's the deal with strings is one of the steps, and

there's the description of that step.

Not too bad.

Django's ORM really helped us out there with step set attribute.

Sometimes though that ends up being a less than optimal addition to your queries.

I'll link to a couple of really handy RM functions named select related and

prefectrulated.

They're outside of the scope of this course, but they can come in really handy.

We'll definitely cover them in a later course, but check them out right now.