rarwe.tar.gz

Ember

Ember-copy

ember2

embercss

rarwe

Ember-copy-5yvdqv

Ember-copy-5yvdqv-copy

Ember-Acceptest

Ember-Acceptest-copy

Ember-unitest

rarwe-copy

Ember-Acceptest-challenge

Ember-helper-challenge

In this course, you begin with an introduction to Ember.js, a JavaScript framework for building client-side applications.

After that, the course guides you through the steps of building a real application so that you can see how the concepts are applied in practice. You'll learn about the building blocks of Ember one by one, in a way that crushes the allegedly steep learning curve of the framework.

The application will get shinier (and/or more robust) with each chapter. By the end, we will have a decent app, and you'll have a great new skill you can add to your resume.

Developing Robust Ember.js Applications

## Default page titles
Whenever we generate a route, Ember inserts a `{{page-title}}` into the templates based on the name of the route. In some cases, this works out quite well, like in the case of the `bands` route we generated in the [previous chapter](https://www.educative.io/collection/page/10370001/4603037207756800/6673520816291840). However, in other instances, we have to manually adjust those default titles.

If you go to any songs page, you'll find that the page title for them is `Band | Bands | Rock & Roll with Octane`. That's because nested routes also imply inheriting the page title of the parent route and then prepending to it. Since we have `{{page-title "Rock & Roll with Octane"}}` in our application template and the application route is the parent of all routes, it will be the end of all page titles.

Next, the `bands` route adds its page title, `Bands` and the `bands.band` route adds `Band`, giving us the full page title of `Band | Bands | Rock & Roll with Octane`, which just looks funny.

To improve our page titles, let's first remove the one in `bands.band`:

# Default page titles
Whenever we generate a route, Ember inserts a `{{page-title}}` into the templates based on the name of the route. In some cases, this works out quite well, like in the case of the `bands` route we generated in the [previous chapter](https://www.educative.io/collection/page/10370001/4603037207756800/6673520816291840). However, in other instances, we have to manually adjust those default titles.

If you go to any songs page, you'll find that the page title for them is `Band | Bands | Rock & Roll with Octane`. That's because nested routes also imply inheriting the page title of the parent route and then prepending to it. Since we have `{{page-title "Rock & Roll with Octane"}}` in our application template and the application route is the parent of all routes, it will be the end of all page titles.

Next, the `bands` route adds its page title, `Bands` and the `bands.band` route adds `Band`, giving us the full page title of `Band | Bands | Rock & Roll with Octane`, which just looks funny.

To improve our page titles, let's first remove the one in `bands.band`:

Let’s discuss how to change titles of different pages of an Ember application.

Improving Page Titles

Course Overview

Getting Started with Ember

Templates and Data Bindings

Routing

Nested Routes

Components

Controllers

Building a Catalog

Talking to a Backend

Advanced Routing

Testing

Query Params

Loading and Error Substates

Helpers

Conclusion

Appendix

Improving Page Titles

Default page titles