Custom page layout , OOTB layout or fixed layout

iwTech

What is the best approach ?

Pls share your thoughts.

-Vin

Find more posts tagged with

Comments

curiousmaverick

Starting point would be here your HTML wireframes.

Simple Crosstab.rptdesign

Rick Poulin

It's been my experience that fixed layout with custom layout definitions specific to your wireframes work best. It's really the only way to enforce your template (if you have one designed), not to mention any consistency in the look+feel of a site. Things just get messy fast with freestyle, but it depends on how nailed down your design is, and how much control over presentation you want to give the authors.

Personal opinion: I've always seen freestyle as the answer to "we don't have any developers; we just want authors to start creating pages". Even then, web folks that are used to dreamweaver usually develop some kind of page skeleton that they copy from page to page, so I've yet to hear a convincing argument in favour of freestyle.. I'd be interested to hear one if anybody's got one.

SplitData.zip

Faizi

In my opinion fixed layout is fine. If you need HTML5 support then you need to go with custom layout option.
Although HTML5 option is coming while creating a page but proper DOCTYPE is not being added on generated HTML source for .page file.

Rick Poulin

In my opinion fixed layout is fine. If you need HTML5 support then you need to go with custom layout option.
Although HTML5 option is coming while creating a page but proper DOCTYPE is not being added on generated HTML source for .page file.

That's not true. Just stick this in your conf/livesite_customer/pagetype-config.xml


<layout-config>
  <page-types>
    <page-type id="html5">
      <name>HTML 5</name>
      <output>
        <doctype>
          <document-root>html</document-root>
          <doctype-public/>
          <doctype-system>about:legacy-compat</doctype-system>
        </doctype>
        <method>html</method>
        <content-type>text/html</content-type>
        <omit-xml-declaration>true</omit-xml-declaration>
      </output>
      <allowed-layouts>
        <layout refid="fixed-layout"/>
      </allowed-layouts>
    </page-type>
  </page-types>
</layout-config>

This produces the legacy-compatible doctype (http://www.w3.org/TR/html-markup/syntax.html#legacy-tool-compatible-doctype) which makes everything happy.

Background: LiveSite uses xalan for XSL transformations, and that project can only produce the legacy-compatible doctype. They have no plans to produce a "proper" html5 doctype, at least not until a new major version. That means LiveSite isn't going to be able to produce it either, unless Autonomy replaces that library with something else (not likely).

Faizi

That's not true. Just stick this in your conf/livesite_customer/pagetype-config.xml

This produces the legacy-compatible doctype (http://www.w3.org/TR/html-markup/syntax.html#legacy-tool-compatible-doctype) which makes everything happy.

Background: LiveSite uses xalan for XSL transformations, and that project can only produce the legacy-compatible doctype. They have no plans to produce a "proper" html5 doctype, at least not until a new major version. That means LiveSite isn't going to be able to produce it either, unless Autonomy replaces that library with something else (not likely).

You are correct rpoulin, but this is a customization not OOTB that is what i have mentioned.
The same thing i have done in one of implementation.