Looking for Best Practices on Customizing Open edX for Unique Use Cases With Jira

Hey everyone! :wave:

I have been working with Open edX for Jira for a while now, but I have recently been tasked with customizing it to fit some unique use cases, and I could use a bit of advice from the community here. :pray:

What are some of the best practices or key things to keep in mind when making custom changes to the platform, do the work in Jira? I am particularly interested in any tips on plugin development, user experience customization, or managing updates when you’ve made a lot of changes. When I was Googling for the same I came across these resources/articles OEP-23: Style Customization — Open edX Proposals 1.0 documentation Jira Interview Questions however they are good but I want to learn more from community members.

Would love to hear from anyone who’s had to tweak Open edX to fit non-standard scenarios. Any resources, guides, or personal experiences would be super helpful!

Thanks in advance! :blush:

Hi @noahrodriguez and welcome! I think it would be helpful to better understand what you’re trying to do with the platform. “Non-standard scenarios” feels quite broad. In general I recommend keeping your platform up-to-date (we’re working on releasing Sumac in December) and leveraging extension points such as LTI and XBlock. In Sumac we’ve got some frontend plugin slots coming, and in Teak we’ll be debuting Design Tokens for better comprehensive theming. Making modifications to the core code makes it difficult to keep your platform up to date and leverage new and improved extension points (also, we only patch the most recent release, so you’re losing out on security patches and bugfixes by running older versions).