Simplify header about ngx-cbp-theme

[yogeshgadge]

@davezen1 wondering how much of the cbp-header is customizable ? I was under the impression that no customization was allowed in terms of what its on it since that directly affected the goal of unified look & feel as users switched between applications. I understand that in the interim we have some freedom as to how each of the items on header are implemented. For example can we provide a default functionality of opening a dialog and "please contact such and such via some@email" or just mailto: some@email.

[jscharett]

Weather all the pieces are required or not would be good to know. I thought I had heard that things like preferences and feedback were 'optional', but maybe I misunderstood. Regardless, it might be better to still abstract those into there own components that contain the services; similar to how they are now. Then, you simply pull them in and drop them into the header. This would provide a nice separation of concerns. Currently, the header has some hard dependencies on the services for these. It might prove better to decouple those.

[yogeshgadge]

Markup requirement for the end developer:-

<cbp-header>
    <cbp-feedback-link></cbp-feedback-link>
</cbp-header>

Additionally refactor necessary templates from cbp-header.component.html into appropriate components - mainly the feedback module.

[yogeshgadge]

We have use case for external facing applications which do not have other parts. We will need to open up all other parts of CBP Headers as per @jscharett to be configurable instead of the current opinionated.

<cbp-header>
    <cbp-apps-menu></cbp-apps-menu>
    <cbp-feedback-link></cbp-feedback-link>
    <cbp-user-menu></cbp-user-menu>
</cbp-header>

[walhow]

+100 on the original comment (jscharett commented on Sep 7, 2017)

[yogeshgadge]

PR #47 closes this.