On Thu, Jun 28, 2012 at 10:53 AM, Tim Howe <th...@bendtel.net> wrote:
> On Thu, 28 Jun 2012 10:26:52 +0200
> Marc Espie <es...@nerim.net> wrote:
>
>> If you guys are serious about anything, go look at ports-readmes.
>>
>> It does extract information from the ports tree, and creates readmes for
>> all ports.
>>
>> Currently, it's a static port. It could very well be a dynamic
application.
>>
>> You can experiment with css, you can experiment with nginx.
>>
>> Preferably, don't add large dependencies (python or ruby out of the
question),
>> write it as a perl fcgi or something, you can use Plack or Catalyst or
>> whatever.
>>
>>
>> Or hey, at least tweak the templates to be nicer.
>
> Perl FTW. I think the site could easily be built with ttree.
> You will have easy to manage templates and content that anyone with
> some html knowledge can edit as easily as before; plus you will have
> static html output. Parts that should be templated can be in a
> flexible and easy to decipher/learn way. Little or no knowledge of
> Template::Toolkit would be required for most changes to be made.
>
> It's pretty easy to bootstrap with your existing layout and
> content. The build process could be managed with an easy make script.
> Template Toolkit is in the ports tree.
>
>
http://www.devshed.com/c/a/Perl/Building-a-Complete-Website-using-the-Templa
te-Toolkit/
from the page you referenced:
| Although HTML is simple, it does tend to be rather
| verbose. It's all too easy for the core content of
| the page to be obscured by the extra markup
| required around it
Then, the next link on that page takes you to:
http://www.devshed.com/c/a/Perl/Building-a-Complete-Website-using-the-Templat
e-Toolkit/1/
Yes, that *IS* much, /much/ better than the initial HTML.
--patrick
