Layout Block
Created 6 years ago by ryanthompsonI have a layout block (PRO) that is DONE but for some options: https://github.com/anomalylabs/layout_block-extension
Here are some things I need help with:
Rows
Currently we have this structure:
- Assign the Blocks FT like you normally would.
- Add a Layout Block
- Add a row within the layout
- Add column(s) with the layout
- Add more blocks per column
The key here is the row. My question is
Do we want there to be a row or should the layout block be the row?
I think some related questions are:
Do we want the Layout block handle the page container?
Do we want to add a Layout block to add another row?
I think a lot of this comes to UI. With the block being the row - we could condense the UI a bit so it's not so nested.
Do any of you have any experience with a similar system? Is it common to let your Layout block handle the container / page width?
Take other blocks for example - mostly they assume full width and thus require a container. So those will rely on a theme container out of the box (customization is another topic - this is out of the box behavior).
I plan on using https://tachyons.io/ for the layout stuff since it's versatile, small, and will be easy to override.
Thoughts? Questions?
@william in generic form sure. I don't have sizing options in there so it's 100/count(columns).
@dwains Mostly for aesthetic purposes. The extra layer (think grid in grid in grid vs grid in grid) is kinda eh.. IMO the shorter the relational strand the better. So no row - the block IS the row. But.. that might be weird.
@dwains wrong thread. But since you mentioned: https://pyrocms.com/posts/icon-field-type-v1-0
Update - this has been changed to separate and free section and column blocks. Working on some styling / CSS control automation and these will be done.
Do we want there to be a row or should the layout block be the row? I prefer that there will be a row
Do we want to add a Layout block to add another row? I dont see why