RFC: Helix Refactoring Guidance

[nickwesselman]

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 advocates for use of a "Legacy" layer to allow incremental refactoring.

Should Helix include recommended, incremental refactoring guidance? How have you approached Helix refactoring?

[lakesol]

In the real world there are 1000s of Sitecore project out in the wild. Anything which helps facilitating bringing those solutions into the Helix approach must be a good thing. Offering a clear and understanding route to allow these project to become part of the Helix principles must only improve adoption.

[muso31]

Just like @anderslaub I just move it all to a Legacy folder and then follow the boy scout principle refactoring parts as I need :) it works well

[TwentyGotoTen]

It would be good to see some documentation around the Strangler pattern appled specifically to Helix

[anderslaub]

Moving the existing solution to a "Legacy" layer is really the Strangler pattern.

I've tried to come up with a general high-level "recipe" but it is hard - or rather impossible - to make valid examples that sufficiently cover all the weird old solutions out there.

As far as I remember I go through the recipe in a presentation from 2017 that I cannot google atm (used to be available on sitecore.com). If I get the time at some point it would really make a great blog post.

[nickwesselman]

@anderslaub's presentation on this topic has been dug up and put on YouTube :)

https://www.youtube.com/watch?v=XN834h2lSWM