TOC
- Overview
- Architecture of portals
- Development Process
NOTE: This documentation is best read online through the repository clone on diffusion or github
The portals are static HTML/CSS/JS pages. However, they use a front-end development stack that includes templates, preprocessors and build-tools to achieve an optimized and performant output. We use Handlebars for HTML templates, PostCSS as a CSS pre-processor, and Gulp as build tool to stitch everything together.
Templates and source files are located in the src folder. The source files are populated with data from the data folder and processed using Gulp. During devlopment, the compiled but un-optimized assets remain in the src folder. During a production build, these assets are optimized and copied to the prod folder.
This diagram represents the flow of data and rough order of operation in the portals repository. The data is collected from multiple sources, processed and passed to the templates for rendering.
Portals repository dataflow diagram