How To Make Two Websites Look Like One - Which Features Are Important?
I'm going to write a tender. The solution can be based on PHP CMS. Later, I could integrate the ASP.NET framework and make it look like a single site.
- What features will make it relatively easy.
- Will OpenId and the like matter?
- In the PHP world, Joomla needs to be more integrative than Druapal. What are the important differences here?
- Are there special frameworks in ASP.NET, Python, or Ruby that are more open to integration than others?
a source to share
The most important thing is to give most of the look and feel in a format that can be used by all platforms. This means that you should develop a standard set of CSS and (X) HTML files that can be imported (or presented directly) in any of these platform options. Think about it by writing a dynamic library that can be loaded by various programs.
Using OpenID for authentication, if all the platform options you support are supported, would be nice, but remember that each platform requires additional user metadata (preferences, last login, permissions / roles, etc.) to be stored for each user. ) that you still have to argue between them. OpenID solves the authentication problem, not the authorization or preference problems.
Finally, since there are so many options, I would stick with cross platform solutions. This will give you more options in the future. There is no compelling IMHO advantage to using ASP.NET if there is a chance you may one day be able to integrate with other systems or migrate to another system.
a source to share
I think the most important thing is to choose the right server. The server must have the appropriate modules. Apache would be a good choice as it supports everything you want, including mod_aspnet (which I haven't tested, but many say it works).
If you think the asp.net integration will be complete, I would choose Windows as the OS as it will be quite simplistic.
You can also set up a reverse proxy that would determine which server should display content based on the request - if the user requests an aspx page, the proxy will connect to the IIS page and windoze, if it asks for php, it can connect to another server ... The problem with this approach is shared memory and state, which can be addressed through careful design to maintain this - like a common database containing all the state and data information of a model ....
OpenID doesn't matter - there are leaks for whatever structure you choose.
a source to share