Case file — PRJ-002
EDX.
Custom plugin and widget development supporting the enterprise arm of one of the world’s largest online learning platforms.
The brief
The edX enterprise team needed custom components their CMS didn’t ship with: interactive widgets and plugins that had to sit cleanly inside an established codebase and survive platform updates.
The build
We built the plugins to the platform’s own conventions, documented them so the in-house team could maintain everything without us, and kept each component isolated so updates upstream never break the work.
Scope of work
- S-01Development
Hand-built front end on a clean stack: fast to load, documented, and readable by the next developer.
- S-02Custom plugins
Components written to the platform's conventions, isolated so upstream updates never break them.
- S-03Interactive widgets
Self-contained interface pieces, documented for the in-house team to deploy and maintain.
The details that mattered
- House conventions, not ours. Every component follows the platform's existing patterns so it reads as native code.
- Update-proof isolation. Plugins are sandboxed from core, so platform releases ship without breaking the custom work.
- Documentation as deliverable. The in-house team runs everything today without us on retainer.
Quick answers
Do you work inside existing enterprise codebases?
Yes. The EDX work was written to the platform's own conventions and handed over documented, so the internal team maintains it.
Can you build custom plugins for our platform?
If it has an extension model, we can build to it: WordPress, WooCommerce, Shopify and custom stacks included.