Writing a site engine
Written 29 Sep 2004
<p>At <a href="http://www.devshed.com">DevShed</a> you can find many articles about all spects of development, especially web development. Recently they published a series of articles on <a href="http://www.devshed.com/c/a/PHP/Building-a-Site-Engine-with-PHP-1/"> building a site engine</a>. The five articles do a nice job of walking a person through many of the basics, with some reasons here and there why some choices are made. Some concepts and choices are a little vauge, but should not prove a stumbling block to a person learning.</p>
<p>As an example of vagueness, he speaks of plugins and modules, with modules depending upon plugins (really, looking deeper into the design, modules provide the "visible" aspects of plugins). The vague part is that in software plugins and modules are quite often the same: something added to the core providing new functionality. Additionally, both words most often refer to:</p>
<ul>
<li>Being exchangeable</li>
<li>Not needed for application use</li>
</ul>
<p>It does not seem such is explained in the articles.</p>