> amount of additional dev overhead
# event-news
d
> amount of additional dev overhead when implementing a fully flexible block grid system As I covered in my talk - this is why you have a dotnet new template with all the basics already made
m
Yeah for sure that definitely helps. I guess it depends heavily on the design, right. If many of the sites a more of a templated type things with a lot of similarities that it's perfect, but if every project is fairly different in it's layout, you still end up having to work out thoses sizes values again. To be clear, I'm not saying block grid is bad, it's not, it's great and can give content editors a huge amount of control and flexibility. All i'm trying to get across is that each time there is a new layout option for a component, it can create more dev work, which sometimes isn't viable for a client 🙂
d
Generally we have found adding new features such as various combinations of image and text layouts is an hour or two work. I have a
_Layout_Layouts.cshtml
and
_Layout_Features.cshtml
to handle all the common stuff then exceptions in the feature file itself. Most of the time layout variotions can be handled with Settings on th eblock grid item a small amount of css
m
For some reason I entered a comment, posted it, but nothing appeared so i'll try again haha
Yeah for sure that definitely helps. I guess it depends heavily on the design, right. If you have a few sites all with similar designs and layouts, it's perfect, but if a lot of your projects have fairly different designs, you still end up having to rework out the sizes etc, and cater for the components at different sizes. As you highlighted, this is getting easier and easier with things like container quieries and css grid, but it still adds more dev work, which isn't always viable for every client. To be clear, i think the flexibility that the blog grid offers is brilliant and definitely worth using for the right type of client, which you pointed out too. My point was less about the technical aspect of how to do the grid, and more around the technical overhead multiple layout options brings with it
d
> technical overhead multiple layout options brings with it I think I need to write up how I handle this - I promise once you have a template system and component library in place layout variations are a breeze. I feel another talk coming on 🙂