Where should shared CSS/JS assets for code.djangoproject.com live?

Django Internals
1

Hi everyone,

I’m currently working on the Dark Mode implementation for code.djangoproject.com as part of GSoC 2026.

While setting up my local environment, I noticed that several CSS and JavaScript assets used by code.djangoproject.com are copied from djangoproject.com during development. The current README instructions include commands such as:

cp ../djangoproject.com/djangoproject/static/css/*.css trac-env/htdocs/css/
cp ../djangoproject.com/djangoproject/scss/_utils.scss scss/
cp -rT ../djangoproject.com/djangoproject/static/js trac-env/htdocs/js

This made me wonder about the long-term direction for these shared frontend assets.

Should the CSS/JS that power the Trac instance continue to be maintained in djangoproject.com and copied into code.djangoproject.com, or would it be preferable for code.djangoproject.com to maintain its own copies/assets independently?

Since I’m working on styling-related changes, I’d like to better understand the intended architecture before making further modifications.

Any guidance on the preferred approach would be greatly appreciated.

Thanks!

1 Like
Why does local django docs have a different styling/theme than the official one?
2

Should the CSS/JS that power the Trac instance continue to be maintained in djangoproject.com and copied into code.djangoproject.com, or would it be preferable for code.djangoproject.com to maintain its own copies/assets independently?

I feel like the shared assets are in djangoproject.com and the code.djangoproject.com specific assets are in scss/trachacks.scss
I think for now, this is probably ok? Unless you want to improve this process

3

Hi Sarah,

Thanks for the suggestion and clarifying the architectural intent!

That makes total sense. I will stick to that approach and keep all of the Trac-specific CSS modifications localized within code.djangoproject.com inside scss/trachacks.scss.

Appreciate the guidance!

1 Like