My department is beginning to incorporate pages into our KB because they do a great job of providing a place for overview-type articles on content nested under the page. But I'm a little concerned that our end-users won't think to click the folder title itself and potentially miss critical high-level information needed to understand our software's more complicated features.
For example, there currently isn't a way to visually distinguish pages from indexes or folders in the category manager. In Image A (see attachments), if I told you that 1 of the below category types was a page, 2 were indexes, and the rest were regular folders, how would you know which is which without clicking every category?
I also, in particular, navigate the category manager primarily using the > arrow expanders / collapsers. There isn't really a reason behind why that's how I navigate other than "that's just how I do it". But if other users press the arrow to open up and browse content in the category manager like myself, then the page itself won't load and users won't be getting the context they need.
Maybe it could help to include icons in the frontend (see Image B), the same ones used in the backend to help Doc360 users navigate their category manager. That way, users can see that the "Workflow Steps" functions like a folder with some kind of readable material attached to it. And once they figure out we're including key contextual information at the "folder-level", then they'll know to reference such information if they see the icon.
I'm conscious that not all customers share our same preferences. I'm sure there will be other customers who prefer no icons, so perhaps this can be something you can easily toggle on/off. E.g. "Show category icons in category manager".

Photo Viewer

View photos in a modal