World is now on Opti ID! Learn more

Jeff Wallace
Mar 18, 2013
  4377
(0 votes)

Divider “Layout” Block

Based on EPiServer 7 and the Alloy Templates

The new Alloy templates released with EPiServer 7 are based on a grid layout. The grid contains a number of rows in which content  blocks will automatically resize and fit on the same row or flow to different rows based on the space available. Ted Nyberg explains this concept well in  his article on the template package. This is fantastic stuff, especially in the mobile world.

 

In some cases editors or marketers may want to create a page and have a little more control over this automatic flow. For example, if they were using the Alloy templates “Landing Page”. I’ve created a “Divider Block” for this exact case. It doesn’t really do anything other than what the title says, adds a divider.

image

Let’s say, for example, you have three items in a row:

Third block

But you really wanted two items in the top row and the third block to push to the next row row similar to what’s pictured below:

Second block

image

No problem! Just add the divider block after the second block and that’s exactly what will happen!

Second block

image

image

If you’re wondering about mobile, well, everything will continue to flow as expected for mobile devices. Simple, yet effective in enabling an additional level of control for the layout. Smile

 

Get the code here…

Enjoy!


  1. This is intended as a starting point for you to customize for your project needs. The code is provided “as is” without warranty or guarantee of operation. Use at your own risk.
  2. If you install on a site that does not include the Alloy Templates you should expect that you will need to make a few minor updates to get it working as desired.
  3. Block photos above (First block, Second block, Third block, etc) were taken from Ted Nyberg’s article on the Alloy Templates.
Mar 18, 2013

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |