Brian Beggs and I came up with the following epics:

Document Best Practices and Architecture Decisions
1. Code Structure: Python modules/django app, Tests, Assets, urls.py, settings.py
2. Assets: JS, Pattern Library, Sass, etc.
3. Interfaces:
  1. api.py
  2. REST
  3. Messaging (async versus sync)
4. Tests: Thoughts on Tests
5. Repos vs django-apps vs IDAs
  - Start with How to add a new feature to LMS or Studio
6. xBlocks can use django!
Validate the Seams
- What Engineering thinks - based on existing codebase and team review
- What Prod thinks - based on JIRA components
Discovery
- Can we co-locate assets?
- Find/create automated tools for refactoring
- Metrics
  - Complexity analysis tool
  - Dependency analysis tool
Dependency Graph
- Use as ongoing metric to validate progress
- Use as input for organizing folders and extracting components
Organize
- Group by functionality using automated tool(s)
- Validate progress using metrics

Browser not supported