Friday, 30 October 2009

CMS name suggestions

As I have said previously, I am currently creating a CMS, however as of yet I have no name for the CMS. I am looking for suggestions for the name of the new CMS. All suggestions welcome.

Thursday, 29 October 2009

I am very happy with my decision to go ahead and create the cms before the forum itself so far. One big reason for this is that it will make it much quicker and easier to handle the social network versions of the forum because they can just be new pages with different templates on them.
Although I could have quite done this easily using templates in Django, being able to decide what modules to use via an admin interface will make changes and updates much easier. Especially when I make introduce the ability for people to host their own forums. Obviously this affects the way that I develop the forum so that functionality is broken into individual modules as is practical to allow customisation.
This approach also allows for more customisations, such as having different menu modules that people can use for their forums etc.

Tuesday, 20 October 2009

to CMS or not to CMS

After weeks of searching for a platform that did everything I wanted and worked on appengine I have decided that maybe I should go ahead and create it myself. My intention with the forum was always to create a CMS at a later date and make the forum available as a module within that CMS.

This would have required alot of work at a later date because the best platform I could find for appengine was python and I wanted to do the CMS in Java. This would have required porting the forum to java, or at least a language running on Java at a later date. Not something I was looking forward to, so I have decided to create enough of the CMS to integrate the forum with it and take care of the templating and url routing for me that were annoying me with the servlet approach to website development with Java.

The initial work on the CMS is going to be based off my experience with DotNetNuke as I like the flexibility of DotNetNuke even if they underlying code leaves a little to be desired at times. Although I will be using a similar tabs/modules approach with the CMS the underlying workings will be quite different as I will be attempting to create a templating engine that is easy for designers to use by keeping to the MVC architecture and leaving all Java code out of the templates. This has an added advantage of keeping the template logic separate enough to allow for modules to be written in different languages without confusing things by having to Java for the views.

This whole process is proving to be quite a headache though as I try to figure out all the details for the CMS implementation and deciding what to build and when. I have never attempted a project even close to this size and complexity before so it will be quite the journey I am sure, and hopefully I will be much the wiser for the experience once this is all over.