I have a completed a Site Designer v3 website (see footer). However, I am not completely happy with the navigation menu I created. I have looked at a few that users have shared in this community and like the vanilla navigation setup.

My question is, as my project file already exists and there are no components in the library, how can I get the vanilla menu from a second Site Designer 3 project into my existing one?

Probably simple, but I haven't worked it out yet, any help much appreciated.

To transfer such an item from one RSD file to another I do the following -

(a) I make the item into a component and save it to the components library as shown here.
(b) I then open the RSD project file into which I wish to transfer it, and find that it is in the Components library in that project. One can therefore in the Components section use the 'Add Component from Library' button.

There is one limitation: both of the RSD project files must be using the same framework (Foundation, Vanilly ...).

Frank

Hi Frank,

I did try that method, but there was nothing to add, component library was still empty! Maybe this is because my SD3 website is bootstrap and not foundation...

Anyone got any bootstrap examples similar to the vanilla drop-down menu I could take a look at?

How about this one: http://horgenhonning.net/sharing/sd3-st … index.html

Hi Inger,

Thank you for the link to the BS menu. Unfortunately it suffers from the same white-space issues I reported that my existing menu has. See this post <white-space menu click issues>

Since SD V3 Vanilla is very plain, it would probably be possible to reconstruct an SD 3 Vanilla menu in an SD V3 Bootstrap project file. I'm wondering to which Vanilla navigation setup the quote above refers.

Frank

Rooky,
After checking a bit I have come to the conclusion that when you operate with text links, the normal behaviour is, that you actually have to click the link itself, not the white-space, to navigate.
It's different with button links, though. They can span the whole available width and you can click anywhere on them. And they don't have to look like buttons.
Try that file again, that I suggested to you. I have modified it so that I have removed the text links and used button links instead.

Hi Inger,

Managed to get your changes into my SD v3 as a bootstrap component np (see Frank's post above). When adding the component to a new BS project the menu works beautifully. However, importing into my existing BS project was less successful... I appear to have fallen foul of different style rules. When adding to my SD project a warning box message pops up stating BS4 classes might need to be re-added, which I guess they do as the menu is not as nicely formatted as when embedded onto a new project.

Is this a case of a element by element, line by line review of the two menus to see where things are different?

Not sure what causes that. Your project is in Bootstrap4 (according to the source code), so is the menu. But you may perhaps have used some of the class names that I also used, but with different properties. I wouldn't know that, because I have never seen your project file.

I'm assuming that you have removed the old navigation before adding a new one, clearly.

The only difference between my first and my second version of this menu is that the submenus, class name '.dropdown-menu', consist of an unordered list with three list items in the 1st version, and a list container with three button links in the 2nd. I have used the same class names in both versions.

Thank you Inger,

I examined the navigation menu you made changes to and was able to apply the some of your workings into my original navigation menu successfully.

Two days on this one, but might have been a lot longer without your help, and of course those others within this forum community willing to share their expertise and experiences