This repository is a template for Open edX micro-frontend applications. It is flagged as a Template Repository, meaning it can be used as a basis for new GitHub repositories by clicking the green "Use this template" button above. The rest of this document describes how to work with your new micro-frontend after you've created a new repository from the template.
After copying the template repository, you'll want to do a find-and-replace to
replace all instances of frontend-app-test with the name of
your new repository. Also edit index.html to replace "BL Dashboard Test"
with a friendly name for this application that users will see in their browser
tab.
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.
In the following steps, replace "[PLACEHOLDER]" with the name of the repo you created when copying this template above.
- Clone your new repo:
git clone https://github.com/openedx/frontend-app-[PLACEHOLDER].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.
Install npm dependencies:
cd frontend-app-[PLACEHOLDER] && npm install
Update the application port to use for local development:
Default port is 8080. If this does not work for you, update the line PORT=8080 to your port in all .env.* files
Start the dev server:
npm start
The dev server is running at http://localhost:8080 or whatever port you setup.
Move README-template-frontend-app.rst to your project's README.rst
file. Please fill out all the sections - this helps out all developers
understand your MFE, how to install it, and how to use it.
This section concerns development of frontend-app-test itself,
not the templated copy.
It should be noted that one of the goals of this repository is for it to
function correctly as an MFE (as in npm install && npm start) even if no
modifications are made. This ensures that developers get a practical working
example, not just a theoretical one.
This also means, of course, that any committed code should be tested and subject to both CI and branch protection rules.
The source for this project is organized into nested submodules according to the Feature-based Application Organization ADR.
Production Build
The production build is created with npm run build.
Please see refer to the frontend-platform i18n howto for documentation on internationalization.
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-app-test/issues
For more information about these options, see the Getting Help page.
The code in this repository is licensed under the AGPLv3 unless otherwise noted.
Please see LICENSE for details.
Contributions are very welcome. Please read How To Contribute for details.
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.
All community members are expected to follow the Open edX Code of Conduct.
The assigned maintainers for this component and other project details may be
found in Backstage. Backstage pulls this data from the catalog-info.yaml
file in this repo.
Please do not report security issues in public, and email [email protected] instead.