going multi-tenant with dotcms

42
Building a CRAPLOAD of Web Sites in dotCMS

Upload: dotcms

Post on 07-Nov-2014

2.821 views

Category:

Technology


1 download

DESCRIPTION

ehc takes us on a tour of how they are leveraging dotCMS v1.9's advanced multi-tenant capabilities to manage 700 web sites that include; hospitals, outpatient facilities, physician practices and other medical service organizations.

TRANSCRIPT

Page 1: Going Multi-Tenant with dotCMS

Building a

CRAPLOADof Web Sites in dotCMS

Page 2: Going Multi-Tenant with dotCMS

OR

Creating a Site Building Framework

in dotCMS

Page 3: Going Multi-Tenant with dotCMS
Page 4: Going Multi-Tenant with dotCMS

700 WEB SITESWE ARE CURRENTLY CONVERTING

to dotCMS 1.9

Page 5: Going Multi-Tenant with dotCMS

CONVENTIONSare your friend

Page 6: Going Multi-Tenant with dotCMS

A connected base framework of HTML, CSS,

JavaScript, Velocity, and Containers that provide a

solid foundation for all sites.

Page 7: Going Multi-Tenant with dotCMS

Why Conventions Are Awesome

• Keeps your team on the same page

• You can go into any project and understand what’s going on, even if you didn’t start it

• You can go to edit an existing site and know exactly where to go to make changes

• Speedy implementations of CSS, JavaScript, Velocity, and other cool stuff

• Enables designers and project managers to implement complex functionality

• Ensures quality control

Page 8: Going Multi-Tenant with dotCMS

How we're using conventions

• “Pluggable” pieces

• Sharing as much code as possible across hosts

• Naming conventions

• Folder structure

• Browser Support, Graceful Degradation, Progressive Enrichment

• jQuery minimalism

• Project Stages and Basecamp

Page 9: Going Multi-Tenant with dotCMS

2GLOBAL

LOCALbe lazy

vs.

Page 10: Going Multi-Tenant with dotCMS

In 1.9 everything lives self-contained on a host.

Because the sites run on the same code base, this

means that we would end up with lots of dupli-

cate containers, vtls, CSS, and jQuery plugins.

Page 11: Going Multi-Tenant with dotCMS

Global Host

• The host where we distribute all the global pieces of our site building framework.

• Host CSS for base layouts, print styles, and mobile styles

• Host jQuery plugins and other global JavaScript

• Host all containers for velocity powered functionality and HTML

• Global content delivery (CDN)

• Host files referenced by widgets and containers used across sites

Page 12: Going Multi-Tenant with dotCMS

Basically, we come back to the age-old principle

of being lazy. Do something once, and then reuse

it a thousand times.

Page 13: Going Multi-Tenant with dotCMS

3AND NOWAN

EXAMPLE

Page 14: Going Multi-Tenant with dotCMS

St. Mark's Hospital

Page 15: Going Multi-Tenant with dotCMS
Page 16: Going Multi-Tenant with dotCMS
Page 17: Going Multi-Tenant with dotCMS
Page 18: Going Multi-Tenant with dotCMS
Page 19: Going Multi-Tenant with dotCMS
Page 20: Going Multi-Tenant with dotCMS
Page 21: Going Multi-Tenant with dotCMS
Page 22: Going Multi-Tenant with dotCMS
Page 23: Going Multi-Tenant with dotCMS
Page 24: Going Multi-Tenant with dotCMS
Page 25: Going Multi-Tenant with dotCMS
Page 26: Going Multi-Tenant with dotCMS

GLOBAL HOST

print.css mobile.css ie6-reset.cssreset.css base.css

LOCAL HOST

ie6.cssscreen.css ie7.css

CSS

Page 27: Going Multi-Tenant with dotCMS

reset.css

• resets all the annoying default styles that browsers love to add

• provides a blank slate to start from

• on global host and cached across all of our hosts

Page 28: Going Multi-Tenant with dotCMS

base.css and screen.css

• controls basic layout

• hosted globally

• @ import the base of your choice for a layout

• screen.css provides layer of typographic and graphic styling locally

Page 29: Going Multi-Tenant with dotCMS

print.css

Page 30: Going Multi-Tenant with dotCMS
Page 31: Going Multi-Tenant with dotCMS

ie6-reset.css

• not all browsers, especially older ones, are going to see exactly the same design

• providing a layer of content level support by using one stylesheet that provides a simple, usable design

• using the same HTML naming conventions makes this really easy

Page 32: Going Multi-Tenant with dotCMS
Page 33: Going Multi-Tenant with dotCMS
Page 34: Going Multi-Tenant with dotCMS

mobile.css

• User Agent detection

• iPhone specific Meta tags

• Currently works with iPhone, iPod, iPad (he he) and most other mobile browsers

• Fully CSS-powered; no JS

Page 35: Going Multi-Tenant with dotCMS
Page 36: Going Multi-Tenant with dotCMS

jQuery

Page 37: Going Multi-Tenant with dotCMS
Page 38: Going Multi-Tenant with dotCMS
Page 39: Going Multi-Tenant with dotCMS

Omniture Analytics

Page 40: Going Multi-Tenant with dotCMS

Omniture Search

• meta tag based indexing controlled by logic in the head container

• giant content pull for indexing (site-map.dot)

• xml based response

• results page widget

Page 41: Going Multi-Tenant with dotCMS

ehc Components

• Distributed across all our sites, tying into our global host.

• similar to dotCMS’s Application widget

• Versioning by structure. ehc Components v1 widgets, v2, v3 ... v#

Page 42: Going Multi-Tenant with dotCMS

Watch for more details on our blog.