More context on page titles (e.g. the ones on the browser tab)

[jonboiser]

Observed behavior

Some page titles are very generic. For example, at a url http://localhost:8000/coach/#/<classroomID>/lessons the title is "Lessons - Kolibri" regardless of the Classroom. A potential context-providing title would be "Lessons for Classroom A - Kolibri".

Expected behavior

Titles provide the right amount of context.

User-facing consequences

• Bookmarked pages may not have informative default titles
• Multiple tabs with same title are hard to distinguish

[radinamatic]

➕ 💯 for this!

• Learner reports for Classroom 2D - Kolibri:
  http://kolibri-beta.learningequality.org/coach/#/fa4cbfeda32c0c0fbf1832fc1ddd10c3/learners
• Learner reports for Abby L. in Classroom 2D - Kolibri (specific learner in a classroom):
  http://kolibri-beta.learningequality.org/coach/#/fa4cbfeda32c0c0fbf1832fc1ddd10c3/learners/eada3a8c2e6832383bd120fe126e630b

[khangmach]

this seems taken care of with the recent page title update, where we used breadcrumbs

[jonboiser]

Not on all the pages. I think the page names on the Facility page can still be improved.

[jonboiser]

I think whatever problem pages I saw in the Facility page back in Feb look okay now.

To hopefully shore up the other cases like the coach reports, I added these generic pure-formatting messages to common strings

  dashSeparatedPair: '{item1} - {item2}',
  dashSeparatedTriple: '{item1} - {item2} - {item3}',

so we can fix up the other titles if/when we find them.

[indirectlylit]

Sounds good. In coach common there are these strings:

  coachLabelWithOneName: 'Coach – {name}',
  coachLabelWithOneTwoNames: 'Coach – {name1} – {name2}',

could possibly consolidate