Andy Wardley wrote: > Sherwood Botsford wrote: >> So I'm sure there is a solution out there, probably a filter. > > There's Template::Plugin::Markdown if you want to go the whole hog: > > > http://lists.template-toolkit.org/pipermail/templates/2008-March/010095.html > > > Cheers > A >
Yeah, I use markdown currently. Markdown has link syntax that can work like this: [Highlighted link text][LABEL] then later in the file [LABEL]: [http://www.somedomain.com/appropriate.html] I've gotten burned twice now when I renamed an internal file and missed one of the other files that linked to it. I'm trying find a means to put the label resolution into a single sitewide file. So that when I change 30_Inventory.tt2 to Inventory.tt2 I don't have to chase every link on the place, but can change it once. (It was originally named that way so that it would appear in the right order in the menu. I have a better way now.) *** To Perrin I've looked at CMS, and I'm daunted. CMS is for sites with thousands and thousands of pages. I have 1 page per species, one page per genus, and a bunch of support pages. My page count probably won't get up above 200. My link count will increase a lot as I cross index the site. So far TT2+Markdown has been a win-win, except for this cross link problem. When Markdown doesn't find a reference for LABEL it just prints the line as if it were text. So I can probably write a post-process script fairly easily that does this. _______________________________________________ templates mailing list [email protected] http://mail.template-toolkit.org/mailman/listinfo/templates
