A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Jeff Wallace
Mar 18, 2013
  6687
(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
CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025

Optimizely PaaS Administrator Certification : Free for Everyone

Optimizely has recently launched a free PaaS Administrator Certification. https://academy.optimizely.com/student/activity/2958208-paas-cms-administ...

Madhu | Dec 9, 2025 |

Fixing TinyMCE Initialization Failures in Optimizely CMS: A Hidden Pipeline Issue with .NET SDK Versions

Over the past few weeks, several Optimizely CMS projects began experiencing a puzzling failure: XHtmlString fields stopped initializing TinyMCE in...

Francisco Quintanilla | Dec 9, 2025 |

Jhoose Security Modules v2.6.0 — Added support for Permissions Policy and .NET 10

Version 2.6.0 adds Permissions Policy header support, updates to .NET 10, improved policy management, configurable security settings, and enhanced...

Andrew Markham | Dec 6, 2025 |