fantasai wrote:
Would you be interested in syncing formats with developer.mozilla.org?
Of course, that would be great. I still would like to keep the
sidebars, since they provide a great deal of functionality for
navigating the site.
Sure. I'd just like to get the markup cleaned up a bit. I'd also need to
know what styles you have on your reference that we might need to add to
the standard mozilla.org set. Ideally, I'd like to see the documentation
on mozref.com and developer.mozilla.org use the same format and style
sheets.
Agreed. Is there a requirement to have the styles between
developer.mozilla.org and mozilla.org 100% identical, or can there be
some maneuvering room to accomodate the kind of content that the
developer site will contain?
and you can help us set up a compatible back end for similar references
outside the AOM's scope.
Well, if I can get the sources for the Mozilla website as a whole, I'm
fairly certain a set of stylesheets can be made to render it
dynamically, with XSL, and still be fast.
www.mozilla.org doesn't have much XML-based documentation.
developer.mozilla.org will, but it runs under a different build system
than www.mozilla.org
Well, there was a long thread in the past as to what form
developer.mozilla.org should take, though, to be honest, I can't
remember all of what was discussed (or rather, so much was discussed,
that it seemed to form into a sort of white noise).
Are there any requirements, or even somewhat-hard ideas about what shape
that site will be?
AxKit is extremely quick at rendering pages, and with caching enabled it
runs at just slightly under the speed of static Apache requests. And if
not, AxKit could still be used to generate static pages to upload to the
mozilla.org website. The nice thing about going with a dynamic XSL website
is accessibility and i18n.
You'll have to explain about the accessibility. As for i18n, you can do
that with static files on Apache as well. I'm planning to set up Gerv's
localization scheme (with some fallback-to-English tweaks) for devmo.
Well, what I mainly meant about this was, if you have an XSL
rendering pipeline, you can choose one style or another, e.g. text-only,
full-blown graphics, printable styles, etc. And with i18n, you can
translate the XSL stylesheet content and website content separately, so
there is less work involved (theoretically).
So far we've only got Darin's XPCOM reference,
which is also written in XML. We're using a static build system, where
the XSLT transformation is performed once to convert pages from XML in
the source directory to wrapped HTML in the destination directory.
Okay. If I can get access to those stylesheets, then that could save
me some effort.
Easily done, but what exactly are you planning to do with them?
Well, since my site's content is rendered using XSL, if I can use the
same stylesheets that render the mozilla.org website, it would simplify
the process of bringing the XML content in-sync. Potentially...I'd have
to see.
It would also ensure that the HTML I produce is as close as possible to
what is rendered on mozilla.org (instead of reverse-engineering from the
generated HTML).
I think we'll probably want to stay static, but having the XML storage
format and the XSLT match seems like a good idea.
Is there any particular reason why you'd like to have the site remain
static? Is it for performance reasons?
I believe so. We'll have to check with Myk.
One advantage of the current system is that one can easily build the whole
site at home, without running a server. How would you handle that with
AxKit?
Usually just a recursive "wget", or render the site through a separate
stylesheet that produces either one large document, a PDF, or something
along those lines.
--
Michael A. Nachbaur <[EMAIL PROTECTED]>
http://nachbaur.com/pgpkey.asc
_______________________________________________
mozilla-documentation mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-documentation
