Static pages (about, blog, donate, etc.) MFE URLs?

Site Operators
,
1

Hi,

What is the URL of the “static pages” ( edx-platform/lms/templates/static_templates at release-ulmo · edx/edx-platform · GitHub ) ? I cannot find them. Do they require a special MFE ?

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 ?

3

@arbrandes mind weighing in on this one?

4

Replied on another thread. Unless Product says otherwise, I don’t think those templates are ever going to be ported.

5

Hum, those are presumably kind of a big deal for some sites ? Couldn’t they be iframed into some general MFE page ? All they really need is to get the proper headers and footers from MFE.

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 them, all reusing the header/footer if they want to.

It’s actually because of this that I think those specific pages will probably never be ported: they won’t need to be.

7

Thanks @arbrandes - to be clear, this won’t be possible in Verawood for the learning MFE though, yes?

8

As far as I know, those URLs are only seen in the Django footer, and the current version of frontend-component-footer (which is what the Learning MFE uses) does not actually have any of them.

But given that frontend-component-footer (which the Learning MFE uses) is configurable (via FooterSlot), all an operator will have to do to get a React About page in Verawood is:

  1. Create a frontend-base app that implements it
  2. Add a link to it using FooterSlot
  3. Wire both up in a single Tutor plugin
9

Follow-up question:

Can’t we just offer those apps out of the box?

Yes, of course. But the combination of a) them being so simple, but also b) the fact they’ll likely be completely different for each instance, makes me think we’re better off making them template apps that users can optionally fork and modify to their liking.

10

Ah, sorry I was mixing threads. I thought we were talking about custom pages (which appear as a tab in the Learning MFE) not the footer links. You’re correct on this.