ideas on implementing custom FAL sitepublisher templates for html5 semantic tags

Our new responsive homepage uses html5 semantic tags. header, footer and main content is wrapped in respective semantic elements. for example <header role="banner"> , <footer role="contentinfo"> , <main role="main">.

Ideally these semantic tags should be generated from fixed layout master template (/com/interwoven/xsl/runtime/fixed-layout.page.xsl). But this template currently works in a way so that it adds <div> tags corresponding to the custom ( Fixed Area layout ) FAL xml file.

I am in a limbo now , changing fixed-layout.page.xsl may break our old sitepublisher pages . Is there a way I can accommodate 2 types of Fixed layout pages in our implementation, that is , one based on new semantic tags & the second one based on <div> tags? I am aware that somewhere inside the livesite code , word "fixed-layout" is hardcoded , thus preventing me from having another type of fixed layout .

Have any of you tried this before? Any pointers will be highly appreciated.

Thanks,

Mike,

TS 7.3.1 Build 20 Interwoven
Red Hat Enterprise Linux Server release 5.3 (Tikanga)

Find more posts tagged with

Comments

Rick Poulin

As you mentioned, you can't have multiple fixed layout definitions and changing that fact basically isn't possible.

What you might be able to do is change your master stylesheet to respond differently based on the canvas that is being used. So even if your new pages use the same layout as the old pages, copy the layout and call it something else. Then you'll have something on which to fork the logic in the master stylesheet. Presumably, you could then just fade out the old one over time and eventually clean up your stylesheet when the condition is no longer needed.

MikeMiracle

Thanks rpaulin, your comments are very valuable.

But, in this implementation, SitePublisher is used for inbuilt preview only. So I think a better approach is to write proper css for the canvas xml. My initial aim will be to display the preview properly and I am not worried about html structure at that stage.

But at the next stage (page generation), I need to have some logic which will remove the <div> tags and replace them with html 5 semantic tags. As it is all in a workflow, a custom task which uses xslt might be able to achieve this. If you have a different view on this approach, please let me know.

Rick Poulin

Huh? Your reply implies that you think my suggestion doesn't apply to you because you're generating pages. My suggestion doesn't require a runtime, and more or less suggests a way forward based on your initial hypothesis.

Obviously, it would be even better if you can write your css/js in a way that doesn't care whether the extra semantic tags are in place. I just assumed that since you're asking, that's not feasible in your situation.

Post processing in workflow is certainly an option, but that won't help you for preview so then you end up with two solutions instead of one...