10/09/2007 © Copyright 2009 Content Here.

<!--content here -->

Web Content Deployment Patternspresented by Seth Gottlieb

The Gilbane ConferenceSan Francisco, CA

June, 2009

1

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Patterns?

2

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Patterns?

2

Re-usable solutions to recurring problems

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

All WCM systems do it

3

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

All WCM systems do it

3

When?

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Key distinction

4

FRY BAKE

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Different architecturesRequest Time

5

management

delivery

management

repository

publisher delivery

!=

repository

Publish Time

FRY BAKE

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Key distinction

6

PUSHPULL

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Each has its advantages

7

Performance/Stability

Dynamism

high trafficpersonalization

access controlcost savings

availability

decoupling“website in a box”immediacy

FRY BAKE

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

The products have chosen

8

FRY BAKE

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

The products have chosen

8

FRY BAKE

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Each can compensate

9

Performance/Stability

Dynamism

cachingclustering

code publishing

structured publishingdynamic client

fragment publishing

FRY BAKE

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Code publishing (parbaked)>> Strategy:

Use the CMS to publish

unexecuted scripting code to an

active delivery tier

>> Advantages

.. Good for small touches of dynamism with “Model 1” architectures

.. Choose your own scripting language

>> Disadvantages:

.. Breaks “MVC” because model is baked into the view

.. Deployment issues on Java. Better for .NET and PHP based delivery tiers.

10

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Dynamic client>> Strategy:

Statically publish content and use Javascript on the client to add dynamism

>> Advantages

.. Minimal disruption to static publishing system

.. Lightweight integration across multiple systems

>> Disadvantages:

.. Security can be a problem

.. SEO issues

.. Accessibility issues

.. Browser compatibility11

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Fragment publishing>> Strategy:

Use the CMS to publish HTML fragments that can be assembled by a dynamic web application

>> Advantages

.. Good for static blocks like headers, footers, and “about pages”

.. Works well with portals>> Disadvantages:

.. Preview issues

.. Fragments are static

12

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Structured publishing>> Strategy:

Use the CMS to publish structured content into a dynamic web application

>> Advantages

.. Maximum flexibility on the delivery tier

.. Maximum de-coupling: “Separation of Concerns.”

>> Disadvantages:

.. Need to have a data driven delivery tier

.. Preview is often problematic

13

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

Key challenges>> Baking systems

.. constant publishing

.. extensive interlinking

.. user generated content

>> Frying systems

.. distributed delivery data centers

.. highly variable traffic

14

11/2/2008 © Copyright 2009 Content Here.

<!-- content here -->

15

Thank You

Seth GottliebContent Hereseth@contenthere.net http://www.contenthere.net