Let's use this time to work together on creating the materials we need to onboard developers and provide the necessary reference material to develop on our platform.

Reference

• OEP-19 Developer Documentation
• Architecture Onboarding Presentation
• Architecture Onboarding Presentation feedback

Goals

• Onboarding
  • Onboarding new developers (internal and external)
  • Onboarding current developers - to new areas - reference material
  • A more approachable structure/direction than the current Onboarding wiki
• Dogfooding our product(s)!
• Keep up-to-date and maintainable
• Refine OEP-19 (Dev Doc) based on actually practicing
• Open edX
  • Keep the content generic (for Open edX), but call out edX-cohort-specific details.
• Content
  • Current and future architecture state.
  • Without overloading with too much information.
  • Main content + "aside" with further detail
  • Assessments - for some things - not necessarily all

Non-Goals

• Not duplicating documentation
• No videos - since hard to maintain and update.

Cohorts

• edX employees (only if private info is required)
• developers
• non-developers

edX Course

Here are some tasks that can be parallelized and worked on independently.  We can break into groups or pair up during the meeting.

High-level Tasks

...

Content-specific Tasks

Create or transfer content to the course - export diagram, add wording, create assessments, etc.

...

• Immerse Frontend throughout the slides/course - not just a separate section.
• In addition to "Services" slide, include a "Clients" slide.
• Decoupled Frontend Architecture (maybe reference the incremental path diagram)
• https://github.com/edx/front-end-cookie-cutter-application
  • Note: Update FED technology OEP to just refer to this repo
  • Technologies and versions: https://github.com/edx/front-end-cookie-cutter-application/blob/master/package.json
    • Includes: Paragon and Bootstrap
• Maybe reference devops SLAs re: independent microfrontends
• Analytics
  • may not have a single solution across all FEDs - but may have a default suggestion.
  • may use https://github.com/rangle/redux-beacon
  • cool tool: https://www.fullstory.com/
• XSS "Django Frontend" diagram needs to be updated

Possible Outline

Crowd-sourced outline:

• (Section) Introductory
  • (Subsection) edx.Org Intro
    • Mission, Themes
  • (Subsection) Parts of course.
• (Section) High-level architectural overview
  • (Subsection) 
  • (Subsection) Scale
  • (Subsection) Mobile Strategy?

Outline from Current Presentation

...

• edx Themes
• DDD principles/overview - slides 5-9
  • edX.org Core
  • Diagram of Core + Customers
  • Subdomains high-level diagram
  • Subdomains + bounded contexts diagram
  • ??? Subdomain interactions
• edx.org Services
• Content diagram
• User diagram
• Data Sources of Truth
• Content Data Flow
• User Data Flow
• edx.org External Services
• LMS/Course Content mini-dive
  • Course Structure
  • LMS Screenshots
  • Content Size (# xblocks per course)
  • XBlock Types
  • XBlock details
  • Course Content Extensions

...

• edx.org Usage Growth
• edx.org Content Growth
• Developer Growth
• Web Usage
• Mobile Usage
• Web Performance (New Relic screenshots)
• Reactive Manifesto
  • Message Driven (future)
• Scaling in Devops
  • Intro to environments, deployments, clusters
  • Autoscaling groups and other infrastructure

...

• edx-platform components
• LTI slides
• Grades slides
• Analytics slides
• Schedules
• XQueue
• XQWatcher Pull Model
• XServer Push Model
• eCommerce
• Forums
• Server-side to Front-end templating
• TODO
  • Devops
  • SSO & OAuth
  • JSInput
  • CAPA 

...

• edx.org Server Environments
• Tools & Technology (slides)
• Monitoring and Data Analysis
• Coding Standards
• Testing
• Security and Security Attacks
• API Design

...

Meeting Notes