Want to develop in house CMS

If this is a fresh project, I would suggest you actually take some time to obtain a clear set of requirements.

Ask the team/client (or yourself) what it needs to do and I would suggest writing a functional spec, will make things easier in the long run.

Once you have that, you could look at producing a technical spec.

Start writing.

Your question in itself is too broad to give an accurate answer in my opinion. If you don't want to spec it (not good) and just code it, then perhaps look at one of the Patterns and practices examples from Microsoft. However, without a spec, it will probably take 3 times as long as you will jump around a lot.

I agree with officedoc.
First, write requirements. After, code it.
In terms of coding, since I have written a inhouse CMS when ASP 3.0 was the bizz knezz, and I have used the following approach:
- Created an application to manage the metadata of the CMS: which are the different type of content (news, agenda, quizz, ...), their fields, their relationships, etc... All this metadata will generate the tables itself and the pages to insert/update/list/delete content on those tables;
- Created a base web application that will receive the generated files. This base application will contain the images, basic javascript, etc.. that will be used by the generated files.

Hi Both,

Thanks a lot for your responses, I think I already know something about my users requirement. I need to write functional specification though. But all i have to do is to convert
http://www.nhsstockport.nhs.uk to a CMS site to a CMS site.
The first module would be to develop something which should enable users to customise the main page, the example of the main page can be http://www.newcastlepct.nhs.uk/ .

@wpcortes:
Can you please guide me about creating meta data applications? is it a relational database in sql server? are there any tutorials available on the internet or would you recommend some book(s)?  

I am sorry if my questions don't make sence but I assume most people will suffer in the start.

best regards

Yes, the metadata could be stored in a relational SQL Server.
Now, I dont think that you are going to find books around metadata. Not specifically for this application.