Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
Hello, Overall, liking RocketCake - I've not been using it long, but I've got one sticking point to do with navigation menus, and it's really bugging me. I've just trawled back through the forum looking to see if anyone else has raised this, and no-one seems to have, which makes me think it's me just being daft and missing the obvious, but here goes... So, I have a single navigation menu set up in my master page, no sub levels, all my other pages use it and the links all work just fine. However, on most websites it's normal for the nav menu to mark in some way which page you're currently on - so the current page is like bold, or highlighted in some other way. I can't quite seem to find a way to do this utilsing the master page method. Only way I can see to do this (at least in the free version) is to add the menu in to all pages and manually highlight the menu option for the page I'm on. This seems a bit crazy, not to mention longwinded if I want to add additional pages. I'd have to edit the menu across all pages. Am I missing something here? By way of explanation, just in case I've really explained the issue badly, here is a link to a website that uses this, click a different page, when you get to that page the link for in the menu is marked so you know where you are. https://drakeofficial.com/ what gives? |
||||
|
Yes, you are right, there is no way to do this unless you do it like you imagined yourself. I'll think about a better way to do this and probably add this in an update. |
||||
|
wrote: Yes, you are right, there is no way to do this unless you do it like you imagined yourself. I'll think about a better way to do this and probably add this in an update. Much obliged, thank you, Niko! Honestly, it's not a deal breaker - I think RocketCake is a very good website building solution even with this little niggle. And I have seen lots of sites that work without highlighting the current page, it's not completely universal. I was really surprised no-one seemed to have mentioned it, which is what led me to believe that I might be completely wrong and missed something. Wonder how easy that might be to implement? I mean, obviously the way it works now primarily kind of enables the use of the sub menus. In order to highlight the page, the menu element on the master page would have to reference the current page then match it up to the right link in the menu, then highlight it accordingly - presumably with a set of customizations for colours and stuff defined it's own properties. It might actually need a different type of menu in the toolset just for that purpose? On a slightly different - but I suppose also slightly related note - the master page itself... This could just be me being ultra picky, but obviously I make the master page, it looks good, it contains all the elements I want shared across all the pages. I know where the content will appear in the master page as it's dictated by the placeholder. And so, I go to create the content in those other pages that will go within the placeholder, and obviously - yes, it works. But I personally find it really odd working on those pages without being able to see in the editor how they will look with the master page elements present. It's like I don't know if they'll look good until I do a full preview. Sure, they probably will look just fine, but to my mind - a WYSIWYG environment ought to be showing you, well - what you'll get! But when you're editing a single page like this, what you see obviously isn't quite what you're going to get. As I said, I know it works, it's also not currently a deal breaker - but I find slightly - disconcerting, I guess! I know a few other editors utilise a layers system, you create the master elements in these shared layers, so background is persistently shown under the content in a low master layer, and obviously something like a menu would be persistently shown but on a higher master level, but they are visible in the editor no matter what content page you're working on. I guess it helps the user 'keep it all in context' a bit easier. I don't know, maybe I'm just overly fussy?!!!!!!  I know that might actually mean in real terms, something of a re-imagining of how RocketCake would work. In fact, you're probably technically looking at a quite a major redesign to implement that, and for what may just be me relying overly on my own visual peculiarities! But I thought I'd throw it out there. |
||||
|
It's not difficult to implement, the bigger problem is how to make it work generically and with a very simple user interface, which won't complicate things for users not using that feature. So I'll have to think a bit for this. You are right, maybe I should add an option to preview the content in the master pages, would be an idea. Let's see. :) |
||||
|
|
){kind=link}