Bitrix .NET Forge CMS features an adaptive interface with flexible settings and drag-and-drop components at the back-end and in the front-end of the product. Website administrators and content managers enjoy using our product because it has a familiar MS Windows-style Control Panel with quick access to any part of their web project.
Amber Ergonomics is:
- A concept for simplicity and convenience in site management
- A powerful front-end administrative console
- A top-notch end visual editor
- Cache dependencies in infoblock components
- A set of recommendations for web developers
The simplicity and convenience in site management concept
Managing information is a daily business and we do everything we can to make that work enjoyable! In each new version of the product steps are taken to make the Amber interface better. In this process, user experience and feedback from developers (resellers) and clients of Bitrix are considered. As a result, the interface is always a work in progress, with that progress facilitating your work.
The Amber interface contains two tabs, which allow easy navigation while managing content. Both modes can be seen and accessed only if you are logged in and have appropriate access permissions.
The new Amber Interface offers two basic modes:
- Site Mode - the front end of your website or portal where you can make changes and view them instantly;
- Control Panel Mode - the back end of your website or portal where you can create, manage or modify structural elements or settings of your web project.
Cache dependencies in components of infoblocks
You do not have to press the refresh button and update the cache of a page in order to see changes you have just made in your site! Edit or add news, products in a catalog or any other element of an information block and you will see the results immediately!
This is possible through cache dependency technology, which displays modifications immediately by means of automatically updating cache data after modification. This is an extremely convenient and time-saving feature, since there is no need to wait for the next schedule cache update. This feature is greatly appreciated by content managers, both experienced and not-so-experienced.
Recommendations for web developers
The Amber concept includes a full set of technological recommendations for web developers. The impressive list mainly deals with the creation of custom applications on the Bitrix platform for optimal integration with the Amber interface. The majority of these recommendations are well-known to experienced Bitrix developers:
- Design. The Integration guide should be followed especially concerning implementation of design templates. We have designed the interface to allow the widest range of layouts and designs possible.
- The site template should use standard menu components with caching.
- Use of Components 2.0 is recommended. Standard components and customized components can be used as well.
- Copy the component template before adjusting its appearance. This ensures that updates will not overwrite them. Templates can be copied directly from the front end of the product using Edit Mode, and any number of template copies can be made
- We recommend that component that have been modified or created be saved in a separate folder with a name that does not occur in the Bitrix standard product.
- Use composite components (violet-colored) to create complex functional elements or multi-page features; linking single-function components often presents difficulties for users.
- To speed up work of the site and scalability of projects that support auto-caching, use Cache Dependencies.
- When configuring the settings of components, it is best to set the component’s Auto + Dependency value to something large (1 – 12 months if you have Cache Dependencies fully implemented).
- In the autocaching regime, the component should not perform database queries or should perform only those queries for which caching is irrational.
- To the extent that it is possible, support of SEO-friendly URLs should be implemented in components to optimize SEO.
- Support of list management elements should be carried out through the API of the product. This allows users to edit and delete elements directly in the site’s pages.
- Major developing work should be done through the creation of a purpose-built module using the API and include the newly-developed components. Placement of such modules in the Bitrix MarketPlace and updating through Bitrix’ SiteUpdate is subsequently possible.
- Work with system objects should be performed using the API platform. We strongly recommend not creating direct queries to the database, as this could result in incompatibility with the update system.
- Preserving the integrity of the core of the product and using our recommendation while developing a project will allow you to update the product using SiteUpdate. If it is necessary change the basic operations of the product, the internal event system can be used, but we strongly recommend seeking consultation on this point.
Site development adhering to these recommendations provides clients with assurance on several issues of principle importance: ease of management, receiving of updates, high performance and high security.