CSS handled by SCSS. It uses
gulp to process these files and prepare them for
All of the static files are located in
warehouse/static/ and external
libraries are found in
Static files should be automatically built when
make serve is running;
however, you can trigger a manual build of them by installing all of the
npm install and then running
When deploying changes to the frontend, to see the changes immediately it is necessary to purge the cache.
Individual pages can be purged from the command line by issuing a
curl -XPURGE https://pypi.org/the/page/to/purge
All HTML pages can be dropped from the cache by purging the
surrogate key via our CDN provider.
The entire cache can be purged by issuing a “Purge All” via our CDN provider.
Purging the cache is not usually necesasry when making frontend changes, unless it would be unacceptable for the site to simultaneously have an “old” version of some pages, but the “new” version of others.
|Chrome||Current, Current - 1|
|Firefox||Current, Current - 1|
|Edge||Current, Current - 1|
|Opera||Current, Current - 1|
HTML Code Style¶
Exceptions to these rules include:
- Protocols can be included in links - we prefer to include
- All HTML tags should be closed
More information on how BEM works can be found in this article from CSS Wizardry.
SCSS Style and Structure¶
Warehouse follows the Airbnb CSS/Sass style guide,
with the exception that JS hooks should be prefixed with
Our SCSS codebase is structured according to the ITCSS system. The principle of this system is to break SCSS code into layers and import them into a main stylesheet in an order moving from generic to specific. This tightly controls the cascade of styles.
The majority of the SCSS styles are found within the ‘blocks’ layer, with each BEM block in its own file. All blocks are documented at the top of the file to provide guidelines for use and modification.