Is it expected that the “Bookmark” page is not part of an MFE ? This is in Ulmo.
I am talking about this page:
courses/course-v1:CQ+CIP101+v1/bookmarks/
which is reached by clicking the “Bookmarks” link in the “Course tools” of the course’s home page (i.e. learning/course/course-v1:CQ+CIP101+v1/home)
Yes facing the same issue, As the bookmark is in the django pages running at different port can we create a bookmark page in the mfe?
Facing issue while the lti launch as the bookmark page is not in the mfe it redirects to another page insted of opening in the iframe
Is there any approach that we can move the bookmarks page from the django page to mfe pages.
Yes, this is a known issue. It’s on our list of things that are left to port over to MFEs: look for “Bookmarks".
Unfortunately it’s not on our team’s priority list, but we’d gladly accept a contribution to the codebase.
Is there any referance how we can move the django pages to the mfe?
Please if you can share some document or any pr that changes the page from the django to mfe.
@Sliver_Horizon, unfortunately there is no step-by-step reference to port Django pages to React apps, and there’s no single PR, either: most pages have been ported as part of overarching projects, each with their own requirements. Take a peek at the board of a current Django port under way: the Instructor Dashboard.
That said, if you were to start porting the bookmarks feature (which would be awesome), my recommendation would be to start familiarizing yourself with the frontend-app-learning codebase, as this is where the page would likely go. I’d also look into what building blocks we use to develop modern frontend features in the Frontend Technology Selection section of OEP-0067: frontend-app-learning is one of the oldest React SPAs we have, and not everything in it is exactly up-to-date.
It shouldn’t be rocket science: it looks scary at first, but the Learning MFE is just a regular React app, for the most part.
Otherwise, you will have to understand how the feature works from the edx-platform side, and figure out how to expose new APIs to the frontend if they’re not already there. In other words, it’s likely you’ll have to modify the backend to make this work, too.