I am a certified Sitecore developer with a passion for the web. I hopped into the .NET space 5 years ago to work on enterprise-class applications and never looked back. I love building things—everything from from Legos to software that solves real problems. I have a strong foundation of backend skills, with sweet spots like security, portal solutions and APIs. Early on, before I had the benefit of SCORE, I made a lot of mistakes with Sitecore but learned a lot in the course of the struggle. I would like to support other developers by contributing my perspective on doing things “the Sitecore way,” rather than fighting the framework. Did I mention I love video games?
Managing your multisite configuration takes a special touch. Building a tenant-agnostic strategy for components and functions is key to ensuring you have an Enterprise layer that is flexible and efficient.
Managing your DevOps strategies can be a bit tricky - from builds and releases to the tools you need to be successful, navigating Sitecore can sometimes require a guide along the path. This post explores Team Development for Sitecore and Sitecore Ship as tools to drive DevOps automation in Sitecore.
Starting a new language version in Sitecore doesn't have to be painful. Sitecore Powershell Extensions can enable your team to copy and manipulate languages in bulk with ease. It's a favorite of every content team I've had.
Helix is an architectural pattern outlined by Sitecore to help guide developers into organizing their solutions in a consistent and flexible manner.Each tenant website that we introduce to the CMS should be thought of as living within the Project layer.
One of the beautiful parts of Sitecore is that it doesn't force you into a particular implementation pattern. You can build websites as small and simple as you like, or as large and complex as you need. You can have a single website driven by the CMS, or dozens hosted out of the same installation.