📜 ⬆️ ⬇️

The idea for the project - UMS.

head

At the moment there are many different, very interesting and promising CMS-ok, forum engines, frameworks, etc.

On Drupal, you can easily organize a socially moderated community with multi-blogging elements. Wordpress is good for personal blogging. Easy-to-learn Joomla with a lot of third-party modules allows you to make decent sites, sharpened by the "corporate" requirements. ModX is ideal for SEO-oriented small sites, and its concept involves rapid development. Boonex Dolphin is good as a community portal, a dating site and a person search according to certain criteria. The SMF forum is not bad in conjunction with Joomla, Phpbb - “there are no words - only emotions” ... And on Vanilla, you can do a full website with light extensibility and the presence of your own framework, about MediaWiki - what can we say ...
')
One problem only. How to tie all this together in any big project?

/ head

body

At the moment, when trying to use multiple CMS in one project, the question of their mutual integration immediately arises, especially for a single user base in one project.

Below is the simplest option, 3 elements:



Single arrows imply user-date movement. Double arrow - "module" of integration.

In general, another round-trip ... The user-date cycle can be provided - the user can log in to the drupal, which is already transmitted by the user-date to Jumla (for example, for comments) and the forum. But already there are questions about ongoing support, compatibility issues when changing (updating) individual cms - elements of the system.

An example with 5 elements:



Drupal, let's say, we use for social blogging and kamtinging, WordPress for a personal blog of a manager who is not very keen on computer issues or his secretary, Jumla using SOBI2 and Virtumart - as a catalog and store, ModIx as displaying SEO-relevant content, a forum for communication. Well, the Wiki as a hypothetical 6th element.

This is to put it mildly impossible to implement. When updating one element of the system, the whole system will die.

One possible solution to the problem is to add one UMS element (user management system):



That is, you need something like a Jumlov team building at the level of different CMS and as a separate CMS.

With the emergence of such a system - the task of integrating systems is facilitated. It is not necessary to write 5 modules for different systems, but it is enough to write one for UMS.

Additionally, you can use OpenID to identify users in UMS.

In general, a very promising idea for a startup in the style of AVIZon , what do you think? :)

/ body

ps. based on UMS - “CMS2.0” (content management system content management system) can be formed :)

Source: https://habr.com/ru/post/15739/


All Articles