Big idea of this email: Our wiki pages do have to live at a second
level. I have a hack in place now that may work out to provide the
nice-and-tidy chandlerproject.org/WikiHome (works now).
Mimi Yin wrote:
I'm not sure how important it is to have identical sidebars at this point.
I can live without them.
Do you think you'll always start at the landing page?
If it's useful, yes, because it's shortest.
A one-off billboard for end-users with links to content on the wiki.
A landing page could be that. But as described, I do think the root
page of our domain, chandlerproject.org, holds a special place in the
community flow and grows in importance over time.
Assuming you lose 70% of people after they follow that one URL pointer
they have to you (the one link in a slashdot article), it's an error to
push off too much content and audience interest until "page 2".
I think our current landing page design does a good job of putting all
the major "2nd steps" (features, screenshots, download, news) in
easy-to-access location, so I don't think it needs much more now. But
it does seem more like we've scaled back the level of coolness we might
be able to implement on the homepage for Preview, rather than the
current implementation does everything I'd want a root-level homepage to
do for us and the community.
All that said, though, it seems that we're not in disagreement for the
Preview scope for both of these things. We're just trying to pick a
page and get the current scope implemented.
I don't think it should remain in the Product Wiki as it is meant to be
a portal page for the entire wiki. Can it be chandlerproject.org/WikiHome?
Ah, that's probably part of the issue. Because, actually, that would be
great, but it's kind of a hassle to implement. Wiki pages need to live
inside a Wiki, so the page can't be /WikiHome, it needs to be
/SomeThing/WikiHome.
[Hmmm]
Well, I wrote a paragraph here about how this issue is hard and I'm
afraid we'll have to pick a area for now. Then I tried something out
and although it's a hack, it might be ok.
You can go to http://chandlerproject.org/WikiHome now and it shows you
the wiki home page. The page is still *actually* at
Product/ChandlerProjectHome, it's just you can view it at this other URL
/WikiHome. Edit links still go to the original, for instance.
That's probably the best I can do for now. The page itself does need to
be in a particular wiki, and I urge us to pick one of Product, Teams,
Notes, Developers wiki instead of creating a new top-level one. (Main
also exists in theory).
We have other pages in this same category; meta-pages without a home.
Knowing that even if we hide it with URL trickery it still has to be
*somewhere* (according to TWiki, sorry), which wiki area will be most
suitable? Product or Notes probably. (Where's the license go, btw?)
It seems odd that there's no appropriate place in our wiki taxonomy for
"meta" stuff or project stuff. Is that something we can correct?
Pushing them "up one level" is causing problems for me.
-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
