HTML for the majority of the site is generated from Django/Wagtail templates and components.
This site has a styleguide, which can be refrenced for frontend development to note intended usage of exisitng styles and components.
CSS is generated from Sass. Styles are based on the mofo-bootstrap theme found under source/sass/mofo-bootstrap.
React is used à la carte for isolated component instances (eg: a tab switcher) since the site is not designed as a single page application. This precludes the need for Flux architecture, or such libraries as React Router.
To add a React component, you can target a container element from /source/js/main.js and inject it.
Django powers the backend of the site, and we use Wagtail with Django to provide CMS features and functionality.
If you are defining a new page class for the site, make sure it inherits both the Wagtail Page class as well as the FoundationMetadataPageMixin mixin. The first is a general Wagtail requirement, and the latter ensures that page metadata used for SEO and the like is (generally) correct.
We use wagtail-modeltranslations for CMS content localization. Please see its documentation for more information.
We currently don't have any A/B testing going on. We used to use wagtail-experiments but we're going to switch over to wagtail-ab-testing
All assets are stored on S3.
/
├── dest <- Compiled code generated from source. Don't edit!
├── network-api <- Django site code
│ ├── networkapi <- Django apps live within this directory
└── wagtailpages <- most of the pages using wagtail are here
│ └── templates <- page templates and overrides
├── locales <- Localized strings (Java .properties syntax)
├── scripts <- Scripts run by npm tasks
└── source <- Source code
├── images <- Image assets
├── js <- JS code
│ └── components <- React components
├── json <- JSON for static data sets
│ └── temp <- JSON pulled from web services. Don't commit!
└── sass <- Sass code