Posts Tagged ‘Sitecore’

The process of taking advantage of the Ignition framework when it comes to building models is to pass data successfully to the view’s agent so it can use its PopulateModel method to transfer the data to view’s model or perform any other logic necessary to properly render the Sitecore component. Through MVC’s architecture, a query […]

I am a broken record on this one topic: Don’t let site search be an afterthought. When determining or upgrading your web solution, site search should be in the mix of the business, strategy, and connectivity discussions from the beginning. Not only is it a user expectation and a way to improve customer experience, but […]

Okay so the first question some of you may have is why the Iced Cap made with Chocolate Milk. If you know me you already know this is my favorite beverage in the summer.  Now onto my article. There are lots of articles on the methods and there are options but no article lists all the […]

I was creating a component in Sitecore where the item structure was three tiered meaning that the component’s datasource, its children and grandchildren from its structure in the content tree would have to be accessed to properly populate the component.  An example of this structure is shown below where the component’s datasource is the top […]

The Ignition framework contains an overridden version of the View() method which is used to not only call the view file which is to be rendered but also has a variety of options to support sophisticated logic associated with rendering the view.  The View() method full signature is defined as follows in Ignition. return View<TAgent, […]

One of the big drawing points of the Ignition Framework for Sitecore is its usage of field templates. In a traditional Sitecore environment, developers must explicitly add all fields to their templates directly. The Ignition approach is to define Sitecore fields as interfaces; simply inheriting an Ignition field’s interface will bring that field’s functionality into the […]

Video Episode 1 – Taxonomy The day in the life of a content author/editor or potential content marketer is busy enough as it is. Finding time to also learn a new platform seems like a daunting task and frankly it can take many months. As one that has been down this road I thought I would […]

The Ignition framework has as a standard for using a constants file as opposed to having constants randomly assigned to variables throughout the application.  When a new Ignition project is created, an IgnitionConstants.cs file is added to the Ignition.Sc project within the Presentation folder of the Ignition solution. Example of the type of constants oriented […]

Ignition is an open source framework for Sitecore, developed by Perficient. It follows industry best practices for architecture and dependencies. It is fast and easy for developers to build new content components. Search blogs.perficent.com for more articles about Ignition or check out the online documentation. In this article I will continue using my “ContentBlurb” component […]

Using the Ignition Framework, we have variety of methods in our disposal for setting the view path to find the view.  The methods of setting the view path which will be discussed in more detail will be… Inherit folder structure Within the View Model itself Using the View Agent Using Agent Parameters Inherit Folder Structure […]

In my introduction to Sitecore’s SPEAK framework, I mentioned that SPEAK applications should always be built from a branch template provided by Sitecore. While it is possible to write a SPEAK page from scratch, there are many moving pieces to consider. Because all SPEAK applications require certain components to function (JS libraries, CSS, a Sitecore layout, etc.), this article […]

Sitecore has five list field types that Glass Mapper maps: Checklist, Multilist, Multilist with Search, Treelist, and TreelistEx. Out of the box, Glass Mapper supports mapping these field types to two .NET collection types: IEnumerable<T> and IList<T>. In this post I’ll cover how to use Glass Mapper to map your code models to these field types.