On Thu, Jan 19, 2012 at 6:53 AM, Seth Johnson <[email protected]> wrote: > On Thu, Jan 19, 2012 at 6:30 AM, HansBKK <[email protected]> wrote: >> I'm not clear about just how generally the term "templating" applies to all >> non-coding use cases. >> >> From my experience with HTML, it would refer to the repetitive "site chrome" >> elements wrapping around the variable content. >> >> However say I'm using Leo to manage a large amount of content for a given >> topic domain, like an encyclopedia. A relatively small proportion of the >> content needs to be output in more than one place, e.g. an article on the >> Bangladeshi spotted deer should be available both in the "D" and the "B" >> volumes. >> >> Is that templating? > > > For an encyclopedia where articles are to be placed in more than one > external file (approximately one file per letter of the alphabet), the > model would be to put all articles for all volumes into one big > @file-managed external file, and then make each volume of the > encyclopedia a @template-produced external file.
And there's no reason you couldn't have several @file-managed "article source" files, if one is too big. The @template-produced encyclopedia volumes are created from cloned pieces of the @file-managed files. Seth -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
