> > > > Nice! Definitely good enough to replace the blog, don't you agree? > I like it! > > However, I would like to see the author at the top of every project/ > major title, and in the PDF version, the main page author is everyone > (my projects will be in there), intro's etc can have an authors name. > > Yeah that was also Joep suggestions. For this, I need to customize XSL-FO stylsheets for PDF output. I tried few things yesterday (see "Jallib Tutorials" on top of page, instead of "OpenTopic"), it may not be that hard.
> Also, I still wonder how others will add/update projects, such as > newbies or people that don't know how to use linux. > > DITA's not stuck to Linux, works on every platform with Java. > Should they post on the website? Should they post on the blog? > Will we have to modify every new example to fit in the book? > What do you mean by "every example" ? > > If someone new updates there example on the website, will it reflect > in the book? > > I'm guessing that if you can copy/paste it from DITA to the website, > you can copy/past from the website to DITA. > This is actually what I did, by copying from jalliblog and pasting in DITA (actually XLM editor Serna) > My suggestion is: > > 1. user uploads there project to the website > 2. we review it and format it so it works in the book and on the > website > 3. user updates the project and scripts auto update the book, allow > the user to see the result in the book? or should we review it every > time? (lots of work) > > same with the other way around, if you modify the "introduction" in > the book via dita, it should reflect on the website. > DITA is supposed to be the pristine source format (just the content, no presentation, no output). So going from the website to DITA, then to PDF isn't the proper way to go, and it may be very, very complex (HTML isn't as structured as DITA, some content in HTML may not fit in DITA elements). I tried HTML to DocBook converter, it produces dirty code (when they can produce it). The idea would be the other way: 1. create a DITA file for your tutorial, project, etc... 2. add your file to one or more ditamap (where you structure book's content) 3. publish your content Step 3. is fuzzy on purpose. What I see here is an automatic way to "push" content on the website (but it may not be that easy: how to transfer URL and navigation ? I need to think a little more, and test for real), and procude PDF files (books), included in releases, but also pushed on the website too. BUT........ before going further, we need to decide whether we go with DITA or not. There are some discussion by now about Open Office for instance. Do you prefer OO ? I'm not in favor of using it: master documents not as flexible as ditamap & content referencing, automatic build may be possible still no one has come the actual command line to do this (produce HTML and PDF from command line, on a server), and, most importantly, content is binary, so no diff and no merge by SVN will be possible, ie. we can't work on the same file at the same time. That said, there's nothing blocking in using OO, people may prefer using it, more than DITA (though I wonder how many have tried :)). Using DITA may keep users away from sharing their projects/tutorials. Keeping what you suggested, Matt, we could let users share through the website (thus, not integrated to books), and when things "deserve" to be in a book, then they'll have to go with DITA (like I did with my tutorials, it's not complicated I swear). Just like when people wants to share jal code to jallib, they have to embrace Jallib Style Guide. Let me know, I'd really appreciate if people could give their opinion. If you want, to clarify, I can post again a summary of what we need (according to me...), what solution can be used that fulfill more or less those needs, and then we can vote. If we go with DITA, I can write some documentation about how to use Serna editor, how to run compilation, etc... I can provide DITA templates to make your life easier, and I can start customize stylesheets (with the help of XSL Guru Joep of course...), and build script to publish contents. Until a decision, I'm continuing to enrich the tutorial book, just for fun, as a POC ! Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
