> Jared, any ideas on what the link should be? I know you wanted > something with a layer of indirection (i.e. a url that redirects > somewhere else...)
The indirection that I propose is an interstitial page on the server side; ie, add one page to the Cosmo distro, but no real content. The user clicks on the link. It takes them to a 1-pager hosted inside Cosmo. The one-pager in Cosmo says essentially "sorry there's nothing here yet. In the mean time, we have some fine on-line documentation available at the OSAF wiki, http://blahblah. On Wed, 2007-01-03 at 10:11 -0800, Bobby Rullo wrote: > Sufficient for now at the very least, but the URL should have a > version # in it, so that people can get help for the version of Cosmo > they have. This is a reasonable idea, until we don't need it anymore because the docs ship with Cosmo. In the mean time, the link itself would go locally, and the "link to OSAF wiki" inside that Cosmo page would direct to a new Projects/CosmoHelpZeroSix perhaps (probably with included sections from the actual pages we want on that help landing page). The reason the interstitial page makes sense from a software packaging perspective if that packages are supposed to be standalone, and essentially work on disconnected boxes. This is for off-the-network, internal-only, test environments, installing old versions, etc. But the help button should still do *something* useful. Serious implementers may want to replace the help documentation entirely. I think it helps them to have at least 1 local page to override as well, though overriding the URL sorta works for that use case too. -- Jared Rhine <[EMAIL PROTECTED]> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
