Angular best practises for layouts

Vote count:

0

I have an admin dashboard application called dashboard.html initiated with its own angular module. This application has an consistent layout with n header bar at the top, left bar navigation etc. When the route changes only the content container gets updated and the rest of the layout stays unaffected.

My problem is that the login page, with a completely different layout, without the header bars and navigation.

Currently I'm solving this issue by creating an login.html file with its own module, when the user successfully login, I redirect them to the dashboard.html app.

Is this a general used approach or is there a clean way of doing it in a single application, by just changing the routes and not redirecting to different apps?

asked 26 secs ago

dieheld

103

Angular best practises for layouts