🧹 Maintain two separate main branches

[craineum]

Description

Currently we only have our main branch which includes templating tags for Lumberstack. If users clone the main branch it will include those tags everywhere. While they don't affect functionality, they can be confusing. I propose along with main we have a template branch that includes all those tags.

This would require us to maintain the template branch by merging in the main branch periodically. This would be synonymous with a production like branching system.

It will make adding new features a bit more complicated as you would have to PR against the main branch to implement the feature, then a second PR against the template branch once the first one is merged to add any tagging.

Affects

• Lumberstack
• Templating tagging

Consequences

Confusing template tags in our main branch.