Clever Geek Handbook

Using master pages with multiple objects

I am starting to plan a complete redesign of our department intranet pages. In any case, each department gets its own folder inside root. They all have the same look and feel but don't use CSS. Everything in every file is straight static text. Basically, if a change is to be made to the header, every file must be changed. The number of files is somewhere in the hundreds. As we are in the process of getting a new look, I figured this would be the right time to reorganize the structure as a whole. My idea was to create a new C # web project to use the main C # pages. In this project, each page will use the master page. Since I know they enjoy doing a lot of minor cosmetic changes, the master pages will make things much easier and frank.I don't have time to manually edit the title 564 (random) times. Another aspect of this site is that the root will contain a document folder in subfolders specific to each of our departments.

Guess my question is, did anyone solve a problem like this and could shed some light on how they fixed it.

Also, is it worth updating IIS and .NET to their latest version?

+1


source to share


3 answers


If you're already on .NET 2.0, you don't need to do any upgrades and there won't be any additional infrastructure costs.

I would highly recommend using master pages, as they make it painless to have a common look and feel for your entire site.



Another great thing about master pages is that you can merge them together . This will allow you to have a common feel between all the pages. And then each department will have its own page nested within your top-level page.

+2


source


I'll start with the question of cost. You must be using ASP.NET 2.0 or higher to use the master pages. The .NET platform is technically free, but Visual Studio is not. Visual Web Developer is free, but licensed only for non-commercial projects. I'm not sure. IIS is also free, Windows Server 2008 is not. You are working fine on XP or Server 2000/2003. There is really no reason to upgrade.



I can't say that I solved the problem in exactly the same way as yours, but it looks like you need a content management system. Some examples are: cuyahoga or Umbraco project . These systems allow you to create a common look and feel and store all content in a database or XML files and provide an online content editor, so the content of the pages can be driven by people who don't necessarily know HTML or Programming.

+1


source


You can have a master page hierarchy:

  • Master page for everyone
    • Main page of department A
    • Department B main page

Regardless of the common to all that you set on the first home page.

Then you create a master page for the department A pages - this master page of the master page.

+1


source






More articles:


All Articles