Michael A Nachbaur wrote:
fantasai wrote:
Ok. You might want to contact the domref authors to see if you can just lift off content from those pages. And talk to Doron, he has some DOM reference documentation in the works.
Okay, I'll do that. It would definitely save me a lot of time, but I was looking to avoid muddying up the copyright licensing. You wouldn't happen to know what the license is on the DOM reference documentation on mozilla.org, would you? The reason I ask is there's a possibility I might be writing a book on Mozilla at some point, and I'd like to include the object reference with that.
Like I said, contact the authors, and talk to Doron, too. I have no idea what the copyrights are, but I know that the authors would welcome any efforts to update and expand Mozilla's documentation. As for writing a book, unless you plan to include the reference as an appendix or something, you should be clear on that. If you do, well, hey, you'll just have to give someone else a cut of the credit. I doubt the DOM reference authors would want their text /not/ to be published. But you really should coordinate your work with what's already being done.
I'm interested in the back end you're using to generate your site. What format is the reference in, and where does the HTML design come from?
The format of the XML files is custom, mainly to make editing of the content as easy as possible. I also have a series of scripts that analyze the documentation tree to notify me of broken references, incomplete sections, etc.
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.
Additionally, I'm looking to add tutorials, howtos, etc. By putting that content in the site, any tutorial that mentions an object will automatically have cross-reference links inserted to the relevant section of the object reference.
This would be useful on DevMo as well, so I'd like to talk about how to get it to work cross-site.
I can help you bring your HTML in line with the mozilla.org style guide
Great, if you can point me at / send me the styleguide and stylesheets, I can convert mozref.com over.
See http://www.mozilla.org/contribute/writing/ mozilla.org's style sheets are at http://mozilla.org/css/
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
> 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.
There's already a lot of high-load websites out there running under AxKit, gentoo.org and opera.com being two of the most notable ones.
Ok, cool. I'm at Opera right now, I think Fredrik was telling me about AxKit awhile ago.
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?
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?
~fantasai
-- http://fantasai.inkedblade.net/contact _______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
