Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Before you make any long-lasting decisions about how to structure the code for your site, I would recommend that you do some reading on the <a href="http://en.wikipedia.org/wiki/Model_view_controller" rel="nofollow noreferrer">Model-View-Controller</a> design pattern. While there are others this one appears to be gaining a great deal of ground in web development circles and certainly will be around for a while. You might want to take a look at some of the other design patterns suggested by Martin Fowler in his <a href="http://martinfowler.com/books.html#eaa" rel="nofollow noreferrer">Patterns of Enterprise Application Architecture</a> before making any final decisions about what sort of design will best fit your needs. </p> <p>Depending on the size and scope of your project, you may want to go with a ready-made framework for PHP like Zend Framework or PHP On Trax or you may decide to build your own solution. </p> <p>Specifically regarding the rendering of HTML content I would strongly recommend that you use some form of templating in order to keep your business logic separate from your display logic. I've found that this one simple rule in my development has saved me hours of work when one or the other needed to be changed. I've used http://www.smarty.net/">Smarty and I know that most of the frameworks out there either have a template system of their own or provide a plug-in architecture that allows you to use your own preferred method. As you look at possible solutions, I would recommend that you look for one that is capable of creating cached versions.</p> <p>Lastly, if you're concerned about speed on the back-end then I would highly recommend that you look at ways to minimize your calls your back-end data store (whether it be a database or just system files). Try to avoid loading and rendering too much content (say a large report stored in a table that contains hundreds of records) all at once. If possible look for ways to make the user interface load smaller bits of data at a time. And if you're specifically concerned about the actual load time of your html content and its CSS, Javascript or other dependencies I would recommend that you review <a href="http://developer.yahoo.com/performance/rules.html" rel="nofollow noreferrer">these suggestions</a> from the guys at Yahoo!.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload