(Best practices) Where to place a store-specific common code?

[Alexander.X]

Hello everyone!

 

Not sure I placed topic into right thread, but it seems there are no better thread for questions about store development.. so, here it is

 

I develop a store with a lot of custom functionality.

And my question is Where I should place my store-specific code?

I'm not going to reuse this functionality or distribute it as a modules, so I need a good place for all little fragments of store-specific code.

 

Yes, I understand that in theory I should group code by the "what it does" and create a module for each group, but...

But usually each fragment is very simple and small and solves a separate task, so it would be a separate module for each 3 strings of code... I really dont think this is a best way

Now I just make an all-in-one module for backend, and another one for frontend, and hooks them to everyone I need... but when module became very large I began to suspect this is not a best way too

 

So the question is - what is the best way? How do you prefer to organize such code?

 

 

Thanks in advance!

Edited September 8, 2016 by Alexander.X (see edit history)

[rocky]

It's best practice to use the override directory for your store-specific modifications to PHP files and the themes/<your_theme>/modules directory for changes to module TPL files.

[Alexander.X]

Thanks for answer, rocky.