Question 1 of 4: Adding additional things before the HTML tag and in the <head>

Hello! I'm very new to TeamSite and need some guidance on the best way to implement some things.

If you have reviewed my other questions, this section is the same:

<about>

Background: A vendor has designed HTML for a new site and we need to manage the pages in TeamSite. We have componentized the common aspects of the pages. The vendor developed the pages without consideration for requirements/restrictions of TS. Being a responsive design, we want to match the HTML provided by the vendor as closely as possible. This way, if the design doesn't work, we can push back to the vendor and request they fix it.

Products/Versions/Current Methodology: We are using TeamSite 7.4.1 with SitePublisher. No customizations have been made to the installation. The pages are currently based on custom fixed area layouts used in a template with various components which are then used to create pages using the same general format (c-clamp etc). NOTE: The pages are typical static marketing type pages and are therefore "invariant" with respect to each request, so we are deploying the HTML generated and NOT using the LSDS.

My background: I am an application architecture and have many years of experience. I know countless languages such as Java as well as technologies like XSL, XML, javascript etc. However, often I know only enough to be dangerous and not enough to say I'm an expert.

</about>

Consider reviewing the other questions posted in separate messages in case they would change your recommendation. They will concern controlling the excess divs generated by a fixed layout, controlling structure of the URL namespace when generating the HTML via the PLC and (somewhat unrelated) can a single server also serve as a development environment separate from the current installation so changes suggested for these questions be tested without affecting the current installation.

Question 1:

How can I add things like the HTML, meta tags and javascript bolded below to all pages? When the meta tags are simple name/content value, we use the page properties to add. Additionally, we have used the site resources to add the simple javascript includes....

<!DOCTYPE html>




<html class="no-js">


If the solution is either a custom page type or an "external" (which the docs lead me to believe are how this is done), could you provide short step-by-step directions (go the this file, add this section go to that file do such and such) and any example "snippets" or complete demos would be greatly appreciated...

Thanks in advance. Some here recently helped me with a problem in the generated HTML (the stuck in preview mode bug) and would really appreicate your suggestions on these problems.

Find more posts tagged with

Comments

WGM

I found the section in the Site Developers Guide on custom page types and it appears that is the best method for doing this.

Rick Poulin

WGM wrote:
I found the section in the Site Developers Guide on custom page types and it appears that is the best method for doing this.

Indeed it is. When you define your new page type, keep in mind that there can only ever be one "fixed" layout, so no other parts of your system will be able to use a different top-level stylesheet for fixed layouts. Also keep in mind that this stylesheet is only applicable to preview and runtime modes. There's a separate one for edit mode, which I DO NOT recommend changing, but there are other ways around it. Ask again after you get your preview+runtime all working, if you need suggestions for this.

Note: I would recommend sending the X-UA-Compatible header via your web server or a LiveSite precontroller. IE tends to respond to it better, as it's sometimes picky if your <head> is so large that it has to start rendering the document before understanding which document mode you wanted.

WGM

When you say:

there can only ever be one "fixed" layout (suddenly I flashed on Highlander, there can be only one ;-) )

Is this still true if I create a new page type via:

<?xml version="1.0" encoding="UTF-8"?>
<!--
  This file contains customizations of page-type and layout configuration
  found in WEB-INF/classes/com/interwoven/livesite/pagetype-config.xml.
  You can use it to add new page-types and layouts (by specifying a new id)
  or override existing elements (by specifying an id that exists in the
  base file listed above).  Page-types in one file can reference
  layout types in the other, and a page-type in the base file that
  references an overriden layout-type in this file will use the
  overriden layout-type.
-->
<layout-config>
  <page-types>
    <page-type id="ourco-html5">
      <name>OURCO HTML 5</name>
      <output>
        <doctype>
          <document-root>html</document-root>
          <doctype-public/>
          <doctype-system/>
        </doctype>
        <method>html</method>
        <content-type>text/html</content-type>
        <omit-xml-declaration>true</omit-xml-declaration>
      </output>
      <allowed-layouts>
        <layout refid="ourco-fixed-layout"/>
      </allowed-layouts>
    </page-type>
  </page-types>
  <layouts>
    <layout id="ourco-fixed-layout">
      <name>Fixed</name>
      <stylesheet>com/ourco/xsl/runtime/ourco-fixed-layout.page.xsl</stylesheet>
      <class>com.interwoven.livesite.layout.impl.FixedLayout</class>
    </layout>      
  </layouts>
</layout-config>

Rick Poulin

What I mean is that I think you'll find your ourco-fixed-layout isn't actually a fixed layout. It'll be a freestyle.

The only way to create a fixed layout is to use layout id="fixed". Hence, there can only be one. Cue music.