Sitecore Overload

Habitat and Helix Habitat is an example on how you can set up a Sitecore Helix solution. I have seen several projects using it as a starter. Habitat is not intended to be a starter solution, or as a recommendation of tools for your solutions. https://github.com/Sitecore/Habitat I created some notes and steps in notepad while setting up my first and second Helix project. I shared these notes with my team members and it has been used as a way to start new Helix solutions for our team. Setup new Sitecore Helix Solution 1, Install site  For Sitecore 8 use SIM . For Sitecore 9 install site with install.ps1. 2. Create a new project in Visual Studio Online 3. Clone the project 4. Create empty solution 5. Add your Sitecore .gitignore This is my starter .gitignore. 6. Add nuget.config 7. Add  "empty" node-templates for feature, foundation and project These will be extended as the solution grows. My starter node templates on GitHub . Feature ...

The add-helixmodule.ps In my first Sitecore Helix project I got introduced to a PowerShell script add-helixmodule.ps1 This script has a few commands that you can call from the console inside Visual Studio: Add-Feature Add-Foundation Add-Project This script saves us a lot of time creating new feature and foundation projects in Visual Studio. It creates a project inside Visual Studio based on a "template". The creator of this PowerShell script is Marc Duiker, for more info you can read about it in his blog post here . Why have two different templates After creating several feature and foundation projects, I wanted to extend the template to have more references and files in the feature projects. I did not want to add all of these changes when creating foundation projects. The solution I solved this by creating two module template folders. One for Foundations and another for Features. In the Feature module template I added references to the foundation projects an...