[General] "4 static pages": What about screenshots?

Jared Rhine jared at wordzoo.com
Wed Jul 11 12:03:53 PDT 2007


This email summarizes the "4 static pages" issue that came up in a wiki 
planning meeting recently; Sheila, here's that recap I was going to do.

The bottom line: No worries; I've reviewed the legacy list and there's 
nothing to flag for Preview.

The issue: we've decided to put all the content we can on the wiki, for 
ease of maintenance.  But not every single page is suited to being a 
dynamic wiki page, for various reasons of performance, design 
flexibility, access control, or media-embedding reasons.

Pieter, in the April timeframe, did an analysis of "what pages need to 
be static or otherwise treated differently than wiki page"?

The results of that analysis were written up in the Community meeting notes:

   http://chandlerproject.org/Journal/CommunityMtg20070406

There, Pieter references a google spreadsheet:

   http://spreadsheets.google.com/ccc?key=pP90TPgaKp_N8fH1RZVtiHg&pli=1

with his results.

He identified four pages that he thought probably should be treated as 
static:

* The landing page (http://chandlerproject.org/)
* The philosophy page ("index to ppt & pdf documents stored on wiki")
* The screenshots page ("big page lots of images")
* release_notes.0.6.php ("big page lots of images")

The landing page, we're still intending to be static HTML for both 
performance and visual control reasons.

The next three, "a page with lots of media", are somewhat 
miscategorized; it's ok to embed media onto wiki pages, even video and 
flash and Java.  For some particularly large resources, I may pull IT 
rank and specify that the big file itself which is embedded on those 
wiki pages should not use the standard /pub attachment mechanism for 
performance, but we can address those as they come up.

We may want a "plainer" page for a screenshots page, though we can 
simplify the skin (really down to nothing) on any given wiki page (set 
SKIN = plain for blank template)

So Mimi, Sheila, that probably the only interesting bit from the 
investigation: the screenshots backend.  The image links on the landing 
page probably link to larger versions; where do they link to?  I think 
we want a ticket for "create screenshots wiki page"?  Or did you have 
another mechanism in mind?

-- Jared





More information about the General mailing list