Stuart Rackham <[email protected]> writes: > Phillip Lord wrote: >> Stuart Rackham <[email protected]> writes: >> Yep, that's it. In my case, I pretty much always use blogpost with the >> "post" command, then let attributes sort everything else out. For me, >> this works superbly. > > OK, I've come up with a general approach to AsciiDoc attributes that I hope > fits the bill: > > - Blogpost always scans AsciiDoc source files for the following blog > parameters: categories, status, title, doctype, posttype. > > - The parameters are entered as AsciiDoc attribute entries. The parameter name > prefixed with 'blogpost-' forms the corresponding attribute name e.g. > > :blogpost-status: published > :blogpost-categories: blogpost,AsciiDoc,Weblog client,WordPress > > - An --attributes=ATTRIBUTES option can be used to enforce selected AsciiDoc > attribute entries. ATTRIBUTES is a comma-separated list of parameter names > e.g. > > --attributes=status,categories > > - Parameter precedence is (from highest to lowest): > > 1. Command-line options. > 2. AsciiDoc attribute entries. > 3. Blogpost cache.
Stuart This sounds very sensible; I hadn't thought about included posttype in the attributes (currently I do this by having different directories and two makefiles, with different command lines). But this will allow arbitrary growth of attributes if new things (such as tags) come along without a massive bloat in the command line. I should also be able to port all my existing blogpost source without any problems, which is a nice side effect. I'll try the patch out as soon as possible and get back to you! Many thanks. Phil -- You received this message because you are subscribed to the Google Groups "asciidoc" 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/asciidoc?hl=en.
