The other option is to use UserControls to create the framework and then have standard server controls for the rest. That is what I use in my company quite often. What that buys you is the ability to not only include the same content in various pages, but you can create events and properties on the controls so you can do things like highlight new or updated sections through code. You can also take the concept of searching and filtering across pages.
I have implemented a search of data using a UserControl instead of creating a Custom WebControl. Encapsulating functionality like the class tree would not be too tough either, cause once you create the user control, you use a property to pass the correct XML DOM and the control iterates through the tree creating the nodes and links.
So a revision of the go-mono.com site can be done with everything that is available, the question is how far do you want to take it.
---------------------------------------------------------------------------
Message: 7
Subject: Re: [Mono-list] Updating or Redoing go-mono.net
From: Miguel de Icaza <[EMAIL PROTECTED]>
To: Ben Maurer <[EMAIL PROTECTED]>
Cc: Aaron Weber <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Date: Sat, 10 Jan 2004 01:14:39 -0500
Hello,
> One of the issues is that v1, asp.net does not have alot of the things
> we need (MasterPages is the biggest example). Once we get to v2 stuff,
> doing the site would be much easier.
>
> OTOH, by the time we 1.0, we *really* want to be dogfooding on the
> homepage.
Well, we can always use the ASP.NET include directive to get 99% of the MasterPage features ;-)
Miguel.
