I'm going to write a tender. The answer may well be a PHP based Content management systems. Later I may want to integrate an ASP.Internet framework making it seem like one site.
- What features will make this relatively simple.
- Would OpenId and other alike really make a difference?
- Within the PHP world Joomla should be more integrative than Druapal. Do you know the important variations here?
- Exist spesific frameworks in ASP.Internet, Python or Ruby which are more available to integration than the others?
I believe that many important factor is to find the right server. The server will need sufficient modules. Apache could be sensible choice because it supports all that you would like, including mod_aspnet (that we did not test, however, many people say it really works).
If you feel asp.internet integration is certanly likely to come, I'd choose Home windows as OS because it will certanly be simpler.
You might install reverse proxy that will choose which server to render content according to request - if user request aspx page, proxy will connect with the IIS and windoze page, whether it requests php it may connect with other server. The issue with this particular approach is shared memory &lifier condition, that could be solved with carefull design to aid this - like shared database holding all condition information and model data....
OpenID does not really make a difference - you will find libs for just about any framework you select.
The most crucial factor will probably be putting because the appearance-and-feel inside a format that may be shared by any platforms. Which means you need to create a standard group of CSS files and (X)HTML files which may be imported (or directly presented) in almost any of individuals platform options. Consider it as being writing an engaged library that may be loaded by different programs.
Using OpenID for authentication, if all your platform options support it, could be nice, but don't forget that every platform will require additional user metadata be saved for every user (preferences, last login, permissions/roles, etc) which you'll want to still need to wrangle together. OpenID only solves the authentication problem, not the authorization or preferences problems.
Lastly, since you will find a lot of options, I'd stay with mix-platform solutions. Which will make you probably the most options moving forward. There is no compelling advantage IMHO to presenting ASP.Internet if there is a chance you might eventually integrate along with other systems or proceed to another system.