Any thoughts? if only the editors would embrace tabs.. though also maybe have improved info content app.. https://cdn.discordapp.com/attachments/882984798719729704/1494034863748288713/Jumpmenu.mp4?ex=69e123e5&is=69dfd265&hm=8fe4ba7c6682a3bd91534cb1ed6319db43b5333f18fe35fedef1dadb92d23c46&

Neat little utility, I would perhaps suggest changing the icon. As to me at first quick glance before you clicked it. Why is there drag & drop icons on the groups for reordering in the content node? Perhaps a ship style anchor?

I think a little of.... but we are used to it from v13.. and we use browser find.. tabs I can't find where the property is and have to visit each one.. I think some of this is just the client also digging their heels in as don't like v17 over v13.... new trees, collection views not quite the same... it's slower (subjectively nothing concrete)... 🤷‍♂️ thought about collapsible groups, (as think there was a package when tabs came) but thought that would be much harder to implement

lol I saw the previous messages and thought: surely Mike knows that TABS already exist 🙈

OK well then a neat package for sure to make a stubborn client happy. But I am still wondering how many properties do they have if they need to CTRL+F typically to find a property. I imagine thats a looooong scrolll bar

it is 🙂 .. ps can still have groups in tabs.. and on smaller(tiny) screens (I know v17 back-office not officially supported on mobiles)

Yeh neat - if they are editing from mobile alot - perhaps build them a custom UI that uses the backoffice MGMT API perhaps as an idea to jam on?

thought: maybe you can give them a search box at the top so they don't need to CTRL+F? just above the first content block I was about to suggest to put links to each block next to the search box but since they refuse tabs, I guess that's too close to what they don't want 😅