Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP best design practices
    primarykey
    data
    text
    <p>Ok, have a bunch of questions that I have been thinking about the past few days. Currently I have a site that is just a bunch of PHP files with MySQL statements mixed in with PHP, HTML and CSS, basically a huge mess. I have been tasked with cleaning up the site and have made for myself, the following requirements:</p> <ul> <li>The site needs to be efficient and well laid out (the source code), I would like to be able to write as little code as possible.</li> <li>There has to be good separation between structure, presentation and logic.</li> <li>For whatever reason, I can't use a framework and need to keep the code maintainable and "simple" as there will be future developers working with it.</li> <li>There needs to be an admin section for at least a few pages.</li> </ul> <p>Saying that, this is what I know about the site as it is now:</p> <ul> <li>Consists of 10-12 pages, a few are completely static, most are dynamically driven via a database and there is a huge form for users to fill out (20-30 fields) that need to be validated and checked.</li> <li>The hierarchy of the site is basically 5-6 main pages and then sub-pages within those.</li> </ul> <p>So, knowing those things I wanted to know if anyone had any tips/suggestions as to how to go about doing this with the least amount of headaches. </p> <ul> <li>Would an OO approach be best in this situation?</li> <li>Since there are many static pages and the dynamic pages just need the content filled in would it be best to use some kind of basic template?</li> </ul> <p><strong>EDIT:</strong> Thanks for the answers, when I said no frameworks I basically meant anything that would require new syntax other than PHP, as whoever gets hired to work on this site after me will probably only know PHP.</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.
 

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