Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/http.php on line 61

Strict Standards: Declaration of GA_Admin::checkbox() should be compatible with Yoast_Plugin_Admin::checkbox($id, $label) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 27

Strict Standards: Declaration of GA_Admin::textinput() should be compatible with Yoast_Plugin_Admin::textinput($id, $label) in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 27

Strict Standards: Non-static method WP_Http_ExtHTTP::test() should not be called statically, assuming $this from incompatible context in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/http.php on line 94

Strict Standards: Non-static method WP_Http_Curl::test() should not be called statically, assuming $this from incompatible context in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/http.php on line 97

Strict Standards: Non-static method WP_Http_ExtHTTP::test() should not be called statically, assuming $this from incompatible context in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/http.php on line 142

Strict Standards: Non-static method WP_Http_Streams::test() should not be called statically, assuming $this from incompatible context in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/http.php on line 145

Strict Standards: Non-static method WP_Http::processHeaders() should not be called statically, assuming $this from incompatible context in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/http.php on line 1038
Setting up as A self employed Web Designer » CMS is the way to go

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 55

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/functions.php on line 55
    February 08th, 2011
  • Uncategorized
  • admin

I’ve spent the last couple of years working on all sorts of web projects, from portfolio sites for architects to full online webstores for Debenhams and BHS among others. But what has really been keeping me busy for the past few months is designing CMS (Content Managed Systems); a CMS is a website which through a combination of server code and a database enable anybody to create content., add new pages, edit existing ones through your web browser. This is brilliant as it means that you don’t need to contact your local friendly web designer every time you want some changes made.

There are a number of CMS frameworks, the most popular is Wordpress, which although originally developed as a blogging system has now been successfully used to create thousands of fully functioning websites. However, I have been using Joomla! for all my web projects. Although not perfect at all it is a wonderful system. Whenever I come up against a limitation I find that somebody has already created a plug-in that does exactly what I want. Many CMS websites look very similar and regimented, however if you have the time and the know how you can develop some very design heavy websites in Joomla! For example:

www.mcmurdoltd.com

www.kannadmarine.com

www.kannadaviation.com


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/14/d376328215/htdocs/mupe_site_only/blog/wp-includes/plugin.php on line 339