in reply to How to start making a database driven website with separation of content from style.

I personally wouldn't use XSLT for web-content. I'd look at CGI::Application, Class::DBI, and Template Toolkit. Everything you could ever want to do in a web-application-with-database can be done with those three modules.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re: How to start making a database driven website with separation of content from style.

Replies are listed 'Best First'.
Re^2: How to start making a database driven website with separation of content from style.
by Thilosophy (Curate) on Dec 03, 2004 at 02:32 UTC
    Exactly. XSLT is just going to eat up a lot of your development time and makes things more complex than they need to be. Using something like CGI::Application (and HTML::Template if you do not like the Template Toolkit) will bring you results very quickly, while still producing maintainable applications with data management, logic and presentation cleanly separated.

    One thing you should not forget in the mix is CSS. You can greatly simplify your HTML output by putting all the styling into CSS. If you were looking at XSLT you should not have trouble to get the concepts here.

      The idea for using XSLT was that, if all the data of my thesis were stored in XML, then I could easily transform it into HTML pages or a .pdf/.ps/.doc/... document.

      But maybe that's indeed overkill.