Item | Notes |
---|
Start the Zoom recording! | |
Demos | Overview: rewriting static asset build for edx-platform to get rid of the python involved and have it all be front-end tooling What does it mean to process static assets? Build. Turn scss into css, run webpack Collect. Copy all built assets to a folder Watch. Run a daemon to look at built assets and rebuild if things change (only for dev env)
Making the collection step simpler: Before: certain xblocks generated scss and we used those as input to the lms and studio scss. That meant there were intermingled stylesheets Current: writing GH actions Ideally, no one notices except maybe that something is faster We don’t want to click through and look at every asset because literally no one has time for that Instead: look at output processes from old and new. Generate sha1s for each created file, and compare the list of shas.
Q&A:
|
Cross Pollination | |
Challenges Each challenge should have a follow up action. If you have an idea for follow up actions, add it. Or if you aren’t sure, leave it blank. We’ll discuss all actions either way.
| - Meeting captain: Transpose action items into the “Action Item” section below.
|
Successes | |
Suggested Action Items | 0-2 minutes: Last Time: This Time: |
Look at the board | https://github.com/openedx/wg-developer-experience/issues |