Hi, I read the separate DB thread. I have been through a few videos for DNN from traincert. Just learning this but about to build on it ( I think), so I have an important question about the portal usage.  I have an application that will be used Internationally, in multiple languages. There will be a signficant resource library that will be built over time by the users of the site.  This resource library is germain to the applications purpose and reason for being.

I had hoped to be able to skin different looks over the entire site, including the company logo at the top, based on who logged on to the system.  Also, the site must have the ability to change languages.

My question is, Is this seem possible to do with the DNN framework and does this scenario seem like an OK usage of DNN from a single site, multiple portal, single database configuration. 

I may be confused about portal... but I hope I have asked this well enough for someone to answer and thank you. Michael Moore - St Paul Minnesota

Sebastian.. thanks for answering this.

This site will have a generic login page with no company or corporate signature. What happens in the two scenarios, I describe below, is based on who logs in to the site.

Scenario 1: This site will have a default site which is provides services to some clients in several languages. The theme of the site, after login, i.e. logos and CSS styling, will be a default theme that is based on my company's theme.

Scenario 2:  this site will proved services to, say a single US corporation. This corporation will be providing this sites services to their clients (their employess) and this will also be in several languages.  This second scenario would need to have the capability of re-theming the site (logo and CSS styling),  on the fly, after logon, based on who logged in.

Both scenarios used the generic single logon page.   I would very much like to use single database and a single membership scheme. All content (for the most part) will be shared and the same.

Is this possible?  I know this may be too difficult to answer here but do you know of the BEST resource to find those special configuration / component issues? 
I have watched 16 videos since yesterday afternoon. I am going to the bookstore shortly. 

Thanks again

S.L.

By multi-lingual, I am referring to using ASP.NET best practices for localization. I thought I have seen that this functionality is built in to the DNN system. By built in, I mean, that localization is one of the DNN features that is made easier to configure, and implement.  But still based on the .NET localization standards.

As far as the Skins go, I am asking if a single DNN implementation can be configured to dynamically apply a different skin after checking WHO the user is. This would require a check against the database as to what company this user belongs to and grabbing the skin for that company (also from the database) and applying a specific skin for this particular company.

For instance: Jon Doe logs in, a check is made against the database, to find the company that Jon works for. After determining the company, a specific skin, is applied to the site.  By SKIN,  I am referring to things like swapping the header graphics, color scheme etc. but most content is common for all users.

Is this clearer?  I appreciate your feedback.

M.M.