* John Plocher <[EMAIL PROTECTED]> [2007-12-23 00:56]:
> I am painfully aware that this seems to have been inspired by the same
> people that work in Georgw W's CIA, but I can do nothing about it. The
> nav bar is auto-generated by the web app and, AFAICT, I (as a community
> editor) have no control over how it works.
>
> The app creates links to each and every sub-page, arc-material and
> attachment in a community, even though 99% aren't even shown because
> they have (style=display:hidden).
>
> There was some discussion a long time ago about changing things such
> that it could be turned off on a per-community basis, but there haven't
> been enough resources to do the work.
Anything to do with the main content application is tied up in getting
rid of it. Luckily, there are a few ways around the content
application:
1. Projects can create source code repositories today, which become
available as static files at
http://opensolaris.org/sc/src/[project]/[repo]
(in addition to their hg/svn access methods). It would be easy to
create and maintain a tree of content this way.
2. Individuals can use cr.opensolaris.org in a similar fashion, using
rsync. I think this might be useful for CGs and projects, but
that will require a little SSH key coordination.
3. In special cases--code review, defect tracking, and testing
services being current examples--we can provision a zone so that
some custom work can be done. We'd like to keep the services and
software on such zones tracked closely, and would like to keep to
a relatively common set of software, but are open to input. An
ARC zone easily qualifies for this treatment, I think.
(The navigation is 1MB because of all of the case pages, I presume?)
- Stephen
--
[EMAIL PROTECTED] http://blogs.sun.com/sch/
_______________________________________________
website-discuss mailing list
[email protected]
