Feast will not be implementing oversized images because:
- Roughly 80% of pageviews are now on mobile, which is already maxed-width
- It creates additional styling considerations (read: headaches)
- To date, we have seen no compelling reason why you would even need it
Mobile over Desktop
With mobile views making up about 80% of all pageviews, design decisions are made mobile-first with support for desktop added after. The mobile layout of food blogs is already full-width, making for good readability with text and instructions being intertwined with food images and process shots.
Our mobile layout is already maxed width for mobile devices, which means the oversized images offer no benefit for 80% of most bloggers visitors.
Another consideration is pagespeed. Oversized images naturally have a larger file size, which takes longer to download, and slows pagespeed load times. What’s more important: a slightly wider image, or pagespeed?
Additional Styling Considerations
What do you do when a screen width is slightly too small for the wide image, and it runs out? Do you align left, right? Center it and let the edges hang over? How far over?
If you have a sidebar, how do you handle preventing the image from overlapping the sidebar?
All of these are complex questions. And absolutely solveable.
But WHY would you waste time implementing something that’s going to cause more headaches? What’s this giant, mega benefit that you get from having slightly-wider-than-content images?
Benefit of wide images
There isn’t one, aside from scratching an artistic itch. It has nothing at all to do with food blogging.
It doesn’t help increase time on site.
It doesn’t help increase pages per session.
It doesn’t help increase your revenue or income.
This is one of the most ill thought-out features in Gutenberg, offering absolutely no benefits.
DIY Implementation
There are lots of tutorials out there that show how this can be implemented. If you REALLY feel like it’s NECESSARY
