Bootstrap aware EPiServer content area render

EPiBootstrapArea

Bootstrap aware EPiServer content area renderer. Provides easy way to register display options used to customize look and feel of the blocks inside a EPiServer content area.

Getting Started

You would need to install package from EPiServer’s NuGet feed to start using Twitter’s Bootstrap aware EPiServer Content Area renderer:

PM> Install-Package EPiBootstrapArea

Default built-in display options are regsitered automatically. Below is described some built-in features.

Available Built-in Display Options

Following display options are registered by default:

• Full width (displaymode-full)
• Half width (displaymode-half)
• One-third width (displaymode-one-third)
• Two-thirds width (displaymode-two-thirds)
• One-quarter width (displaymode-one-quarter)
• Three-quarter width (displaymode-three-quarters)

Display Option Fallbacks

For every display option there are 4 fallback width for various screen sizes based on Bootstrap grid system. According to Bootstrap v3 specification following screen sizes are defined:

• Large screen (>= 1200px)
• Medium devices (>= 992px && < 1200px)
• Small devices (>= 768px && < 992px)
• Extra small devices (< 768px)

These numbers are added at the end of Bootstrap grid system class (for instance 12 for Large screen -> 'col-lg-12')

Display Mode Name	Extra small devices (xs)	Small devices (sm)	Medium devices (md)	Large devices (lg)
`Full width`	12	12	12	12
`Half width`	12	12	6	6
`One third`	12	12	6	4
`Two thirds`	12	12	6	8
`One quarter`	12	12	6	3
`Three quarters`	12	12	6	9 Eventually if you choose `Half-width` display option for a block of type `EditorialBlockWithHeader` following markup will be generated: ```xml ... ``` Breakdown of added classes: * `block` : generic class added to identify a block * `{block-name}` : name of the block type is added (in this case `EditorialBlockWithHeader`) * `col-xs-12` : block will occupy whole width of the screen on extra small devices * `col-sm-12` : block will occupy whole width of the screen on small devices * `col-md-6` : block will occupy one half of the screen on medium devices * `col-lg-6` : block will occupy one half of the screen on desktop * `displaymode-half` : chosen display option name is added ### Example Let's take a look at `One quarter width` block. This is a block layout in EPiServer content area on-page edit mode (desktop view - large screen `col-lg-3`):  This is a block layout in EPiServer content area on medium devices - `col-md-6`:  This is a block layout in EPiServer content area on small and extra small devices - `col-sm-12` and `col-xs-12`:  ## Customize Bootstrap Content Area In order to customize available display options you need to add new ones through provider model. ### Provider Model There is a tiny provider model inside this library to control how list of supported display modes is found. By default `DisplayModeFallbackDefaultProvider` provider is registered with following module: ```csharp [ModuleDependency(typeof(ServiceContainerInitialization))] [InitializableModule] public class DisplayModeFallbackProviderInitModule : IConfigurableModule { void IConfigurableModule.ConfigureContainer(ServiceConfigurationContext context) { context.Container.Configure(x => x.For() .Use()); } public void Initialize(InitializationEngine context) { } public void Uninitialize(InitializationEngine context) { } } ``` ### Register Custom Provider You can for instance create new module and register your own new custom provider: ```csharp [ModuleDependency(typeof(DisplayModeFallbackProviderInitModule))] [InitializableModule] public class CustomDisplayModeFallbackProviderInitModule : IConfigurableModule { void IConfigurableModule.ConfigureContainer(ServiceConfigurationContext context) { context.Container.Configure(x => x.For() .Use()); } public void Initialize(InitializationEngine context) { } public void Uninitialize(InitializationEngine context) { } } ``` **NB!** In order to run after built-in initializable module you will need to add dependency to it in your module. ```csharp ... [ModuleDependency(typeof(DisplayModeFallbackProviderInitModule))] public class CustomDisplayModeFallbackProviderInitModule : IConfigurableModule { ``` And then in your custom provider you need to specify list of available display modes by overridding `GetAll()` method. ```csharp public class DisplayModeFallbackCustomProvider : DisplayModeFallbackDefaultProvider { public override List GetAll() { var original = base.GetAll(); original.Add(new DisplayModeFallback { Name = "This is from code (1/12)", Tag = "one-12th-from-code", LargeScreenWidth = 12, MediumScreenWidth = 12, SmallScreenWidth = 12, ExtraSmallScreenWidth = 12 }); return original; } } ``` There is also backward compatibility with DDS storage. You will need to switch to that provider manually: ```csharp ... context.Container.Configure(x => x.For() .Use()); ``` Registered display options will be stored in Dynamic Data Store under `EPiBootstrapArea.DisplayModeFallback` store type. Currently there is no built-in support for editing DisplayOptions on fly from EPiServer UI. For this reason you can choose for instance [Geta.DDSAdmin](https://github.com/Geta/DdsAdmin) plugin. ### Additional Styles Similar to EPiServer AlloyTech sample site it's possible to define custom styles for block. You have to implement `EPiBootstrapArea.ICustomCssInContentArea` interface. ```csharp [ContentType(GUID = "EED33EA7-D118-4D3D-BD7F-88C012DFA1F8", GroupName = SystemTabNames.Content)] public class Divider : BaseBlockData, EPiBootstrapArea.ICustomCssInContentArea { public string ContentAreaCssClass { get { return "block-with-round-borders"; } } } ``` ### Localized Display Option Names You will need to add few localization resource entries in order to get localized DisplayOptions. Following entry has to be added to get localized names for default display options: ```xml Full (1/1) Half (1/2) One third (1/3) Two thirds (2/3) One quarter (1/4) Three quarters (3/4) ``` Happy Bootstrapping! [*eof*]