@opencraft/frontend-component-footer
v12.5.4
Published
Footer component for use when building Open edX frontend applications
Downloads
6
Readme
######################### frontend-component-footer #########################
|Build Status| |Codecov| |npm_version| |npm_downloads| |license| |semantic-release|
Purpose
A generic footer for Open edX micro-frontend applications. It includes a logo and an optional language selector dropdown.
Getting Started
Prerequisites
The devstack
_ is currently recommended as a development environment for your
new MFE. If you start it with make dev.up.lms
that should give you
everything you need as a companion to this frontend.
Note that it is also possible to use Tutor
_ to develop an MFE. You can refer
to the relevant tutor-mfe documentation
_ to get started using it.
.. _Devstack: https://github.com/openedx/devstack
.. _Tutor: https://github.com/overhangio/tutor
.. _relevant tutor-mfe documentation: https://github.com/overhangio/tutor-mfe#mfe-development
Requirements
This component uses @edx/frontend-platform
services such as i18n, analytics, configuration, and the AppContext
React component, and expects that it has been loaded into a micro-frontend that has been properly initialized via @edx/frontend-platform
's initialize
function. Please visit the frontend template application to see an example. <https://github.com/openedx/frontend-template-application/blob/3355bb3a96232390e9056f35b06ffa8f105ed7ca/src/index.jsx>
_
Environment Variables
This component requires that the following environment variable be set by the consuming micro-frontend.
LMS_BASE_URL
- The URL of the LMS of your Open edX instance.LOGO_TRADEMARK_URL
- This is a URL to a logo for use in the footer. This is a different environment variable thanLOGO_URL
(used in frontend-component-header) to accommodate sites that would like to have additional trademark information on a logo in the footer, such as a (tm) or (r) symbol.
Installation
To install this footer into your Open edX micro-frontend, run the following command in your MFE:
npm i --save @opencraft/frontend-component-footer
This will make the component available to be imported into your application.
Cloning and Startup
.. code-block::
- Clone your new repo:
``git clone https://github.com/openedx/frontend-component-footer.git``
- Use node v18.x.
The current version of the micro-frontend build scripts support node 18.
Using other major versions of node *may* work, but this is unsupported. For
convenience, this repository includes an .nvmrc file to help in setting the
correct node version via `nvm <https://github.com/nvm-sh/nvm>`_.
- Install npm dependencies:
``cd frontend-component-footer && npm ci``
- Start the dev server:
``npm start``
Usage
This library has the following exports:
(default)
: The footer as a React component.messages
: Internationalization messages suitable for use with@edx/frontend-platform/i18n <https://edx.github.io/frontend-platform/module-Internationalization.html>
_dist/footer.scss
: A SASS file which contains style information for the component. It should be imported into the micro-frontend's own SCSS file.
- onLanguageSelected: Provides the footer with an event handler for when the user selects a language from its dropdown.
- supportedLanguages: An array of objects representing available languages. See example below for object shape.
Customization via MFE config API
Other than the environment variables listed above, it is also possible to customize the footer via MFE config API <https://github.com/openedx/edx-platform/blob/master/lms/djangoapps/mfe_config_api/docs/decisions/0001-mfe-config-api.rst>
_. Below is the possible list of settings
.. code-block:: python
MFE_CONFIG = { # Update footer container styling "FOOTER_CUSTOM_STYLE": { "backgroundImage": "url(http://)", # to change opacity of background image # "backgroundImage": "linear-gradient( rgba(255, 255, 255, 0.85), rgba(255, 255, 255, 0.85) ) , url(http://)", }, # Update footer container styling via bootstrap classes "FOOTER_CUSTOM_CLASSNAMES": "py-5 px-4 text-center flex-column justify-content-center flex-wrap text-dark", # Update footer inner conatiner styling via bootstray classes "FOOTER_CONTAINER_CUSTOM_CLASSNAMES": "py-5 px-4 text-center flex-column justify-content-center flex-wrap text-dark" # Update footer logo styling "FOOTER_LOGO_STYLE": { "marginBottom": "2rem", }, # Override environment variable "LOGO_TRADEMARK_URL": "https://", # Add links to footer "FOOTER_LINKS": [ {"url": "https://openedx.org/terms-of-use/", "text": "Terms of service"}, {"url": "https://openedx.org/code-of-conduct/", "text": "Code of conduct"}, {"url": "https://openedx.org/privacy-policy/", "text": "Privacy Policy"}, ], # Update link container classes "FOOTER_LINKS_CONTAINER_CLASSNAMES": "flex-wrap", # Update link styling "FOOTER_LINKS_CLASSNAMES": "text-dark font-weight-bold", }
Examples
Component Usage Example
.. code-block:: javascript
import Footer, { messages } from '@opencraft/frontend-component-footer';
...
An example of minimal component and messages usage. <https://github.com/openedx/frontend-template-application/blob/3355bb3a96232390e9056f35b06ffa8f105ed7ca/src/index.jsx#L23>
_An example of SCSS file usage. <https://github.com/openedx/frontend-template-application/blob/3cd5485bf387b8c479baf6b02bf59e3061dc3465/src/index.scss#L9>
_
Development
Install dependencies::
npm i
Start the development server::
npm start
Build a production distribution::
npm run build
License
The code in this repository is licensed under the AGPLv3 unless otherwise noted.
Please see LICENSE <LICENSE>
_ for details.
Contributing
Contributions are very welcome. Please read How To Contribute
_ for details.
.. _How To Contribute: https://openedx.org/r/how-to-contribute
This project is currently accepting all types of contributions, bug fixes, security fixes, maintenance work, or new features. However, please make sure to have a discussion about your new feature idea with the maintainers prior to beginning development to maximize the chances of your change being accepted. You can start a conversation by creating a new issue on this repo summarizing your idea.
Getting Help
If you're having trouble, we have discussion forums at https://discuss.openedx.org where you can connect with others in the community.
Our real-time conversations are on Slack. You can request a Slack
invitation
, then join our community Slack workspace
. Because this is a
frontend repository, the best place to discuss it would be in the #wg-frontend
channel
_.
For anything non-trivial, the best path is to open an issue in this repository with as many details about the issue you are facing as you can provide.
https://github.com/openedx/frontend-component-footer/issues
For more information about these options, see the Getting Help
_ page.
.. _Slack invitation: https://openedx.org/slack .. _community Slack workspace: https://openedx.slack.com/ .. _#wg-frontend channel: https://openedx.slack.com/archives/C04BM6YC7A6 .. _Getting Help: https://openedx.org/community/connect
The Open edX Code of Conduct
All community members are expected to follow the Open edX Code of Conduct
_.
.. _Open edX Code of Conduct: https://openedx.org/code-of-conduct/
Reporting Security Issues
Please do not report security issues in public. Please email [email protected].
.. |Build Status| image:: https://api.travis-ci.com/edx/frontend-component-footer.svg?branch=master :target: https://travis-ci.com/edx/frontend-component-footer .. |Codecov| image:: https://img.shields.io/codecov/c/github/edx/frontend-component-footer :target: @opencraft/frontend-component-footer .. |npm_version| image:: https://img.shields.io/npm/v/@opencraft/frontend-component-footer.svg :target: @opencraft/frontend-component-footer .. |npm_downloads| image:: https://img.shields.io/npm/dt/@opencraft/frontend-component-footer.svg :target: @opencraft/frontend-component-footer .. |license| image:: https://img.shields.io/npm/l/@opencraft/frontend-component-footer.svg :target: @opencraft/frontend-component-footer .. |semantic-release| image:: https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg :target: https://github.com/semantic-release/semantic-release