Tree node context menu design, what would you expect? - user-interface

My team is designing a set of applications, some of them are using trees to display data. The levels of the trees are 2-4 at the moment, might grow later depending on our domain model.
Lets say that we have 3 levels:
Book
Page
Word
My question is this: What would you, as a user, expect to see in a context menu on the nodes on the different levels?
Example Book context menu:
New Page
New Book
Edit Book
Delete Book
Example Page context menu:
New Word
Edit Page
Delete Page
Example Word context menu:
Edit Word
Delete Word
(I don't care about separators for now)
The thought about this example setup is that you edit the node you clicked on.
Inserting a new Word edits the Page you clicked on.
Only exception is the root node, where you can actually create a new root node.
All input is welcome an appreciated.
Edit:
I'm thinking, is this the right setup of the CRUD operations, or would you expect to see a Add Page in the context menu for a Page node?

Listing a few below which come to my mind -
Refresh
Move
Rename
There could be more based upon what operations can be done on the items as per the functionality in your application. Best thing is to ask the customer\business ambassadors and
build only what is needed.
Edit:
IMO, Add Page should be available only on the Book element.

Related

Using one Wix Dynamic Page for various entries in the site menu

I am doing a site in Wix.com so my wife can maintain it without my input. The draft site is live at:
http://www.wingspan.info
IMPORTANT: The wife is not a techie.
Essentially, the site displays our art work in galleries of paintings, etc, filtered by artist.
I have coded one page, then duplicated that to create the galleries and filter the WixDataQuery according to Andrew or Helen and Categories like Painting, Drawing, Sculpture, iPad Art, etc. Also, where we have exhibited (Exhibitions menu) some of our paintings.
All working, but any change to design and I have to change 15 pages...
So, it now strikes me that it would be more efficient to design one dynamic page, and set up the menu to display the different categories, as it is set up in the live site:
However, I can't find any documentation that shows how to use just the one dynamic page rather than my coded page duplicated to produce 12 different pages. Not clever...
Any suggestions / tutorials where I can find how to do this?
Thanks!
Basically, you want to add the Content Manager to your site if you haven't already, and then set up a collection with all of your data in it. One row per eventual "page" that you want.
Next, you can take the page you already designed and convert it to a dynamic page. It will then have a dataset on the page which you need to connect to various elements on the page through their connect buttons.
Finally, you'll need to edit your menu to point to the various instances of your dynamic page instead of the regular pages you have them pointing to now.
You can read all about how dynamic pages work here and here.

Menu not branching out in Kentico 7

There are two different websites with drop-down menus, but only one is having the appropriate "branch-out" affect.
Picture 1 is the one not branching and picture 2 is doing what I want:
No Branch
Branch
The menu that is correct is using a tree menu widget and the other is not, only a breadcrumbs widget. As you can see I added a "Test Page" under Government, but it is simply at the bottom of the menu. If it's just a matter of inserting a Tree Menu widget to get the affect I want, I'll do that, but I wanted to see if there was another solution first. Thanks.
Looks like it could be an issue with the webpart used for the menu. So the one site showing correctly may have the levels set to the necessary depth whereas the other site may not. This doesn't seem to be the case though as the webpart is picking up the "Test Page" but not the "Tax Matters" page.
It could also be an issue with the overall design of the site's menu. Maybe the site's menu wasn't designed with 3 levels of depth on it. To check this you can go to the webparts transformation property and see if there are multiple levels setup to display that 2nd and 3rd level nested within one another.
Not knowing the configuration of your webpart or the transformation makes it a bit harder to actually troubleshoot.

Web App UX row selection best practice

Which is a better User Experience / Design decision for opening a table row (in a business website)? To place an "Open" button like this:
Or, to allow the row to be opened by clicking anywhere on it?
Your question assumes that people understand that there is more information to be gained by "expanding" these rows in this table. As this is designed right now, there are zero hints for a user that they are capable of viewing more information inside the same view that they are using.
Option 1: Open button
Let's assume (dangerously) that people are knowledgable that they can use this table to view more info about a line item in this table. The button itself is separated from the content it is referring to, breaking Fitt's Law. Also, the label is "open", which most users would interpret as taking them to another page, or opening a new context. "View More" or "Expand" would be a better label.
Option 2: Click anywhere
This is slightly better than the button, as it clearly relates the action to the content. However, it still doesn't solve the problem of exposing the functionality to the user.
I would recommend a combination of both of these approaches, making sure you are solving for Fitt's Law as well as exposing a label that will tell the users what functionality is present in these table rows, and how to access them.

Dynamic menu table in inner pages

I want to add dynamic menu table in inner pages based upon the tabs on the home page.
how to do that in joomla,please help me.
It sounds like you are trying to create a split menu where the link you click at the top determines the menu that shows up in a column/below. This is the native behavior for Joomla menus simply by setting the start and end levels in the menu module. Here is a good tutorial -
http://www.theartofjoomla.com/magazine/article/27-more-menu-tricks-the-split-menu-technique.html
Beware:: The split level menu feature in Joomla only works when the split equals TWO levels. If you want to build your site with a single master menu that spans 3 or more levels, this does not work. It looks like the internals of Joomla do not know how to track the parent properly (not really sure) when the menus are generated (probably an overstatement). Level 1:1 works, Level 2:2 works but then when you try to specify a menu starting at level 3, it breaks. In my case, I hacked the menu to check the pathways (breadcrumbs) list and derive what I wanted from it so I could determine the real parent of the items at level 3 (or other). Then I could get the items to generate proper. This was a disappointment in Joomla (v1.7). And then on top of this, you would then have to hack further to ensure that each menu item instance starting at 1 is highlighted proper. Perhaps the menus should be more closely coupled to the breadcrumbs pathway list.

Interactive elements of a web page

I was wondering if we have to consider interactive elements of a web page which are basically changing a section of a web page as a new level when making a site map. For example, I have a web page "x" with edit, new, delete function button. Clicking on these buttons changes only a specific part of the page which is associated which is a constant area in itself. The parts of the web pages which don't change are the top navigation, footer etc. While thinking of a site map I wasn't sure if clicking on features like edit would be considered a new level since the web page is the same.
No, interactive page elements would not be considered part of a site map.
The page they reside on would be placed on the site map, but that is it.
A site map is meant to record the hierarchy and individual pages of a site... the things a person can navigate to.
Interactive elements would not fit this unless there are several different bits on one page and those bits can be reached by anchors.

Resources