Helix.Docs
Helix.Docs copied to clipboard
Sitecore
Sitecore Helix is the official guidelines and recommended practises for developing in Sitecore.
As most of what FakeDb does can be accomplished through mocking, and as a 3rd party tool it may or may not be compatible with future versions, we should update...
With the new Basic Company [Helix Examples](https://sitecore.github.io/Helix.Examples/) going public, any Habitat references in existing docs which can be replaced with Basic Company should be removed and replaced. Below is a...
This is a lot of reading for what's not really solution architecture, but development best practice: https://helix.sitecore.net/devops/development/version-control.html At the very least, I think this section could be drastically slimmed down.
It has become very clear that the Helix documentation should include some scenario-based narratives that give guidance on how to follow the practices and adhere to the core principles. Feature-to-Feature...
Implementations which are not yet using Helix, and do not qualify for a full tear-down, may benefit from refactoring to the Helix architecture. @anderslaub has spoken on this topic and...
Helix should include recommended practices for Sitecore XConnect, which provide for long-term maintainability and shared conventions across the community. * Sitecore XP development may require developing on, and deploying to,...
Helix feedback has included a desire for more guidance on multi-site implementation, specifically the ability to implement site-specific designs. This is a complex topic as multi-site implementation approaches can vary...
The [Definitions](../blob/master/helix/introduction/definitions.rst) is somewhat belabored, focusing attention on double meanings that pose little actual confusion, such as the distinction between a C# Project and a project in the business or...
Helix docs should be moved to `https://helix.sitecore.com` to align with the rest of Sitecore web properties, and appropriate redirects configured.
As Sitecore XP continues to introduce independent services split off from the "monolith," there is an increasing need to be able to deploy to multiple targets, both locally and in...