6 posts tagged with "JSS"

It’s probably seems like Sitecore’s JavaScript SDK (JSS) has been on the back burner since the last release. And yes, you read that right, JavaScript SDK (formerly known as JavaScript Services) got a little naming update to align better with its new .NET Core SDK cousin.

Before I go any further, I want to acknowledge our wonderful community, who definitely has not taken any breaks. They have kept up blogging, making videos, presenting at virtual user groups, doing demos for us (🥰), and lighting Slack on 🔥🔥 - keeping the knowledge sharing and innovation going strong. The JSS team and I want you all to know how much we appreciate the collaboration.

Now, on to business. There have actually been big things happening in JSS behind the scenes.

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

Component reuse is an important subject for developers. As I was building structural grid components for my JSS app, I thought, “all projects need grid components, so is it possible to package these up for reuse?” So I set out to create a POC of the idea. This post shares how I published JSS components as an npm package that can be imported into other JSS projects.

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.

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

My "jss-sandbox" site is going to showcase upcoming Sitecore community events. But before I could start the fun part of building components, I needed to create some mock content.

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

The manifest API is important for modeling Sitecore data in disconnected, code-first workflow. If you are using a Sitecore-first workflow, then you do not need to worry about the manifest.

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