edX Branding Sweep and Removal in MFEs

[e0d]

Initiative placeholder.

Goal: To remove unnecessary and irrelevant references to edX in the codebase.

Requires some discovery re: scope of project and intersection with other clean-up work.

[jmakowski1123]

Notes from Planning 3/7: Narrow scope to focus on MFEs. Create a discovery project with BTR to audit, capture and create a list of edX references. Then create plan to fix. Also target creation of a reference doc to outline how MFEs should be branded and themed.

[brian-smith-tcril]

course-authoring currently has edx branding in the studio header that will be removed when using the shared header component

i think good next steps here are:

1. Put together a list of all the MFEs we need to check
2. Do a quick check of each MFE, if we find edx branding:
   a. make an issue on the MFE repo with notes of all the places edx branding exists
   b. link said issue to this issue so we can track them all

[arbrandes]

This is, or should be, part of a checklist on whether an MFE is ready for release or not. (I'm working on that, but in the meantime, this is a summary of what's been suggested so far.)

Which is to say, we can be proactive and check each and every one right now, or simply create issues as MFEs are considered for release. I favor the latter, as the effort would be bunched per MFE, as opposed to per checklist item. In practice, I imagine this would result in fewer MFEs being released faster (versus more MFEs being released later).