You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make footer links easily customizable, enabling the addition of custom navigation links, the organization’s logo, copyright information, and legal links.
Context & Background (in brief, if a Product Proposal is linked above)
Legacy LMS allows for the configuration of footer elements such as navigation links, the organization’s logo, and legal links. However, the MFE footer does not currently support this functionality. At present, the only way to achieve this is by forking the footer component repository, which is both difficult and time-consuming to maintain. The goal is to make the footer fully customizable, enabling the addition of custom navigation links, the organization’s logo, copyright information, and legal links.
Scope & Approach (in brief, if a Product Proposal is linked above)
Abstract
Make footer links easily customizable, enabling the addition of custom navigation links, the organization’s logo, copyright information, and legal links.
This replaces the proposal #324
Detailed Product Proposal
https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4512514079/Proposal+Customizable+Footer+for+LMS+CMS
Context & Background (in brief, if a Product Proposal is linked above)
Legacy LMS allows for the configuration of footer elements such as navigation links, the organization’s logo, and legal links. However, the MFE footer does not currently support this functionality. At present, the only way to achieve this is by forking the footer component repository, which is both difficult and time-consuming to maintain. The goal is to make the footer fully customizable, enabling the addition of custom navigation links, the organization’s logo, copyright information, and legal links.
Scope & Approach (in brief, if a Product Proposal is linked above)
Following the configuration option proposed in the discussion https://discuss.openedx.org/t/plugin-slots-vs-configuration/13009
Value & Impact (in brief, if a Product Proposal is linked above)
At present, the only way to achieve this is by forking the footer component repository, which is both difficult and time-consuming to maintain.
Milestones and/or Epics
Update the PR openedx/frontend-component-footer#403 to follow the proposals in in the discussion https://discuss.openedx.org/t/plugin-slots-vs-configuration/13009
Named Release
Teak
Timeline (in brief, if a Product Proposal is linked above)
This shouldn't take more than a week once everyone is in agreement about the implementation.
Proposed By
MIT Open Learning
Additional Info
No response
The text was updated successfully, but these errors were encountered: