I’ve built and continue to manage http://www.mindful-taichi.co.uk site, which uses the BAM menu action on my CSS menu. All works great on desktop machines, but would like to make improvements to how it works on iOS and Android devices.
I know it’s been in beta for a while, and (from a very quick look) does not appear to work in FW6. So, basically what I’m looking at doing is rebuilding the menu system with something more compatible. I really like how it works at the moment, so looking for something that will look identical.
Cheeky side question - the site has now been fully indexed by Google and appears well in search engines if I search for mindful tai. How much of that is down to using a CSS menu system, and will I break any of that if I replace the menu?
Thanks for the reply. I was thinking of probably dropping the action and looking for an alternative way of construction, and that’s the answer I’m scratching my head over. Maybe a show/hide layer type effect or something similar - any ideas?
Neither BAM nor target show/hide are for me basic concepts to play nice on small screens. Both are space consuming concepts that you don’t have, though.
As a result, big menus on desktop devices are often more or less styled simple drop-downs for smaller screens just to keep navigation always available and compact to use.
Another concept, that might be much nearer to your needs could be this “slide in from aside” concepts. This could enable you to get back the “need more space to present” aspect.
A simplified version of this:
Whether you follow the responsive idea or the redirect to a second specified mobile design (which I would prefer) is up to you.
But what I definitely would do is to take (a screenshot) of an iPhone (just to underlay) first and start scribbling the page for this area. This is amazing cause it makes you merciless clear how less space you’ve got available.
Many thanks for the replies - really appreciate you taking the time.
If I was to go down the target show/hide layer route, will this have a detrimental effect on how the site is indexed by Google (as opposed to using a ‘proper’ CSS menu like it is now), as presently (after about 5 months from launch) the site’s menu breakdown appears in search results and I’d like to keep this (search google.co.uk for ‘mindful tai chi’ and you’ll see what I mean).
Thomas - thank you for your examples. This is a bit over my head and I need to have a think about how I’d approach it, a lot of reading up to do! Obviously, the first example you showed is excellent, and I understand where you’re coming from with regards to the space it uses up.
Given time, I don’t mind rebuilding the site again as a box model site, and completely in FW6, but as the site needs updating now I’m keen to address the BAM issue as soon as possible.
I’ve just updated the BAM Action to deal with the way Freeway 6 handles CSS styles. Previously (as many of you know) this was breaking the Action. The updated code uses Walter’s excellent Style Accessors CSS library (http://actionsforge.com/articles/view/11-get-and-set-css-styles-in-freeway-6) so a big thanks to Walter for making this possible.
