terminalfour t44u 2009 - university of york case study

45
BEYOND .HTML – BEYOND .HTML – MULTIPLE FILE MULTIPLE FILE EXTENSIONS IN SITE EXTENSIONS IN SITE MANAGER MANAGER Dan Wiggle, Paul Kelly (dw538 / pak500 @york.ac.uk)

Upload: terminalfour

Post on 19-Jun-2015

144 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: TERMINALFOUR t44u 2009 - University of York Case Study

BEYOND .HTML – BEYOND .HTML – MULTIPLE FILE MULTIPLE FILE

EXTENSIONS IN SITE EXTENSIONS IN SITE MANAGERMANAGERDan Wiggle, Paul Kelly(dw538 / pak500 @york.ac.uk)

Page 2: TERMINALFOUR t44u 2009 - University of York Case Study

Overview

Why we needed multiple file extensions

Developing the new feature

Using multiple file extensions

Page 3: TERMINALFOUR t44u 2009 - University of York Case Study

The way things were

Single extension per channelPick a default filename for a channelNo exceptions

Page 4: TERMINALFOUR t44u 2009 - University of York Case Study

RSS on a separate channel Separate RSS channel Top content navigation objects retrieve

content and a formatter outputs in RSS format Publishes to same filestore as main channel

Page 5: TERMINALFOUR t44u 2009 - University of York Case Study

Empty feeds, everywhere

Page 6: TERMINALFOUR t44u 2009 - University of York Case Study

Thousands of errors

Page 7: TERMINALFOUR t44u 2009 - University of York Case Study

More channels = longer publish

Page 8: TERMINALFOUR t44u 2009 - University of York Case Study

iCal abandoned

http://www.flickr.com/photos/keso/2262459574/

Page 9: TERMINALFOUR t44u 2009 - University of York Case Study

Coldfusion Serving everything

as .cfm unrealistic Another whole channel

not realistic ‘Wrapping’ possible, but

not scalable

So… left out of the CMS altogether

http://flickr.com/photos/oguz/3771024673/

Page 10: TERMINALFOUR t44u 2009 - University of York Case Study
Page 11: TERMINALFOUR t44u 2009 - University of York Case Study

“Maybe in version 7…”

Page 12: TERMINALFOUR t44u 2009 - University of York Case Study

Into v6.2

http://www.flickr.com/photos/35588958@N07/3491438500/

Page 13: TERMINALFOUR t44u 2009 - University of York Case Study

Developed a specification

Page 14: TERMINALFOUR t44u 2009 - University of York Case Study

Development

Committed to work late March

Initial remote demo early June

First test build installed at York late June

Page 15: TERMINALFOUR t44u 2009 - University of York Case Study

Testing

Page 16: TERMINALFOUR t44u 2009 - University of York Case Study

Release

Page 17: TERMINALFOUR t44u 2009 - University of York Case Study

Rebuilding our feeds

Fewer files

Fewer errors

Quicker publish

Simpler configuration

Page 18: TERMINALFOUR t44u 2009 - University of York Case Study
Page 19: TERMINALFOUR t44u 2009 - University of York Case Study
Page 20: TERMINALFOUR t44u 2009 - University of York Case Study

How we rebuilt the feeds

New configuration options

RSS style

Re-used top content navigation objects

Page 21: TERMINALFOUR t44u 2009 - University of York Case Study
Page 22: TERMINALFOUR t44u 2009 - University of York Case Study
Page 23: TERMINALFOUR t44u 2009 - University of York Case Study
Page 24: TERMINALFOUR t44u 2009 - University of York Case Study
Page 25: TERMINALFOUR t44u 2009 - University of York Case Study
Page 26: TERMINALFOUR t44u 2009 - University of York Case Study
Page 27: TERMINALFOUR t44u 2009 - University of York Case Study
Page 28: TERMINALFOUR t44u 2009 - University of York Case Study
Page 29: TERMINALFOUR t44u 2009 - University of York Case Study
Page 30: TERMINALFOUR t44u 2009 - University of York Case Study
Page 31: TERMINALFOUR t44u 2009 - University of York Case Study
Page 32: TERMINALFOUR t44u 2009 - University of York Case Study
Page 33: TERMINALFOUR t44u 2009 - University of York Case Study
Page 34: TERMINALFOUR t44u 2009 - University of York Case Study
Page 35: TERMINALFOUR t44u 2009 - University of York Case Study
Page 36: TERMINALFOUR t44u 2009 - University of York Case Study
Page 37: TERMINALFOUR t44u 2009 - University of York Case Study

iCal

Page 38: TERMINALFOUR t44u 2009 - University of York Case Study

Style vs. template extension choice

RSS and iCal have file extensions set by the section style

Other uses set the file extension based on a content item’s template…

Page 39: TERMINALFOUR t44u 2009 - University of York Case Study

Integrating dynamic content - before

Static HTML

Page 40: TERMINALFOUR t44u 2009 - University of York Case Study

Integrating dynamic content - before

Dynamic ContentWidget

(eg .cfm)

= new channel

Page 41: TERMINALFOUR t44u 2009 - University of York Case Study

Integrating dynamic content - now

Page 42: TERMINALFOUR t44u 2009 - University of York Case Study

Integrating dynamic content - now

Section containing content that requires CFM extension will be published as index.cfm

Page 43: TERMINALFOUR t44u 2009 - University of York Case Study

Future uses

Training courses database integration Authenticated streaming video Same-page form validation PHP for Computer Science Integration of legacy cfm apps

Page 44: TERMINALFOUR t44u 2009 - University of York Case Study

Still on the wishlist… Parameter-ised content would allow us

to:Add an ‘rss feed’ content itemFill in fields for branch and number of itemsHave a template formatter pass field values

to a generic RSS navigation object which retrieves content based on those parameters

Coming soon…? ;)

Page 45: TERMINALFOUR t44u 2009 - University of York Case Study

Any questions?