Jeff Wallace
Mar 18, 2013
  7074
(1 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

Petri Isola
Petri Isola Mar 18, 2013 08:39 AM

Cool. Just what the doctor ordered!

Mar 18, 2013 12:43 PM

Does this give any padding in the final rendering?

Jeff Wallace
Jeff Wallace Mar 18, 2013 01:12 PM

The output HTML is:



The idea here was basic. You could customize it to add a height property and add any padding you want, change the color, add a horizontal rule, etc. I thought about adding some configurations and realized I better focus on some other things first. :)

Please login to comment.
Latest blogs
Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 1 of 2)

How Niteco's Upgrade Machine   uses orchestrated AI coding agents to deliver a buildable baseline and a running CMS, then hands over for...

Hung Le Hoang | May 11, 2026

Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |

Optimizely SaaS CMS Developer Certification Exam

The Optimizely SaaS CMS Developer Certification is an industry-recognized credential for developers and architects who build scalable, composable...

Megha Rathore | May 5, 2026