Tuesday, December 06, 2005

Content Management System - Architecture

It is of general design philosophy to go from vagueness to detail. Vagueness may seem as a shortcomming, but the insight the overall picture gives is worth it. Hence, to design the system that I wanted, I came up with a very basic picture of what I wanted.

CMS Overall Architecture

As can be seen in the picture, it is basic, but that is the purpose of it. I plan to use server side scripting to get the content from the database, and the layout and design using CSS, and present it as webpage. For server side scripting, I plan to use PHP. I do not have PHP knowledge, but I plan to learn it incourse of this project. For that matter of fact, I do not know CSS that well either, and I plan to learn this too.

So, before even we think of coding anything, we need to know how the content and layout-design would be. The layout design should not be much of a problem, since that is the essense of using CSS. As of content, we do not need the content yet, but we should have a fair idea of how the content is stored. The content would be dynamic, and the only prior knowledge that is required is to know how it would be structured.

Man, this blog is turning out to be some sort of info site. Good going. Am following CSS.
add another to following the CSS list... :-)
hey vyoma, that seems to be very technical, typical of you. After doing a AIP's job for the past 14 months or so, I have somehow, lost touch with the technical side of things. So dont have much to say abt the Content Mnagement System. heard abt this for the first time from ur blog. Good going.
Post a Comment

Subscribe to Post Comments [Atom]

Links to this post:

Create a Link

<< Home

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]