Questions Management – Frontend – Split SB Admin 2 template using Module, Component of Angular

Our Questions Management application will have many pages, each page will have some common sections for all pages and specific sections for this page. Therefore, splitting our template using Component and Module in Angular is essential. In this tutorial, I will guide you all how we split our SB Admin 2 template.

First, look at the current Question Management interface:

Questions Management - Frontend - Split SB Admin 2 template using Module, Component of Angular

You will see the left navigation menu and the navigation section at the top of the page are common to all pages of our application. Only the middle part of the “Dashboard” will change as we move between different pages.

If you look at the contents of the app.component.html file, you will see inside the root tag with the id wrapper, we have two sections for navigation and page-wrapper, as follows:

Questions Management - Frontend - Split SB Admin 2 template using Module, Component of Angular

The navigation section is the left menu and the top navigation, while the page-wrapper is the Dashboard.

Now I will create two directories dashboard and navigation in the corresponding src/app directory for each of the above:

Questions Management - Frontend - Split SB Admin 2 template using Module, Component of Angular



Talking first about the dashboard, the content of the Dashboard page will contain a lot of different information. Each information will be a component in the Angular so I will create a DashboardModule class to compile these sections. I will now create 3 files: dashboard.module.ts, dashboard.component.ts, dashboard.component.html.

Questions Management - Frontend - Split SB Admin 2 template using Module, Component of Angular

The contents of the dashboard.component.html file will be copied from the page-wrapper section of the app.component.html file. Content is a lot so I will not copy this here, but one thing is that we will replace the contents of the page-wrapper in the file app.component.html to “<qm-body> </ qm-body>”.

Now the contents of the DashboardModule class and the DashboardComponent class are as follows:

DashboardComponent:

DashboardModule:



Next, we will talk about navigation.

As I said, this navigation consists of two navigation menus on the left and navigation at the top. Look at the HTML content of the app.component.html file at the moment, you will see this clearly:

Questions Management - Frontend - Split SB Admin 2 template using Module, Component of Angular

The top navigation is the <ul> tag in the above image, while the left menu is the <div> tag with the navigation role.

To split the template for this navigation, I will create a module is NavigationModule with two components is NavbarTopComponent and SidebarComponent as follows:

Questions Management - Frontend - Split SB Admin 2 template using Module, Component of Angular

As you can see, we created two directories sidebar and navbartop in the src/app/ navigation directory.

The sidebar will define the SidebarComponent component to define the content of the left menu. The contents of the sidebar.component.html file will be copied from the <div> tag with the navigation role in the app.component.html file. The content of the SidebarComponent class will be as follows:

The navbartop directory defines the NavbarTopComponent component to define the content of the navigation at the top. The contents of the file navbartop.component.html will be copied from the <ul> tag in the app.component.html file. The content of the NavbarTopComponent class is as follows:

In these two component classes, you see that the selector in the @Component decorator is defined with the values nav-sidebar and nav-top, which are the HTML tags defined in the navigation.component.html file.

The content of the navigation.component.html file is copied from the navigation section of the app.component.html file with the left menu replaced by the <nav-sidebar> tag and the navigation section at the top is replaced by the < nav-top>. The contents of the file navigation.component.html are now as follows:

Now, the contents of the NavigationComponent and NavigationModule classes are defined as follows:

NavigationModule:

NavigationComponent:

In the selector section of NavigationComponent above, as you see, I have defined the value “qm-nav”. This is an HTML tag that has been replaced by the content of the navigation section in app.component.html.

And because of this, the content of the app.component.html file is now as simple as this:

OK, here we have basically finished splitting the SB Admin 2 template into small parts. At this point, you run the application, the results are still similar.

Questions Management – Frontend – Split SB Admin 2 template using Module, Component of Angular
Đánh giá bài viết
Chia sẽ bài viết này ...Share on Facebook
Facebook
2Tweet about this on Twitter
Twitter
Share on LinkedIn
Linkedin

Add Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.