Posted 29 July 2012 - 06:28 PM
I'm in the process of writing a Content Management System (CMS) that can be "managed" from an accounting system (desktop program) the company I work for created/maintains.
I'm after some ideas of what to do/what not to do from past experience, also what features a CMS should have, I have been looking around at Joomla, Wordpress and Drupal and their themes/plugins/internal functions to get some inspiration and have a pretty long list already, but could always use some more giudence/input!
I have created an API that the CMS and desktop program interface with to exchange data, much similar to the Twitter API, but also took some idea's from Facebook. I have written a shopping cart that interfaces with the SecurePay API for credit card processing and the Australia Post API for calculating shipping costs. Obviously anyone using it for ecommerce will need a SSL certificate etc...
Has anyone ventured into this area before/have any suggestions how I could minimise the lost time "learning"?
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.