3
Good night,
And the next one I’m developing a big project and I’m almost done but now I’ve seen the need to separate the code for reasons of structure organization and greater performance because it’s a platform that will have a large volume of traffic in the future PHP of HTML how best to make this change in major changes to the platform ?
Uses an MVC Framework
– Rod
Any suggestions ?
– César Sousa
This question is a bit wide, it would be better to give more details than you need to do. For example, separating just because you’ve heard it’s good, is a "legend" (like almost any talk of "good practice"). If you have a real reason to do this, put your needs into the question and the problems you are having so we can help. As it stands, this question will probably attract votes to close.
– Bacco
There are several, go from your project and level of Exp in php
– Rod
I edited and improved the question
– César Sousa
I have not yet started to implement the functionality I asked because I need to know a principle where to start so I did not detail much put the essential
– César Sousa
Couldn’t you ask the question a reason at least? It would help a lot. Separating PHP from HTML doesn’t have much to do with traffic. Without more details, what you can say is "do in PHP the pages that have information that change dynamically, and in HTML the ones that have fixed information", but I think that’s not quite what you want. Anyway, let’s see if anything comes up to help you.
– Bacco