Hi Jared,
Thanks for summarizing this. I had lost track of past decisions. I
think things have changed significantly since we discussed this last.
The philosophy page is going away. We will have a single Vision
Document that Katie, Ted, Sheila and I have been pulling together. I
think our assumption has been that that would do fine on the wiki.
We don't have plans for a screenshots page. I believe that's been
rolled into Pieter's Getting Started Guide, which will be static
HTML. I imagine the screenshots on the landing page will link to the
guide.
I'm not sure about the release notes, Sheila?
How is that different from the Feature List and Known Issues pages? I
don't think we were planning on putting together a document with lots
of screenshots in addition to the Guide.
So I think Landing Page and Getting Started Guide are the only 2
static pages.
Mimi
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/)
* 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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
