Site Design (Rokodo)

Backend: What I see as site admin when updating the site.
Frontend: What the user sees when they are browsing the site.

I attained some space on my friend's server so I could practice with the implementation of a website via the TYPOlight open source Content Management System (CMS). I will spare you the details and revelations of the horror of implementing the drop-down menu. Essentially I modified the default template including modifying some of the Cascading Style Sheet (CSS) of the default template to suit my needs, as well as creating new graphics. You can view the website here for now, until the domain changes which is highly likely to happen at some point in the future. (Note that some things are likely to be broken in terms of page design, because for some reason after the daily site maintainance I noticed it had ruined my hard work of positioning the navbar.) The beauty of using a CMS is you can update pages and change site structure via the backend with relative ease, without having to constantly maintain individual pages and uploading them manually. The site's theme can be modified and instantly applied across all the pages of the site by modifying a CSS file and uploading that, as opposed to downloading each individual page and changing each one manually. This is the reason why most reputable companies use a website with a CMS along with CSS controlled themes. Information is easier to track, design changes can be implemented across hundreds or even thousands of pages with ease, and one does not have to worry about inconsistencies in page design.

Ciao.
Rokodo