2008/3/5, Gerard Beekmans <[EMAIL PROTECTED]>: > Jeremy relayed an idea in one of his emails that I brought up again. > Maybe you didn't see it, or maybe it just doesn't apply to the question > you posted. In which case, can you clarify what you are after as I must > have misunderstood.
I am after the need to identify what pieces of information need to constitute the output. The input of the dynamic website is currently defined better than the output. > A few years ago we had an idea that creates custom books for people > on-the-fly. The idea behind it being you end up with a book that is > tailored to your needs. Somewhere on the website you select from a list > of pre-defined modules if you will. The answers to those questions (ie: > do you want to add a Package Manager) would result in a book with > additional instructions (ie a bash RPM patch if you chose RPM, or a > other-package DPKG patch) or potentially instructions removed. Yes, that's right. However, the idea never went behind "we have to generate the content dynamically", and nobody provided even a single page of the modified book. So it looks a bit abstract to me. > This idea didn't come to fruition mostly due to server resource > limitations. That problem shouldn't exist anymore nowadays. Here I am not sure whether I agree about the reason, but this disagreement is off-topic for this thread. I want the idea to be clarified by providing samples how the generated content should look like, in terms of HTML layout. Such samples would help us classify the replaceable/optional items and thus avoid redesigning the generator more times than it is needed. > If at the end of the day the current DocBook setup can no longer deliver > what we need, and nobody can find a way to make it work, then we'll have > to do what it takes to get the job done. Staying with > DocBook/XML/whatever is never a requirement. We'll use what we need to. Yes, investigating the possibilities is the subject of this thread. But, unlike your previous thread, we have a constraint on the output here: it is HTML. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
