CMS’s worldview and methodology
CMS (content management system) is a philosophical question.
Because cms has already reached the philosophical level.
Let's analyze the worldview and methodology of the best CMS in the world now and in the past
1. XOOPS (https://xoops.org/)
The former uncrowned king, the former "station erector".
XOOPS is almost unknown in China. But more than a decade ago, XOOPS was very popular in foreign countries and Taiwan. In Taiwan, it was even called a "website-building machine."
1. XOOPS’s Worldview
XOOPS believes that the world is people-centered. No matter what function it has, it must be used by people (users) in the end.
2. XOOPS Methodology
The core is a complete user center, and then install corresponding modules based on the user center (using hooks to mount to the user center) according to the required functions. For example: article module, comment module, RSS aggregation module, etc.
XOOPS's worldview and methodology are very classic, and many systems are built on this worldview and methodology.
2. WORDPRESS (https://wordpress.org/)
This is the most widely used CMS at present. Many of its concepts and methods have a huge impact.
In fact, the methodology of WordPress is deeply influenced by XOOPS. Its hooks and plug-ins are inspired by XOOPS.
But the worldview of WordPress is very different from that of XOOPS.
1. The worldview of WordPress
WordPress believes that people's needs for the Internet are two things: posting and viewing. That is, posting content and viewing content.
2. WordPress Methodology
The key is to do a good job of posting and viewing content, and then leave the rest to hooks and plug-ins.
Looking at the content, each website actually has its own needs, so the theme system is built based on hooks and plug-ins.
3. JOOMLA (https://www.joomla.org/)
This is currently the second largest CMS in the world.
This is a very unique CMS, Joomla. In my opinion, it is more suitable for people with a little development ability.
1. Joomla's worldview
Joomla believes that the world is multi-layered, and so are websites/WEB projects, from the lowest level of data to the highest level of applications.
2. Joomla's methodology
Joomla defines itself as something similar to "webOS". It is a relatively low-level and component-based thing. When using Joomla, you are actually using extensions based on this "webOS".
This is the same principle as making an IOS or Android app.
4. DRUPAL
This is currently the third largest CMS in the world. This is really awesome stuff.
1. Drupal's Worldview
Drupal believes that technology is reusable.
2. Drupal Methodology
Reusable, then configure it, and finally, configure everything.
As long as the CMS is fully reusable on a technical level, all required functions can be implemented through configuration without the need for further development.
Say more.
Ideals are full, but reality is skinny.
In order to make it reusable and configurable, Drupal has put forward many ideas and concepts, such as views, blocks, etc. These ideas and concepts have a huge impact on the development of CMS, and many of them have become the standard configuration of CMS today. However, even though Drupal is highly reusable and configurable, and even though many people use Drupal, few people can complete a website/WEB project through simple configuration. Most of them use Drupal as a development framework. Even in many foreign companies, there are many positions such as Drupal engineers.
5. DjangoCMS (https://www.django-cms.org/en/)
The first four are all things in the PHP world, now we come to the Python world.
Django (https://www.djangoproject.com/) is the most used development framework in the Python world.
DjangoCMS is the most widely used CMS in the Django community.
1. The worldview of DjangoCMS
No matter what the world looks like, what is ultimately presented to users is nothing more than pages one after another.
2. DjangoCMS methodology
How to build a page hierarchy?
How to structure the page?
Everything DjangoCMS does revolves around these two issues.
Therefore, using DjangoCMS is to configure the page structure and modularly build one page after another/layer by layer.
