Recommendations to Separate the Website Parts Into Their Own

[Glese]

I have built a website where everything comes together one can think of regarding building sites for the internet and now I would like to separate the functionalities into their own so I can use them again in the next projects.

 

Be it the commenting, favoriting, rating, profile, sign in, sign up system and et cetera - I simply want all systems to be separated for later re-use.

 

I am wondering what would be the best way to approach this? Any recommendations?

 

I did consider to use neutral and abstractive terminology when coding the scripts so it is not specific to the current project.

[scootstah]

I would build a mini framework and use a modules system. Each thing (commenting, favoriting, rating...) would be its own module and completely independent of one-another. This way you can just drop in whatever module you want and you're good to go.

[Glese]

I am having troubles to imagine that.

 

I am using the MVC model, and as you can tell it is a bit spread across. Do you have any example showcasing your suggestion?

[scootstah]

Look at the HMVC pattern.

[ignace]

re-usable as in php code? or as in the entire thing (images, css, js, ..)? The first scenario means a strong abstraction. The second implies the use of modules (or mini-app):

 

module1

- css

- js

- img

- something.php

- manifest.xml

module2

- css

- js

- img

- something.php

- manifest.xml

[Glese]

I think the HMVC model seems to be a well solution, once the development has finished, simply consider moving the whole folder into the new projects.