What is a best approach to develop the large content asp.net pages portal

Question

Hi,

What is the best approach to develop a static content portal which has almost 200-300 static content asp.net 2.0 pages with CMS.

 Option 1: Simple option traditional way of building:

• Create 1 or 2 master pages for themes & styles.
• Create 200-300 asp.net individual static pages
  
• No db involved
• If CMS and Multi-lingual are enabled, how does this option fit into?
  

Option 2:  Virtual pages:

• Create 1 or 2 master pages for homepage and sub-sequent pages
• Create 1 dynamic page in asp.net to hold the 200-300 static content from the database
  
• Store the content in database
• page url looks like: ../contentpage.aspx?contentid=168
• If CMS and Multi-lingual are enabled, how does this option fit into?

 Option 3: Use Windows Sharepoint Services (WSS 3)

• Does WSS 3 have the capability of multi-lingual support? 
  

 

Which option do you think is the best? Is there a better approach? Please advise.

Thanks.
Shaf