# MFE for custom pages?

**URL:** <https://discuss.openedx.org/t/mfe-for-custom-pages/18526>\
**Category:** Frontend\
**Tags:** ulmo\
**Created:** [March 3, 2026, 6:17pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526 "2026-03-03T18:17:58Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mboisson](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/mboisson/32/7551_2.png) [@mboisson](https://discuss.openedx.org/u/mboisson)\
**Post date:** [March 3, 2026, 6:17pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/1 "2026-03-03T18:17:58Z")

</div>

Hi,

Is there a plan to get custom pages through MFEs in a future version of EdX ? It looks like those pages are not styled correctly. For example:

> **[Aide-mémoire | CIP101 | evolo](https://edx.evolo.calculquebec.cloud/courses/course-v1:CQ+CIP101+v1/291693addb8b4ad9b484253203e1aec7/)**

---

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [March 3, 2026, 8:10pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/2 "2026-03-03T20:10:00Z")

</div>

Hey!

Yes, this is a known issue. It’s [on our list of things that are left to port over to MFEs](https://openedx.atlassian.net/wiki/spaces/COMM/pages/4262363137/MFE+Rewrite+Tracker): look for “Custom Pages”. The first hit is the Studio interface, which you likely found. The second hit describes the lack of a proper frontend in the Learning MFE.

---

<div class="post-metadata">

**Author:** ![mboisson](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/mboisson/32/7551_2.png) [@mboisson](https://discuss.openedx.org/u/mboisson)\
**Post date:** [March 3, 2026, 8:14pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/3 "2026-03-03T20:14:56Z")

</div>

Ok, thanks.

I don’t think I know the code base enough to write it myself, but I am happy to help achieve it whatever way I can.

---

<div class="post-metadata">

**Author:** ![mboisson](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/mboisson/32/7551_2.png) [@mboisson](https://discuss.openedx.org/u/mboisson)\
**Post date:** [March 4, 2026, 3:45pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/4 "2026-03-04T15:45:07Z")

</div>

@arbrandes it looks like the “bookmarks” page is missing from the list of things that are left to port to MFEs. [Bookmarks page not in MFE?](https://discuss.openedx.org/t/bookmarks-page-not-in-mfe/18509)

---

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [March 16, 2026, 2:45pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/5 "2026-03-16T14:45:29Z")

</div>

Yes, that seems to be a feature that wasn’t ported yet. I just added it to the list. Thank you!

---

<div class="post-metadata">

**Author:** ![mboisson](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/mboisson/32/7551_2.png) [@mboisson](https://discuss.openedx.org/u/mboisson)\
**Post date:** [April 13, 2026, 2:54pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/6 "2026-04-13T14:54:31Z")

</div>

@arbrandes

I also do not see the “about”, “donate”, “tos”, and other static template pages in an MFE, nor listed ?

> [@Static pages (about, blog, donate, etc.) MFE URLs?](https://discuss.openedx.org/t/static-pages-about-blog-donate-etc-mfe-urls/18786/2):
>
> I think I found them, they are not under an MFE. Apparently at edx.\<domain\>/about and such. Is there any plan to port them to an MFE ?

---

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [April 15, 2026, 2:40pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/7 "2026-04-15T14:40:54Z")

</div>

I’m not certain any of those instance-specific pages are going to be ported. I believe the expectation at the moment is that the operator should just link out somewhere else.

But this is ultimately a call that a lowly developer like myself can’t make. 😅@jmakowski or @sarina, what’s Product’s take on this?

---

<div class="post-metadata">

**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\
**Post date:** [April 15, 2026, 2:57pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/8 "2026-04-15T14:57:41Z")

</div>

What would it take for custom pages to be in the learning MFE? The experience now is not great, and it (naively) seems kinda easy to shove a custom page into the learning MFE rather than falling back to the django template (if that’s what’s going on here?)

Sorry I’m kinda dumb on this but I thought that eventually we want to support all available features in the MFEs, so we can remove all the legacy django templates.

---

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [April 15, 2026, 3:08pm UTC](https://discuss.openedx.org/t/mfe-for-custom-pages/18526/9 "2026-04-15T15:08:59Z")

</div>

This time I gave my take on the _other_ thread, lol:

> [@Static pages (about, blog, donate, etc.) MFE URLs?](https://discuss.openedx.org/t/static-pages-about-blog-donate-etc-mfe-urls/18786/6):
>
> (Disclaimer: this is just my personal opinion as a developer.) Giving operators the ability to present arbitrary externally-hosted content sandwiched between the existing header and footer does makes sense. And yes, an iframed page would solve that. As a matter of fact, this will be explicitly possible in Verawood using the new frontend-base app architecture (which I’m rushing to get ready as we speak sweat_smile). An operator will be able to create arbitrary routes and pages to go with th…
