Desk 2.0 - New Navigation

[joshreeder]

This topic has been moved to Frappe Forum, Please continue your participation and sharing your ideas there.
Here Is the Link: https://discuss.frappe.io/t/desk-2-0-getting-started/83

---

I’ve spent the last couple months rethinking navigation and layout and hope to get support because what I am proposing is not an app but I am willing to fund it to get it done if everyone wants this.

Would love to know who would support this… and what devs would want to help or be involved.

Simplify bootstrap layout
Convert desktop to part of the sidemenu
Simplify it to be modules
Add associated “Document” doctypes to submenu like module side menu
Separate out “user” navigation from “admin” navigation
Separate out help, videos, settings, and setup from module doctype lists and into appropriate areas
Make menus editable but start with permitted items to user or role
Allow for menu editability to be given to user by admin
I hope to start on this immediately, let me know what you think, I know this will be pretty low level stuff and that’s why I think we need to have it pulled in, but will take some work.

[almeidapaulopt]

Excelent work, I think this is a start of a very important and urgent enhancements of frappe.

I’ve already gave the idea that enhancements of UI and UX should be in the roadmap in

Frappe Framework Enhancements

Hi, Here my ideas: Doctype inheritance Group by (with multi level) on edit tables (example be able to group by a field in item table of a quotation) Add contrast in base theme Enhance user experience Multi doctype workflows (be able to design a process workflow for a company) I know, some of this are really challenging. I can detail better my ideas if you liked to.

Thank you

[joshreeder]

All of the above was done through editing the dom elements in inspector.

If I get help on editing frappe and erpnext to layout the items properly for bootstrap I can do the css.

Or I can do most of the work by just editing but some of the dynamic nav menus I will need help with implementing.

[joshreeder]

I guess let me know what you guys think is best. To post a job or get volunteers or post a bounty. I want to get started immediately.

[OneiricIT]

Love it - a much needed change and I think what you have proposed is a fantastic progression in the navigation. Will keep watching this space to see how I can contribute.

[tmatteson]

Excellent work Josh! This is a great compliment to the traditional desk view.

[woakes070048]

That looks great. I think that there is going to have to be a way to switch between views.

[jai_kejriwal]

Agree. Should be a toggle to switch as many people are already used to the existing views.

[ganas]

I specially Agree with you on containers width. On my MacBook retina ~1/3 of the screen (left and right sides) are empty non utilized spaces, and even the waste is bigger on my desktop big screen.

[ngu1k]

wow… that’s really really cool man… love it and looking forward to use it…

[joshreeder]

To all the devs who know frappe backwards and forwards, is that an easy ask? If we rearrange that many files is it an easy switch between the two?

I’ve been looking at how the modules config files are setup and it seems easy to rearrange but not sure about how to flip back and forth. If anyone had a clear path on how they would go about it, speak up and we can get started if the option is critical to most.

[joshreeder]

I added the container thing in my theme a while back. Huge plus. Love it.

[wale]

Hi @joshreeder

This looks very good!

I agree with folks that say there should be a toggle between this and the tradittional desktop. More importantly, I’d like to know what would be the default view for users when they login? There are a couple of threads on the forum where UI issues were discussed and the idea of having some sort of widgetized landing page with configurable dashboards seems to be fairly popular

With Navigation Icons being moved to the sidebar in this new design, I would think it should be a good opportunity to look into the issue of having configurable dashboards/widgets on the landing page (Desk)

Kind regards,

[JoEz]

@joshreeder Can u post mobile view screenshots?

[ganas]

Even if this achievable easily at the beginning, it will become a nightmare for developers to maintain consistency and updates for the two different UI. Also the platform will start having identity crisis with different interfaces lol.

So the right way of doing interface revamp is to slowly introduce changes between updates so the end use get familiar and not get shocked, and the end result is the users transition to new UI without much complaints.

[wale]

Makes sense!

[mulyadi-agtechsg]

Great work and initiative!

I just hope that the module access menu on the left is accessible so that I wont have to scroll down to click on a module

[tundebabzy]

Cc: @netchampfaris, @rmehta

[joshreeder]

I am working on this too. I’ll finish it up and share. For the first pass, see the menu builder. The module icon has the option to set the path for initial path for selecting a module and I will add a default module choice for the site home page but want to add dashboard builder that can be used for these and som defaults.

[joshreeder]

Not sure I follow. You mean the traditional modules view? My goal is that that is reorganized into a admin settings set of items and normal app use for everyday records is part of the new organization. This makes both things far less huge. Now that admin settings and setup (traditional modules view) is accessible if you have privledges in the top user nav dropdown in your user name. So for admins it’s even easier to access.

Also if you are an admin, and you are using the settings view from the top, and say the menu selection is developer/doctypes and you edit one and then accesss it from the sidebar to test and then go back to the doctype menu. The paths are still set since they are different menus now and they will default to were you last were thanks to how they are appended and hidden as you go through the system. A huge benefit and mentally satisfying to be able to build and then use. One from the top menu and one from the side. Separating these roles will help the developer see through the eyes of the user they are trying to serve well.