give buttons that do nothing the class "doesnothing" so that we can style/hide them.
Being able to hide navigation items that dont do anything, but are planned would help make things a bit easier when testing.
So the current workflow is that I go in and mockup a page, create buttons such as "edit page" or "add user"
these buttons dont do anything because there is no logic connected to them. I could in css create something like
.doesnothing{
text-decoration: underline;
}
Developers can quickly see what elements have lose ends and fix them.
Another example is when certain features are planned. These items can already be added to the main navigation so that we can sort out spacing before it becomes a problem. This also helps the Product Owner get a sense of the flow of the application, sort of like a clickable wireframe with dummy content, but then dummy content would be buttons.
Why are your developers adding buttons that do nothing? If they add them, and you want to hide them, it seems like a communication issue in your team...