Build websites only with board tools
With the help of the Content/Contentmenu components it is easy for customers to prepare a simple set of pages to maintain their own content. Of course such a site focuses a little on the online shop 😉 but other tools like a CMS system can be saved.
Contents are stored in the content area – only the short name of the post has to follow a certain pattern to appear in the navigation. Post pages can also be used in the navigation (to be set in the PCG) as before.
In the standard template, the fastest way to go live with a shop, the corresponding components are already provided in the upper area and appear automatically if posts are available.
Posts can be written with the built-in HTML editor or in Wiki syntax. The WebDesigner also keeps a little more influence over the style of the articles written by the customer.
Besides, text modules can be used in another post as variables.
Images in the shop are usually delivered via the built-in proxy. This mainly catches too large images, wrong data and image formats of the stored images.
Now you can – via the configuration of the components – also scale individual dimensions, e.g. using wide narrow banners in the header area of the articles.
More display options
In some places further data elements are provided, e.g. the basic prices in the list view, information about blocked orders or indications for picture errors or article notes. Usually these parts are built in as non-intrusively as possible to avoid interfering with designs. In the standard template, all new features are always included first.
Individual designs therefore sometimes have to be corrected manually. Maybe you have to look into the Trello every now and then.
In this category we inform developers about changes to the system. Normally we will keep all interfaces (CSS class names, API calls, library dependencies) backwards compatible. For this reason, find here changes that can be incorporated into your managed websites, but they do not have to. Occasionally we also mention fixes for “prominent” bugs.
- A change in the HTTP headers now prevents caching from taking effect in development environments if it is not intended. This was the case when simultaneously editing files with calls to a staging and to the live system (or generally from different servers).
- Improvements in the SEO area: All permalinks have been unified to really point to one resource. In general, navigation entries now all have an href attribute (. oo-shop-item-permalink). The generated sitemap has also been adapted to the new shop.
- New component: Chat. After a long evaluation of alternatives we decided to implement our own. This component is to be installed and adapted like all the others; there is a design guide and also a reference. As a WebDesigner you have the right to use the “remote station” in the admin area, so you can try it out and design it. A more general description will follow in a later blog post.
- New switch on the search component: data-oo-search-onenter=”true” allows an “Enter” to trigger the search directly. If you do not select this option, the results preview will be displayed as before.
- New component: Subscribe. We also use them ourselves in our blog. This makes it very easy to register for a newsletter, including double opt-in. After successful confirmation, the addresses land in a PCG action group. The unsubscription can be done with links from the serial mails and is also handled by this component. So try out the whole process during design!
(Translated with DeepL.com/Translator -sorry, but its great! – Bob)