I think you may need to re-think this page in terms of how it’s structured. The Action isn’t doing you any favors here in this regard. While all the text is kept in the page, and thus is technically there for the search engine to consume, it’s not structured in any way that the outline checker can recognize. You have N separate (floating) DIVs, each containing an H2 and a little bit of text, and they aren’t nested into one another or in some outline structure that the outliner can grasp.
I wrote these carousel effects to take the kind of layout that Freeway can create easily and merge it into a whizzy effect. Ironically, the original Carousel was more semantic than the current iteration, because it actually horsed around with the elements on the page and moved them into “slide strip” structure:
div#outer
div#slider
div#pane1/
div#pane2/
div#pane3/
/div
/div
The latest version was written at a time in Freeway 6’s development when Actions could not accurately see or change the CSS styling of an element on the page. I have since written a set of library code that makes this possible, although there are serious teething pains within it and I haven’t had time to sit down and sort that out. (It forces a full page republish every time a page it’s on is published – even with no changes at all.)
As a result, Carousel 2 uses JavaScript to rearrange the DOM at page load rather than Action mechanics during publishing. The page is a fragmented mess when published, but brought into the structure you see above after the JavaScript rearranges the DOM. Unfortunately, outliners can only see the source code, not what a browser makes out of it.
You could try building your carousel as an inline construction, with all of the panes inline within a parent wrapper DIV containing the main pane, and with that wrapper set to Overflow: hidden so the extra panes are not visible when the page loads. The JavaScript will still stir the page around and add the inner slider element, but if you started from here:
div#wrapper
div#pane1/
div#pane2/
div#pane3/
div#pane4/
/div
then the outliner would still see those h2s as meaningful members of a hierarchy of content.
Walter
On Oct 3, 2013, at 1:03 PM, RavenManiac wrote:
So, should I change the h2 tags to another h1’s instead?
I think I understand the concept of semantics, but if the amount of content on a page is limited, what’s the point?
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
