I am new to angular 4. What I'm trying to achieve is to set different layout headers and footers for different pages in my app. I have three different cases:
- Login, register page (no header, no footer)
routes: ['login','register']
- Marketing site page (this is the root path and it has a header and footer, mostly these sections come before login)
routes : ['','about','contact']
- App logged in pages (I have a different header and footer in this section for all the app pages but this header and footer is different from the marketing site header and footer)
routes : ['dashboard','profile']
I run the app temporarily by adding a header and footer to my router component html.
Please advise me a better approach.
This is my code:
app\app.routing.ts
const appRoutes: Routes = [
{ path: '', component: HomeComponent},
{ path: 'about', component: AboutComponent},
{ path: 'contact', component: ContactComponent},
{ path: 'login', component: LoginComponent },
{ path: 'register', component: RegisterComponent },
{ path: 'dashboard', component: DashboardComponent },
{ path: 'profile', component: ProfileComponent },
// otherwise redirect to home
{ path: '**', redirectTo: '' }
];
export const routing = RouterModule.forRoot(appRoutes);
app.component.html
<router-outlet></router-outlet>
app/home/home.component.html
<site-header></site-header>
<div class="container">
<p>Here goes my home html</p>
</div>
<site-footer></site-footer>
app/about/about.component.html
<site-header></site-header>
<div class="container">
<p>Here goes my about html</p>
</div>
<site-footer></site-footer>
app/login/login.component.html
<div class="login-container">
<p>Here goes my login html</p>
</div>
app/dashboard/dashboard.component.html
<app-header></app-header>
<div class="container">
<p>Here goes my dashboard html</p>
</div>
<app-footer></app-footer>
I saw this question on stack-overflow but i didn't get a clear picture from that answer
There are cases where the layout and shared elements don't really match the routing structure, or some elements have to be hidden/shown depending on a per-route basis. For such cases I can think of the following strategies (let's take an example of
app-header-main
component - but it will apply to any shared page element obviously):Inputs & css classes
You can provide inputs or css classes to control the inner appearance of your shared elements, such as:
<app-header-main [showUserTools]="false"></app-header-main>
or
<app-header-main class="no-user-tools"></app-header-main>
and then use :host(.no-user-tools) to show/hide what needs to beor
at a route level (child or not):
And access it through
ActivatedRoute
like so:this.route.data.header.showUserTools
TemplateRef input
Inside
app-header-main
component:@Input() rightSide: TemplateRef<any>;
Input of type
TemplateRef<any>
where you could feed anng-template
element directlyNamed slot transclusion
You can author the app-header-main so that it uses named slot transclusion
Inside of app-header-main template:
<ng-content select="[rightSide]"><ng-content>
Usage:
You can solve your problem using child routes.
See working demo at https://angular-multi-layout-example.stackblitz.io/ or edit at https://stackblitz.com/edit/angular-multi-layout-example
Set your route like below
Recommended reference: http://www.tech-coder.com/2017/01/multiple-master-pages-in-angular2-and.html
you can use child e.g.
MainComponent and AdminComponent like
the post talk about separate in diferent files the routes