I work in a company that uses legacy content management system based on PHP usage templates. I am fed up with it because it is extremely low for modern CMS (i.e., Drupal), especially due to the poor illusion of AJAX implementation capabilities and brunchy template trees. It is within my power to switch to a new CMS, as long as I have concrete logic to return it I decided to go to the people on this site because I mainly call it a sign.
Mike
I consider this legacy CMS a bespoke development? You can argue that the use of an established Open Source CMS is a better option due to the ongoing development and support - and generally speaking, whenever some bolt-on functionality is required, then there is a good chance that The functionality that has been developed to provide a plugin or module already.
So, my main argument will be support and development benefits.
Comments
Post a Comment