[MUSIC]

Users can view a list of all our page titles but

they can't view the content of single pages yet.

For a post resource they can click a link on the list of all posts to view

an individual post.

Let's set up links to view single pages as well.

We wanna turn these page titles into links, so we can click on them and

view the associated page.

Remember how we showed you that all saved rails model objects have an ID

attribute that's used to look them up in the database.

Creating links is one major reason that ID attribute exists.

We're going to use that ID in our links to tell rails which model objects to load.

We can embed dynamic HTML links into the output with output embedding tags.

Within rails views, a helper method named Link to is available.

It returns the necessary HTML string for creating a link.

Link to his first argument should be the link text that you wanna displayed.

And the second argument should be the path that you want the browser to request.

If we save this we'll have web links in our output, let's say link text and

that point to the nonexistent path of slash link, slash path.

We can see the HTML output in our browser's developer tools.

There's the link text within the anchor tag and

there's the path of the link references.

Now let's update this call to link two and make it do something useful.

We'll change the link text argument to be the page object's title.

And we'll change the link path to the double quoted string slash pages slash

page ID.

And there's that idea attribute.

We interpreted into the path string, so

that the post with an idea of one creates a link to slash pages slash one.

A post with an idea of three creates a link to slash pages slash three and so on.

If we save this and reload our browser will see our updated links.

But we can't actually click on them yet If we're trying will see an error, no route

matches [GET] /pages/4, or whatever the idea of the link we tried to click on is.

We need to go into the configs/route.rb file to fix this.

We've set up a route for slash pages by itself but

there's no route for slash pages followed by an ID.

Let's set one up.

Since the browser is requesting to load a page.

It's going to be an HTTP get request.

So, we'll set up another get route.

We want it to match requests for paths that start with slash pages slash, so

we'll add that string next.

But following slash pages slash we're expecting a string representing the ID

of the page object we want to load, so will type colon ID.

The colon followed by a name is a URL parameter.

A URL parameter captures part of the request path and

makes it available within the controller in the params object.

You may remember that we used params before to access form submission contents.

So, if we type colon ID here,

it will be available later in the params object under the ID key.

We can name the parameter whatever we want.

But by convention, the name ID is used for model record IDs.

On the route for the list of all pages we specify which control or and

which action should handle the requests.

We need to do the same for the route for individual pages will add a second

argument to get with a key of two and a value of pages pound sign show that

will direct requests of the show action on the pages controller.

Let's save our work and now if we click on these pages for link of our browser.

We'll be routed to the show action on page's controller,

of course we haven't created that method yet but will take care of that in a bit.