The Front End#
Pegasus’s front-end architecture is a hybrid model, with a standalone front-end codebase that is compiled and served inside Django templates.
Pegasus’s styles use either the Bootstrap or Bulma CSS frameworks, and building the CSS files is included as part of the front-end build pipeline. For more details on CSS in Pegasus, see the CSS documentation.
The source front-end files live in the
assets directory, while the compiled files
get created in the
Generally you should only ever edit the front-end files in
and compile them using the instructions below.
Prerequisites to building the front end#
Pegasus is developed and tested on the latest LTS releases, which (at the time of this writing)
are Node version 14.16.1 and npm 6.14.12.
Later versions may work, but aren’t well-tested.
Also it’s recommended to use
nvm to manage different node/npm environments more easily.
nvm is essentially
virtualenv for Node.js/npm.
Getting started should be as simple as running:
In your project’s root directory. This will install all the dependencies necessary to build the front end.
It will also generate a
It is recommended that you add this file to source control for consistency across installations.
Building in Development#
Whenever you make modifications to the front-end files you will need to run the following command to rebuild the compiled JS bundles and CSS files:
npm run dev
You can also set it up to watch for changes by running:
npm run dev-watch
Building for production#
To build for production, run:
npm run build
This will compress your files, remove logging statements, etc.
Long-term best practices#
For ease of initial set up, the front-end bundle files are included with the Pegasus codebase. This allows you to get up and running with Pegasus without having to set up the front-end build pipeline.
However, keeping these files in source control will typically result in a lot of unnecessary changes and merge conflicts.
so they are no longer managed by source control, and have your developers build them locally using the steps above.
For production deployment, see the production guidance on this.