Max Headroom
Active Member
- Joined
- Nov 16, 2010
- Messages
- 63
- Reaction score
- 0
Take the middle line. Use both:
I work with Drupal, which thinks of itself as a web frame work, not a CMS. You use a web frame work to build a CMS, or any other application that is needed to your needs. Drupal is not a cookie cutter CMS.
I say middle line, that is have an application (like Drupal, and WP and Joomla to a point) and try and use as much as possible the ad-dons or modules that can do different things for you that you need out the box, such as user control.
Not knowing what your job is about, you can also use an e-commerce ad-don, which will already take care of the basic stuff like invoices and orders, etc
Then, with PHP, create your own custom code or modules specific for your needs. Such as your payment gateway.
Two golden rules for a developer (that you can check on):
NEVER change core code. Updating core and ad-on modules should not break the site.
Strictly follow the coding and API standards of the platform you build on.
Custom modules that are built properly must be able to be installed on any installation without any problems, and be under version control. And it can stay proprietary, despite what the open source license say. You not distributing or selling the code.
I work with Drupal, which thinks of itself as a web frame work, not a CMS. You use a web frame work to build a CMS, or any other application that is needed to your needs. Drupal is not a cookie cutter CMS.
I say middle line, that is have an application (like Drupal, and WP and Joomla to a point) and try and use as much as possible the ad-dons or modules that can do different things for you that you need out the box, such as user control.
Not knowing what your job is about, you can also use an e-commerce ad-don, which will already take care of the basic stuff like invoices and orders, etc
Then, with PHP, create your own custom code or modules specific for your needs. Such as your payment gateway.
Two golden rules for a developer (that you can check on):
NEVER change core code. Updating core and ad-on modules should not break the site.
Strictly follow the coding and API standards of the platform you build on.
Custom modules that are built properly must be able to be installed on any installation without any problems, and be under version control. And it can stay proprietary, despite what the open source license say. You not distributing or selling the code.