Documentation Required: Title overrides

[jswope00]

A test case exists in the ULMO Testing doc that has no documentation. Therefore, documentation is required. Here is the ULMO Test case:
Test Title:
Title overrides

Notes:
Component displays the overridden title in the course

Description:

1. Open a content library with a published component that has a title
2. Use the component in a course
3. Override the title
4. Save changes

[sarina]

@sdaitzman could you help me out here? We're trying to match named release test cases with documentation pages. However I'm not sure what documentation to add in this case. What is the full override behavior? We need a how-to page in the documentation about what overrides do - and do you lose th eability to sync your unit if you do an override? etc

[sdaitzman]

Responded on #1298 with an overview of override behavior. A lot of the behavior is documented in the Content Libraries project board under openedx/frontend-app-authoring#2182

Let me know if there are any additional questions, I'm happy to devote some of my CC time in the next week to help support this testing/documentation effort with more user-facing documentation.

[sarina]

@sdaitzman -

I'm happy to devote some of my CC time in the next week to help support this testing/documentation effort with more user-facing documentation.

Any chance you'll have some time to write up some documentation on this? I think we need a "How-To" article that covers how to override library content in your local course, plus a bit on what the effects are (particularly, how does it affect ability to sync down the road, and what happens if you sync -do your overrides disappear? Is there a difference between overriding a problem block vs text block vs title vs sequence?)