Code a la Mode banner

Sitecore JavaScript Services - Troubleshooting Errors of Going Connected

This post is part of a series - Sitecore JavaScript Services (JSS) Sandbox

Disconnected vs Connected

Similar to disconnected mode, connected development mode also runs your JSS app on a local server (http://localhost:3000). The difference is that in disconnected mode the app is hydrated with content from yaml/json files, but in connected mode the app is hydrated with content from Sitecore.

To run connected mode, I needed to deploy my app to Sitecore, which did not go smoothly. This post covers the errors I experienced and how I solved them.

Read More

Sitecore JavaScript Services - Customizing Scaffolding of Components

This post is part of a series - Sitecore JavaScript Services (JSS) Sandbox

This post explores customizing the jss scaffold command. This post is part of a series on learning to work with Sitecore JavaScript Services (JSS).

When I followed the “Getting Started” guide from JSS Documentation to learn how to create new components, there was one section in the docs that caught my eye:
Your First Component | Sitecore JSS Documentation

Scaffolding a JSS Component
JSS’ sample apps include a script that allows you to easily scaffold new JSS components. The script is run like so:

jss scaffold <componentname>

This script is a completely customizable boilerplate (_scripts_scaffold-component.js) if you don’t like the default scaffolding conventions. Take it and make it yours!

Read More

Automate Creation of New Sitecore Projects Using Yeoman

Visual Studio solutions for Sitecore projects are quite complex, as there are multiple integration points to manage. Automating the solution setup process accelerates the time it takes to kick off new projects and enforces consistency across the entire development team.

This post demonstrates how to use Yeoman to create a custom Sitecore project generator. With Yeoman, we can create a Sitecore solution template that’s source controlled and collectively managed. This allows teams to hit the ground running faster, and when a team does something really cool in their project that everyone likes, they can add it to the template so that everyone can benefit from the learnings and the “company standard” can evolve.

Read More

Run Gulp Tasks From the Comfort of Visual Studio

If you are a back-end Sitecore or .NET developer who spends most of your time inside Visual Studio, and your project utilizes gulp tasks, then I’m sure you understand the convenience of the Task Runner Explorer. This window allows running gulp tasks from within Visual Studio, and (even cooler) it allows binding specific tasks to MS Build targets. There’s just a couple steps needed to get this window to work correctly.

Read More

Building for Multiple Sitecore Versions With .NET Core

One of the most important factors in authoring a successful Sitecore Marketplace module is maintaining compatibility with new Sitecore versions. This post goes over how to utilize .NET Core’s simplified csproj footprint and implicit package dependency resolution to build your project against multiple Sitecore versions in one step. Automate the dev-ops part of maintaining modules so you can just have fun and focus on the code.

Read More

Custom Sitecore Pipeline Processor to Allow Dynamically Binding Multiple Placeholder Settings Items to a Single Placeholder Key

This post is part of a series

  1. Structuring placeholder keys and settings in a multi-site Sitecore implementation using out-of-the-box functionality
  2. Custom pipeline processor to allow dynamically binding multiple placeholder settings items to a single placeholder key

Building upon the Placeholder Overrides functionality described in the last post, this post describes a small customization that enables any page template to bind multiple placeholder settings items to the same placeholder key. This is very useful in multi-site implementations.

Read More