Labels

accessibility (2) ADF (1) archiver (3) cmu (1) contributor (13) cookie (1) DAM (3) date (3) download (3) dynamic list (4) ephox (5) fatwire (1) fck (1) filters (1) folders (4) headers (2) IBR (3) ImageAlchemy (3) java (4) javascript (2) layout/template (4) link (6) locale (2) multilingual (1) rendition (3) replicator (4) rules (1) schema (1) search (11) sites (1) sitestudio (24) ssp/sspu (5) SSUrlFieldName (2) stellent (4) timezone (1) urm (1) weblogic (1) workflow (2)

Thursday 11 December 2008

SiteStudio10gR4 - Region Definitions & Region Templates

Forgive me for back-dating this post but I wanted to mention my excitement over the upcoming release of SiteStudio 10gR4. There was a webcast/webinar/webthingy where Oracle announced a new version (hopefully due in Jan09) where the main new features are region templates and region definitions.

Currently all layouts contains content regions that are defined and styled by settings in the layout. Editable elements in the region are also controlled in the layout. It leaves heaps of non-web code on the page and it is awkward to customise the display of content items. My real-world example is trying to maintain identical element settings in over 40 separate layouts, phew.

The definition of a region is now a separate "Region Definition" xml file. It has all the usual options (edit, info, approve, view differences) plus it now has the element definitions. Element definitions have been expanded, like allowing people to insert Flash as easily as inserting an image. It's separate to layouts, so in my 40-layout example all I would need to do is update the one definition file, instead of each of the 40 layouts. The region definition also controls the assigning of selected region templates.

The "Region Template" is also a separate xml file. It controls the presentation of content inside the region. An example they gave was a template that took a static list content item and displayed it as tabbed panels. Applying a different template changed the list into a flat page of heading & paragraphs. Hmmm... this looks ideal for creating navigation that is not section-based. Yay! They had another example that loaded a dynamic list query of images into a flash object. All the contributor had to do was change the query. Neat.

Other points of interest:
* Easy choice of FCK or Ephox editors
* Override the chosen editor's config or css, per element
* More element types (querys, dropdowns etc)

This brings some real power to contributors and yet it gives tighter control to designers. Impressive! I can't wait.

*****
UPDATE - Oooh oooh the new docco is now available on the Oracle site... it says they updated the LinkWizard! Yay! I can't find a picture... but it seems to work the same? Bah!

2 comments:

  1. I have region definition that contains three element.
    1. A text element for title
    2. An image element for picture
    3. A WYSIWYG element for detail content (That will fill the replaceable region of secondary page)

    Now i want to display only image element on my home page form content file that is based on region definition described above.

    how can i access that image ?

    I am able to access the title with following idoc script

    <$ ssIncludeXml(dDocName,
    "wcm:root/wcm:element[@name='title']/text()") $>

    What version of this idoc script i should use to access the image element.

    Waiting for a helpful response

    Sadia

    ReplyDelete
  2. Sadia, the image is loaded the same way. Just change the @name= value.

    ReplyDelete