Bitrix Framework

Seeking knowledge first

The programmers who switched to Bitrix Framework from other platforms and CMS face additional difficulties caused by the “pressure” of previous experience.

In order to learn how to work in Bitrix Framework efficiently, you should try to understand the way other things are implemented in this system rather than compare the things you know from other systems. The “comparative” method is of no use for this course. Omit your old knowledge and study the new system using only your knowledge of PHP and site building rather than comparing ideologies and technologies. This will make it easier for you to grasp. You may indulge in comparison later, after you have mastered Bitrix Framework.

The direct comparison of Bitrix Framework and other systems does not always work. And yet these questions do arise. That is why we will include some opinions given by the partners of Bitrix and programmers working on Bitrix Framework.

Bitrix Framework and Drupal

The main structural unit of CMS Drupal is a node. As a matter of fact, any page of a website on Drupal (except for service) is either a list of node previews or a complete display of one node. Any page may be displayed together with additional blocks, but they are secondary in relation to the node anyway.

In Bitrix Framework the ideology of infoblocks is implemented. Infoblocks are structurally similar to a table in a database. Infoblock is a collection of objects with the same set of properties.

All infoblocks are equal in the sense that any infoblock (or even several infoblocks) may be used for displaying both in the primary area of the page and in additional areas. Thus, a node in CMS Drupal is just a particular case of infoblock, and this system actually has only one infoblock while Bitrix Framework may have an unlimited number of them.

Bitrix Framework and Joomla

• The site templates in Bitrix Framework more or less correspond in concept to the site templates in Joomla.
• Creation of a site template for Bitrix Framework using a ready-made layout consists in the selection of blocks and the placement of components instead of these blocks. Then, these components are set up for a data source and output templates are edited for them in accordance with the site layout.
• Unlike Joomla, the Bitrix Framework site template has no positions for numbered modules. Therefore, a programmer cannot indicate from the administration section as to which model must be allocated to which position simply by changing a number. The placement of components in Bitrix Framework is different.
• Modules in Bitrix Framework constitute a backbone for the integration of all the functions necessary for programmers in a single place and their separation by versions. Extensions perform the same function in Joomla.
• A module in Joomla is a component in Bitrix Framework. A component obtains data from somewhere and displays them as necessary. A component template is responsible for proper displaying.

  One component may have several templates that display information differently. For example, if you need to display news and articles on the site, you should create two folders on the disk, put the News integrated component into each folder, and set them up for a data source. After that, you can revise templates.

• Dynamic and static data are separated in Bitrix Framework. There are clearly dynamic blocks, for example a catalog of goods. There are static blocks. And there are mixed blocks. However, in order to display dynamic information, e.g., a catalog of goods, you must build a “house” for it – a folder on the disc where a “catalog” integrated component will be located and process references to dynamic information.