The final choice fell in favor of Layout Builder, despite its young age nature. management capabilities, which would be pretty complicated and time-consuming to integrate with fields in paragraphs. The second option was also a no go as the platform in the making was to have color, font type, etc. Layout Builder = ok, but not totally stable.Īs we already mentioned - panels were simply too difficult to handle for inexperienced users.Paragraphs + Bricks = ok, but not what we wanted exactly.We came up with several most optimal options to choose from: This included choosing the most proper page builder. All the platform specifics needed to be as clear as a bright day to every other user.Īll this spawned a necessity for a week-long brainstorm to figure out each point in the most optimal way possible. Lastly, surely, we had to come up with a painless way to deploy all new layouts and updates for end-users. We needed to help everybody paint the big picture step by step so that they would, for instance, understand that it’s unreal to complete the project in a month’s time or so. Then there were the priorities in different Markets’ requirements. That’s why we just had to create something that a non-Drupal employee would be able to understand and efficiently use in working practice. The idea to adopt a Drupal-based system was the head office’s one and so all connected offices simply had to deal with it. When we were going through page builders to choose, we almost decided to teach everyone to use panels eventually, but timely understood that we wouldn’t be able to do that efficiently even in a week’s time. How to deploy new layouts/updates painlessly.How to make the life of 30+ people who will be using the platform easier.How to teach all Market reps to work with Drupal.On top of that, we had to provide an interface that would be equally easily grasped by the 25 people (the client’s team) who would be working with it. Read also: the detailed roadmap for Drupal 8 to Drupal 9 migration Thus, every Market gets an optimized builder interface to handle projects individually the way they see them in every other country based on a single platform. The major gist of the platform we were working on is that the client wanted a solution that its head office would distribute among the Markets located in different countries. List of settings per block inside builder - the next thing we had to provide is the ability to, when working on the structure of the website (adding blocks and such), add certain basic settings (you shouldn’t necessarily need to know which particular settings you will have to add from the very start, but stay sure that you will need to do that one way or another and the number of required settings would formulate in the process of building pages).Limit lists of layouts per content type - the client had a clear requirement in that they wished to have an ability to use any kind of layouts they wished anywhere in the platform to fill them with blocks.The default thing simply looks too cumbersome to handle. So the first question we had to clarify is whether we could somehow limit the list of blocks to make the content managers’ life easier. Limit lists of blocks per content type - you know how when you click “Add block” in the Layout Builder, you get a screen filled with a whole bunch of various options.Speaking of our practice case, our team needed to provide the client with an intuitive, friendly content management solution, and so we had to fulfill the following requirements and questions: That was our primary choice for the development of the new project, and we’ll give you more than one reason why we went with it in the first place. Then there’s Gutenberg - a pretty interesting new project editor solution that isn’t, however, polished enough for the best use in the field as of yet.Īugust 2018 saw the release of Drupal 8.5, which introduced the Layout Builder as an essential experimental module. They are pretty convenient to handle, but it’s hard for any “non-Drupal” person to get a good grasp on them fast. Panels, for instance, is a very common efficient solution for most, well remembered from Drupal 7. What major options do we have? Let’s see: This usually happens at the start of every project a Team Lead has now to handle most properly. sound more than familiar, you probably struggle every time you need to come up with the general page building approach. If you work on the creation of a Drupal project’s backend and the words “layouts”, “gutenberg”, etc. Layout Builder from “experimental” additions.In particular, let’s go through such topics as: Struggling with the choice of the best approach when implementing a Drupal project? Let’s go through the essential pains that every Drupal developer experiences and see Layout Builder may be the best way to go based on the finished case.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |