Use Asp.net 2.0 to build an enterprise portal platform (1. Design Philosophy)

This portal platform is named ecubeportal.
What is ecubeportal?
Ecubeportal is an enterprise-level portal platform similar to communityserver and dotnetnuke. In fact, it is more like SharePoint (features are not complex but flexible than SPS ). Compared with Cs and dnn, it has two major features:
1. More user-friendly URLs
CS and dnn use such a URL link, www.xxx.com/default.aspx? Tabindex = 1; www.xxx.com/default.aspx? Tabindex = 2;
On this platform, www.xxx.com/product/; www.xxx.com/service/
2. the modules on the platform use webpart, which is directly supported by. NET 2.0, unlike CS and dnn.
Other theme, skin, and security management systems are built on. NET 2.0, which is more flexible and convenient than CS and dnn.

I. Design Ideas
Let's assume a simple website requirement:
There is a company named ecube. To implement a simple company website, it should first include the company profile, product profile, service and support, and contact us in four major topics,
The company asked them to be able to customize the content of each page online, and said they would also want to add new topics (such as online recruitment) If possible, and hoped they could do it online.
We usually implement the following:
Without considering the customization requirements of the company, we create a new web project and then add four pages:
Default. aspx // company profile page
Product. aspx // product page
Service. aspx // service support page
Contac. aspx // contact us.

Then fill in the content of each page and link between pages. A simple company website is complete.
If you consider the customer's deep-seated needs, things may not be so simple, so we have Cs and dnn.
CS and dnn provide a good idea for us to solve similar problems.
In CS, the main sections and subsections of the website are stored in a centralized manner, and then the default. aspx? Tabid = 1;
They all implement a custom httpmodule that intercepts user requests and then assembles them into a page.

This is also the idea of my solution, but the part of the Assembly page is handed over to. Net webpart for implementation.
Use the internal mechanism of. NET 2.0 for theme, skin, and security management.

Next, let's implement a simple website to demonstrate the magical effect of urlrewrite.

Reference: http://erpcrm.cnblogs.com/articles/234246.html