6 posts tagged with "Sitecore Tips"

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.

A multi-site Sitecore implementation is when multiple different websites are deployed into the same Sitecore instance. Each site has its own unique set of renderings and templates. However, even sites that look and function completely different may still share a common set of generic renderings, like grid structures or an image carousel.

This post is part of a series

1. Project Organization - Beyond Helix
2. "Sitecore Flow" - The benefits of versioning your Sitecore environments

Put aside everything you know about using git because this post explores a completely untraditional method. This method enables you to roll back failed deployments in seconds. Additionally, it automates the clean up of obsolete files.

This post is part of a series

1. Project Organization - Beyond Helix
2. "Sitecore Flow" - The benefits of versioning your Sitecore environments

This post covers recommendations on how to structure your Sitecore solution to support synchronized environments and quick spin-up of new instances.

4 practices specific to testing Sitecore that all Quality Assurance Specialists should follow to ensure correctness and head off bugs early.

This blog post covers how to inject extra metadata text into Experience Editor. One of the great uses of this metadata text it to help content authors see a visual difference between renderings that use local datasources and renderings that use shared datasources.