Bootstrap3

[Ree]

The only "issue" with bootstrap is the navigation with dropdowns (if you use multilevel menus).
Well not exactly an issue but if you want to have parent menu items to be clickable(well to navigate to their links) then you need to hack/extend the core bootstrap navigation.

That was actually one of the things I liked about Bootstrap! The previous template I used on all my sites had to have what I would consider redundant pages to allow mobile visitors access to the sub-menu items since it was only possible for the to click on the parent (so clicking on the parent simply displayed a page containing a list of the sub-menu links). With Bootstrap that's no longer necessary since clicking on the parent expands/collapses on all devices.

I can see why some people would consider it a good thing to be able to click on the parent though. Maybe I'll look into adding a new "make parent clickable" option that will enable hovering on desktop and duplicating the parent menu item in the sub-menu on mobile. I previously looked at the hover mod that you linked to below, but haven't tried it yet to see how it messes with the menu, but hopefully that can be worked around (or will be fixed soon).

I've just found out that if you place the following CSS in the css/Bootstrap3.css file then any inserted images scale gracefully in all devices and browser widths.

img, img a {
max-width:100%;
}

I debated on whether to add this to Bootstrap3.css or not. I'm using that CSS inline on my screenshots on randm.ca, so I agree it's useful, but I wonder if there may be circumstances where people wouldn't want it so then it wouldn't be good to have in the .css file.

I absolutely can't get this working, I can't find Bootstrap3Settings.xml, which i probably causing the total crash.. I'm extremely frustrated about this.. any help?

Poor coding on my part. What you're seeing are notices informing you that $Settings is undefined, which it will be the first time the page loads because I only define it if Bootstrap3Settings.xml exists (and it only exists after you save your settings). I'll have to update the code to assign default values to $Settings if the file doesn't exist, then the notices will go away.

Since they're just notices it shouldn't be causing a crash though. Are you able to fill out the form and hit save? If so I would expect the notices to go away at that point.