[epic] edx-platform XBlock Extraction

In this epic we will extract out all the xblocks which exist in openedx-platform here

We have created a new repo where all these xblocks will reside sharing the common requirements file and release process.

Here is the core architecture PR for this repo

More details here: https://openedx.atlassian.net/wiki/spaces/AC/pages/4243030019/edx-platform+XBlock+extraction

Rationale

The extracted blocks will need to use the pure XBlock API rather than by cheating with edx-platform's remnant XModule-esque APIs. This will force us to improve several aspects of the XBlock API which are currently lacking for custom XBlocks.
We need to remove XBlock frontends from edx-platform in order to complete the MFE conversion process and remove edx-platform's outdated, hard-to-maintain legacy frontend tooling.
This will help simplify the relationship between LMS and CMS.
The extracted blocks will be easier to maintain and test in isolation.
We are fixing bugs and generating documentation along the way.

We will now move these xblocks to single repo as discussed here openedx/axim-engineering#1169

Repo: https://github.com/openedx/xblocks-contrib

I'm curious, is there any desire to move extract other core XBlock types as well? Specifically, I'm thinking things like:

HTML Block
Video Block
Problem Block

We've run into places where we had wanted to add/extend behavior and were limited by the fact that these were too tightly integrated into platform to neatly override them. I've also done some thinking here so happy to help with scoping / discovery on that work.

@nsprenkle

@nsprenkle Thanks for expressing the interest.

I've updated the story description to include more details. Any contributions or insights you can provide would be greatly appreciated.

refactor: Convert builtin blocks' sass variables to css variables (#3…

parent 42afa1b

fix: add resourcetemplate to xblock_mixins (openedx#37184)

chore: add aximprovements team to CODEOWNERS for xmodule

Adds aximprovements team to the code owners of xmodule (#37531)

Adds aximprovements team to the code owners of xmodule (openedx#37531)

Is this the right place for https://github.com/openedx/xblocks-core work as well? Should the issue description get updated to explain contrib vs core, or is that elsewhere?
I noticed that https://github.com/openedx/xblocks-core/blob/main/README.rst tracks the status of the extraction, and should probably be noted in the appropriate issue description.
Between "Ready to Use" and "Done", we have duplicated code/features, and I don't see any docs on expectations for changes during that transition time.

Do we expect that only xblocks-core will be updated, and legacy xblocks will get no new features?
Or are changes meant to be duplicated until we get to Done?
Will we do a manual sync check before getting to Done in case legacy was updated, but core was not?
Would fixes follow the same or a different process as features?
Thank you.

Navigation Menu

Repository navigation

[epic] edx-platform XBlock Extraction #34827

24 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[epic] edx-platform XBlock Extraction #34827

Description

Activity

irtazaakram commented on Jun 27, 2024

nsprenkle commented on Aug 6, 2024

farhan commented on Aug 7, 2024

24 remaining items

robrap commented on Sep 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions