Stuff to do LATER.Ĭurrently, I'm writing the css directly into the inline styles of the divs. the danger is probably pretty mitigated by the fact that most sites wouldn't allow untrusted users to build layouts, but if you are doing that, consider this a warning. Patches welcome :-)Īlso, there's very little validation on the user input. Clearly, something changed since the last time I did this, so I should square that away sooner rather than later. I have form errors in my code, but they aren't showing, and even I got confused a couple times when I did the css wrong and it wouldn't submit. By implementing these two properties as configuration, we can extrapolate how many layout regions to create, and we use the raw css to style the divs. These form elements conform to the grid-template-columns and the grid-template-areas css properties. Grid Layout provides a new configurable layout plugin with two form elements. This is a first pass at building the most basic version of what I wanted. So with that small introduction, I give to you the Grid Layout module. Having a new version of that idea built on new standards has been a personal goal for quite some time. Merlinofchaos built a flexible layout plugin builder in Drupal 6/7 for panels, but things like flex & grid were a distant dream at that time and so the implementation was much more difficult, and had some interesting side effects for deeply nested regions. Both inside and outside of Drupal, other tools have and do exist.
Now, I'm certainly not the first to do something like this. Elegant enough to attempt building a tool around. So, as page layout tools have evolved, doing the sort of CSS I used to spend hours on has become a simpler and more elegant process. At some point we've all been the one-stop-shop for everything we wanted to get done. CSS grid is GREAT! I think most of us got into web development at the front end.
DRUPAL RESPONSIVE GRIDS FULL
Full disclosure, it doesn't work in IE 11. While adopting option 1, I made myself familiar with css grid. I've been down that road before, and while Layout Builder has a bunch of great options for limiting how users might experience a situation like that, I really didn't want to write and maintain that many new layouts and control when they are or aren't available. As the site stands right now in my local development environment, this is the choice I've taken.
.png "drupal responsive grids")
Abandon Layout Builder in these cases, and use old school css to style my entities.While the 33/66 & 66/33 layouts had been great for roughing in the site, they were falling desperately short of what I actually wanted. However, once I stopped to look critically at my ACTUAL layouts, I wasn't very happy. Layout Builder, like page_manager/panels/display_suite before it, is limited to the pre-existing layout plugins in the system. I was rocking and rolling, and really enjoying the process. I built an SVG formatter for displaying dates. I built a "Heading" formatter so that string data (like titles) could be turned into h1s or h2s via the user interface. At first, most of my issues were easily solved by building new field formatter plugins. In a word: "nothing". Layout Builder does exactly what it says on the label and it does it well. This hasn't gone anywhere close to how I would have liked. All in all, this has gone pretty well, but as a big contributor to Layout Builder, I really wanted to use it on the site as much as possible.
DRUPAL RESPONSIVE GRIDS UPGRADE
Obviously, I've been planning to upgrade it to the newest Drupal 8. It's been iteratively migrated and upgraded from those early days on pmachine to its current iteration on Drupal 7. I've been working on a personal site that I've maintained since before I even got involved with Drupal.
0 kommentar(er)
