Jared...comments inline.
On Jul 11, 2007, at 12:03 PM, Jared Rhine wrote:
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/)
As you mentioned, we have already identified this as a static page -
Mimi is working on it.
* The philosophy page ("index to ppt & pdf documents stored on wiki")
The page that Mimi is working on is on the wiki right now. We still
have quite a bit of content to write and refine and I recommend that
we stick to the wiki page for Preview. We will be lucky just to get
all the content done to be honest.
* The screenshots page ("big page lots of images")
I believe these are simply just part of the Getting Started Guide but
Pieter is a better person to answer that since I don't know how he is
planning on working these in. My understanding is that they were just
part of the guide and there wasn't some separate set of pages for this.
* release_notes.0.6.php ("big page lots of images")
So now that the release managers ( Jared, Philippe) are writing the
"release notes", I don't know what kind of content you have planned.
Basically, we will have some release announcement but I would think
it would be pretty low key - just to the mailing list etc. It's NOT
the Preview launch. I see this page that we have used before simply
getting replaced with the landing page, the feature list and all the
stuff we are working on for Preview. I guess what I am saying is...I
don't see why you guys would be preparing something like this in the
first place and it would be simply rolled in with all the other
documentation.
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
