I think it could be usefull if I could hide the pages section.
The clients normally just needs the blocks and you can break the layout if don’t know what you are doing.
I know I can do that inside the code, but what about a little switch inside the config?
In version 4.9 (I think) there’s going to be an option to select different items for the opening dashboard page - so direct to blocks for example, but not to hide sections. But agreed that would be awesome.
Somebody already customised by hiding all elements with CSS except the blog (he wanted a blog tool for a client) but that’s a great idea. Noted
I started hiding the Pulse UI from clients back in version 2 by simply hiding elements using CSS. This was later picked up by Mark and the stylesheet was incorporated into Pulse itself.
I even wrote a bookmarklet that unhide the items so you could work on the hidden parts of the CMS.
Adding an option to the config would be a useful addition although maybe Pulse ultimately needs a client user level creating that limits some of the functionality and stops users from deleting or renaming blocks.
Oh definitely. This was a great feature in the old version of Pulse. We definately do not want editors going into the pages section. They already find it hard to understand the concept.
Until such time as it is baked in, how can we hide it in CSS?
I had to do something very similar yesterday for a client who is little too keen on playing with features in the CMS.
What I ended up with was this to hide the new gallery button;