Static can be more

water drop

Jozef Kutej

Agenda

:-?

1. theory

1.1. static pages?

1.2. dynamic pages?

2. examples + practical solutions

2.1. http://ba.pm.org/

2.2. Makefile + inotify

2.3. Template::Toolkit

2.4. xml+xslt => .tt2 & .rdf

2.5. SVN for RC and deployment

2.6. store + planet + testing + minification + ...

I hope that there will be something new for everyone and you'll enjoy it, or ...

or ...

attention

let's start

Static pages

WYBIWYG

Dynamic pages

Server side static pages

Static Pages/Content

advantages

Static pages

disadvantages

server side Scripting/Programming

advantages

server side Scripting/Programming

disadvantages

Laziness

<?
Include "./_conf.php";
Include "./_head.php";
?>

<h1>Welcome to my page.</h1>
<p>For an idea that does not at first seem insane,
there is no hope.</p>

<?
Include "./_tail.php";
?>

Compromise

-KOMPROMIS (2005 LP)-
-KOMPROMIS (2005 LP)-

the practical part

BA.pm.org
https://cle.sk/repos/pub/www/tt-pm/
http://www.ohloh.net/p/bratislava-pm-org

BA.pm.org features

BA.pm.org more features

it's better to see once
then to hear 100 times

for the curious

visitors

TMB score

Tick My Boxes book cover
72 out of 100

HOW?

Makefile + inotify

Template::Toolkit

ttree

_cfg.tt2,
_wrapper.tt2,
_header.tt2,
_footer.tt2,

redirect.tt2

events.xml + events-to-(html|rdf).xslt

who.xml + who-to-(html|js).xslt

i18n

send-feedback.cgi

nginx.conf

SVN notify + deploy hooks

the rest

Questions?

:-?

That's it

Thank you!

:-)