Website Architectures

[Bingo]

I wanted to get some feedback from people who write web applications. I am always working on projects on my own and I am constantly looking for better ways to organize my code. I was hoping to get some new ideas because I always fall back into the same pattern or just improve on my current system.


My basic architecture consists of an index.php file that defines a table to contain a top, middle, and bottom section of the page, and then a left, center, and right section. The contents of each section are defined in separate php or html files. It's very simple, but it seems to work more-or-less. I usually use session variables to transfer data between pages.



Pros : Quick to write, easy to debug, easy to understand, expandable, flexible
:sad: Cons: Conflicting variable names, somewhat difficult to process forms, difficult to transfer data - no main resource, constantly re-writing same code for different pages.

Please comment and post your ideas!

 

[poringy]

There are many people that write php with a system like CakePHP or Code Igniter. Try searching up on those; they make code writing for php far more efficient and easier.