Consult about the structural design of vue-router,

this is my current routing structure.
question 1. At first, we thought of the bottom navigation as a first-level route, and all page jumps were under navigation, but registration and login wanted to fill the full screen, so it became a first-level route, and now there is a problem. That is, if I log in and store the information after vuex refresh, I store it locally through localStorage. But if you read it, you don"t know where to write it. Before the project, all the pages were under the second-level route, so it was written directly under the first-level route. How should I adjust my words like this?
there is an idea to change the registration page to second-level routing, and then skip to this page to hide the first-level routing navigation bar, and then the initialization of the data is written directly in the first-level routing. I don"t know if this is the right way of thinking. Or the initialization of the data is written in main.js?
clipboard.png

question 2. In addition to the project itself, we may also have some activity pages, which can be opened in app or shared in moments. How should I deal with this, because the logic of this page has nothing to do with the project itself, but it uses some resources of the project (Wechat login and so on). How should I design this?

Mar.12,2021

resolved. In fact, it is OK to follow the normal structure, and take out the other separate pages. Some comprehensive pages just hide the bottom navigation.

Menu