Solution Documentation: Solution Structure (Branches & Sites)

How do branch inheritance and releasing changes work in 7.2 Solution Documentation?

What is a 'solution' in 7.2 content management, and what's the best-practice number to use?

What does a classic five-system ERP landscape look like in LCG terms?

What's the best practice on how many branches to create, and why have multiple project teams share one?

How does a Logical Component Group let non-technical users connect a process to systems, and what do its logical components represent?

What does the product/version-independence of a Logical Component Group let you include in a solution, and who else reuses it?

What does a 'conflict' lifecycle state mean for a SolDoc element, and why does the maintenance branch take priority?

What extra branches might an S/4HANA implementation add, and what special branch does Business Process Monitoring need?

What is a branch, and which two branches are created automatically with a solution?

What is a 'site' used for, and how do you enable it?