Building Pages
In this chapter, you will build the first few pages of your Ember app and set up links between them. By the end of this chapter, you should have two new pages – an about page and a contact page. These pages will be linked to from your landing page:
While building these pages, you will learn about:
- Defining routes
- Using route templates
- Customizing URLs
- Linking pages with the
<LinkTo>component - Passing arguments and attributes to components
Defining Routes
With our first page down, let's add another one!
This time, we would like the page to be served on the /about URL. In order to do this, we will need to tell Ember about our plan to add a page at that location. Otherwise, Ember will think we have visited an invalid URL!
The place to manage what pages are available is the router. Go ahead and open app/router.js and make the following change:
import EmberRouter from '@ember/routing/router';
import config from 'super-rentals/config/environment';
export default class Router extends EmberRouter {
location = config.locationType;
rootURL = config.rootURL;
}
Router.map(function () {});
Router.map(function () {
this.route('about');
});
This adds a route named "about", which is served at the /about URL by default.
Using Route Templates
With that in place, we can create a new app/templates/about.hbs template with the following content:
To see this in action, navigate to http://localhost:4200/about.
With that, our second page is done!
Defining Routes with Custom Paths
We're on a roll! While we're at it, let's add our third page. This time, things are a little bit different. Everyone at the company calls this the "contact" page. However, the old website we are replacing already has a similar page, which is served at the legacy URL /getting-in-touch.
We want to keep the existing URLs for the new website, but we don't want to have to type getting-in-touch all over the new codebase! Fortunately, we can have the best of both worlds:
import EmberRouter from '@ember/routing/router';
import config from 'super-rentals/config/environment';
export default class Router extends EmberRouter {
location = config.locationType;
rootURL = config.rootURL;
}
Router.map(function () {
this.route('about');
this.route('contact', { path: '/getting-in-touch' });
});
Here, we added the contact route, but explicitly specified a path for the route. This allows us to keep the legacy URL, but use the new, shorter name for the route, as well as the template filename.
Speaking of the template, let's create that as well. We'll add a app/templates/contact.hbs file:
Ember comes with strong conventions and sensible defaults—if we were starting from scratch, we wouldn't mind the default /contact URL. However, if the defaults don't work for us, it is no problem at all to customize Ember for our needs!
Once you have added the route and the template above, we should have the new page available to us at http://localhost:4200/getting-in-touch.
Linking Pages with the <LinkTo> Component
We just put so much effort into making these pages, we need to make sure people can find them! The way we do that on the web is by using hyperlinks, or links for short.
Since Ember offers great support for URLs out-of-the-box, we could just link our pages together using the <a> tag with the appropriate href. However, clicking on those links would require the browser to make a full-page refresh, which means that it would have to make a trip back to the server to fetch the page, and then load everything from scratch again.
With Ember, we can do better than that! Instead of the plain-old <a> tag, Ember provides an alternative called <LinkTo>. For example, here is how you would use it on the pages we just created:
There is quite a bit going on here, so let's break it down.
<LinkTo> is an example of a component in Ember—you can tell them apart from regular HTML tags because they start with an uppercase letter. Along with regular HTML tags, components are a key building block that we can use to build up an app's user interface.
We have a lot more to say about components later, but for now, you can think of them as a way to provide custom tags to supplement the built-in ones that came with the browser.
The @route=... part is how we pass arguments into the component. Here, we use this argument to specify which route we want to link to. (Note that this should be the name of the route, not the path, which is why we specified "about" instead of "/about", and "contact" instead of "/getting-in-touch".)
In addition to arguments, components can also take the usual HTML attributes as well. In our example, we added a "button" class for styling purposes, but we could also specify other attributes as we see fit, such as the ARIA role attribute. These are passed without the @ symbol (class=... as opposed to @class=...), so that Ember will know they are just regular HTML attributes.
Under the hood, the <LinkTo> component generates a regular <a> tag for us with the appropriate href for the specific route. This <a> tag works just fine with screen readers, as well as allowing our users to bookmark the link or open it in a new tab.
However, when clicking on one of these special links, Ember will intercept the click, render the content for the new page, and update the URL—all performed locally without having to wait for the server, thus avoiding a full page refresh.
We will learn more about how all of this works soon. In the meantime, go ahead and click on the link in the browser. Did you notice how snappy that was?
Congratulations, you are well on your way to becoming a master page-crafter!