I need help, about the best practices for portal and paths

[bewh1629]

1. I think my confusion lies in the design of the user portal. What are the best practices for the user portal?
2. User login journey:

• http://127.0.0.1:8000/#login # Login interface
• http://127.0.0.1:8000/apps # Users are required to select an app
• http://127.0.0.1:8000/insights/dashboards # Assume the user selects the Insights app
• http://127.0.0.1:8000/ # After login, this page is the “My Account” page

…
Some applications have paths to return to other apps, while in others, there are none.
Not all apps have a link back to the Desk.
How to deal with these things?

1. Visitor Browsing, sign up , sign in
2. user profile
3. select an app
4. from an app to another.
5. back to where? back to home ? back to userProfile ? back to desk ?

I know these are easy for experts, but as a beginner, I want to find the best practices from Frappe.

[peterg]

The routing is quite complicated, indeed. That’s largely a function of Frappe’s history and modularity. There are many different content-rendering mechanisms with significant overlap in functionality. Individual apps have the ability to generate their own roots and only handling logic, and their data can usually be accessed there or via the desk interface (/app). Applications like builder can set arbitrary content at any route as well.

It’s all very configurable, though doing the configuration isn’t trivial. Simple things like where your root path routes can be configured in Website Settings, and you can even design your own routing schema. If you’re not happy with how things currently work, it’s worth understanding how the routing and rendering functions work:

https://docs.frappe.io/framework/user/en/python-api/routing-and-rendering