Bricolage---
David Wheeler

----

Standards, formats looks and feel inconcistant
workflow issues
Multiple formats
--
WHO 
100 dept 
100 workflows
1 DB
--

Bricolage
Document versioning , loocking , ci co

Browser Based 
Customizable, workflow , permisisons
Content storage, output diff, output via template
SOAP, database FTP 

---
Mason / mod_perl --- Mac OS X
SSL 
Postgress  --- UNICODE

--- Docs 
Stories vs  Media
Docs are made of elements
	hierarchically
	subel, fields -> HTMl
			
---Document Analysis
Model stucture-----DEEP
  Paragraphs count
	Pull qouytes
	next pages
	media boxes 
	headerfs

---Meta
Titles
Bylines
---
Media and Text handled seperatly
---Perms
by user, handled in UI Level
---Docs ,and Templates are seperate


--$burner
Managers templates
$m like, trigger element output
category info  --> can use for the breadcrumb, uri, etc

---$element global
Element for curr docs
contain content
	sub el,
	media
	data
	etc ....
for $elements->get_elements
	-> get_data
	->get related story


-- Templs
Cat, Element, Utils

----CatTemplates
are autohandlers
cascade down the tree, of cal_next call the next template that might be resposible

for /reviews/books
looks for template in ROOT then REVIEWS then  BOOKS

Then does Document templates

----Element Templates

like dehandler, up the tree
1 for each element type 
$burner->display_pages ==== does for this page, then the next like a for loop but magical

can ignore or use anything in the template

--- Utility Template
executed by other templates, manually
workfow and version


----Higher
many doc type same elements
CMS --> produces FLAT HTML to publish


--- UI
has element editor, that includes cheat sheets, containers  Data elesments

---Versioning
---Virtual FTP server
everything is in the DB
SOAP,HTML and Virtual FTP server, WOW