PHP and Smarty on Large-Scale Web Development

Do you have to deal with large projects on a daily basis and feel that you’re always behind schedule? Have you tried all the available frameworks and quit because they don’t really fit into your development methodology? Are you a Web designer tired of writing PHP code all day long?

PHP and Smarty on Large-Scale Web Development

PHP and Smarty on Large-Scale Web Development is a Short Cut Book from O’Reilly that I wrote along with Vitor Rodrigues. It’s a book for developers, engineering managers and Web designers. It shows you what a good choice using PHP and Smarty can be for Large Scale Web projects.

The book covers numerous topics related with Web development, template systems and performance solutions. Here’s a taste of the type of material you’ll find in the book:

The biggest advantage of the Template View Pattern is that it allows web designers to compose the content of the page simply by looking at the page structure. This means that you can efficiently split the tasks of development and web design within your team.

The approach described on the following pages is rather unconventional for applications using PHP and Smarty, but it is an excellent and elegant way of implementing the MVC pattern.

The Short Cut is currently available for download on the O’Reilly Web site.


7 thoughts on “PHP and Smarty on Large-Scale Web Development”

  1. Very, very interesting. I’ll definitely get it.

    Bruno, on the topic… have you ever worked with XSLT for templating a (whole) website? Do you have any idea whether it scales well or not?

  2. Good work guys. I’ve read it and it’s really good. The Short Cut is a great book for those (like me) doing stuff with PHP and Large Scale Applications.

    I’m using those techniques at and it has really been useful to use the Template View Pattern (with Smarty) to organize and schedule development.

  3. Parabéns,
    eu li, está porreiro.
    Não tive oportunidade de comentar, mas pareceu-me um muito bom trabalho.
    Um abraço.

  4. Thanks for the comments.

    André, regarding XSLT, I had some experiences using it but not for a whole website.

    XSLT is the exact opposite paradigm of the Template View Pattern: the Transform View Pattern.

    That means that it must render or “burn” any document before it is served to the browser. I’m not sure if it will scale, but you can of course deploy a cache layer on top of it.

  5. Oh I see what you mean.

    Since it can include a series of templates, I thought it was in the same family as smarty. Silly me. 🙂

    Maybe i’ll do a test case… the same document (huge table?) generated both by smarty and xslt and time the results. 🙂

    One obvious advantage on using transform with xslt is that the View stays platform independent. That’s why I’m curious to test it performance-wise. 🙂

    Thanks, you’ve given me stuff to think about.

Comments are closed.