On 9/7/05, John Krystynak <[EMAIL PROTECTED]> wrote:
> In case you haven't seen it, Simon Cozens posted a nice set of example
> code and a very helpful 25 page PDF file explaining a lot about how
> Maypole works.  I found it very handy:
> 
> http://blog.simon-cozens.org/20050902-1.html
> 
> 

Cool. THanks.  I'm a little confused about something in the Static
pages section , p. 24 of the PDF.  He says "We don't want static pages
like the CSS processed through the whole Maypole system . . . "   What
exactly does he mean about CSS being processed through Maypole?  My
css is strictly in the HTML or so i think.

Also, I guess the strict definition of a static page is that there is
no concept of even a user.

cheers,


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users

Reply via email to