django-simple-bulma is a Django application that makes Bulma
and Bulma-Extensions available to use in your Django project with as little setup as
possible. The goal of this project is to make it as easy as possible to use Bulma with Django.
This project currently uses Bulma v1.0.4, and is automatically updated with every new release. Version 3.0 represents a major upgrade that focuses on actively maintained extensions and Bulma 1.0+ compatibility. If a new version has come out with features you'd like to make use of, please create an issue, and we will be happy to make a release to update it.
To get django-simple-bulma, up and running for your Django project, follow these simple steps:
Install it from PyPI with pip install django-simple-bulma (or add it to
your Pipfile)
In your Django projects settings.py file:
django_simple_bulma to your INSTALLED_APPS
INSTALLED_APPS = [
# ...
'django_simple_bulma',
# ...
]
django_simple_bulma.finders.SimpleBulmaFinder to your STATICFILES_FINDERS. This normally holds two default
handlers that you will probably want to keep, so unless you have any other custom Finders, it should look like this:
STATICFILES_FINDERS = [
# First add the two default Finders, since this will overwrite the default.
'django.contrib.staticfiles.finders.FileSystemFinder',
'django.contrib.staticfiles.finders.AppDirectoriesFinder',
# Now add our custom SimpleBulma one.
'django_simple_bulma.finders.SimpleBulmaFinder',
]
Run python manage.py collectstatic command in order to build Bulma and move it to your staticfiles folder. Please
note that you will need to use this command every time you make a change to the configuration, as this is the only way
to rebuild the Bulma css file. If you are not using collectstatic
, read up on it
and start using it.
This app works fine with Whitenoise, which is a great way to serve static files without needing to mess with your webserver.
django-simple-bulma should now be working! In order to import it into your template, first load the app
with {% load django_simple_bulma %}, and then use the {% bulma %} template tag. If you're planning on using icons,
you might also want to import FontAwesome by using {% font_awesome %}.
<head>
<!-- ... -->
{% load django_simple_bulma %}
{% bulma %}
{% font_awesome %}
<!-- ... -->
</head>
Bulma looks nice by default, but most users will want to customize its look and feel. For this, we've provided a super simple way to change the Bulma variables and to choose which Bulma extensions you want to load into your project.
In order to do this, we'll simply create a dictionary inside your settings.py called BULMA_SETTINGS, and configure
it there. Here's an example of what that looks like:
# Custom settings for django-simple-bulma
BULMA_SETTINGS = {
"extensions": [
"bulma-calendar",
"bulma-tooltip",
],
"variables": {
"primary": "#000000",
"size-1": "6rem",
},
"alt_variables": {
"primary": "#fff",
"scheme-main": "#000",
},
"output_style": "compressed",
"fontawesome_token": "e761a01be3",
}
You may here define any variable found on the Bulma variables
page, and you may use any valid SASS or CSS as the value. For example, hsl(217, 71%, 53%) would be a valid value for a
color variable, as would #ffff00. Please note that any syntactically incorrect values may prevent Bulma from building
correctly, so be careful what you add here unless you know exactly what you're doing.
If you want multiple different configurations of variables, then you should define them as separate themes. Define a new
theme by providing a key that matches the regex \w+_variables (e.g. alt_variables or dark_variables), unique
stylesheets will then be generated using the variables at that key.
To use these stylesheets in a template, pass the theme name to the {% bulma %} tag either as a
string {% bulma 'alt' %} or as a template variable {% bulma theme %}. When calling the bulma template
more than once in the same document (for example for implementing a dark theme switch), you will want to pass include_js=False to
at least one of these to prevent duplicate loading of JavaScript resources.
If the extensions key is not found, it will default to not loading any extensions. If you want all extensions, simply
set it to the string "all".
We currently support these actively maintained extensions compatible with Bulma 1.0+:
Note: As of this version, we have streamlined our extension support to focus only on actively maintained, Bulma 1.0+ compatible extensions. Many of the previously supported extensions are no longer maintained or compatible with modern Bulma versions.
If an extension you want to use is missing, feel free to create an issue and we will be happy to add it. Alternatively, add it yourself and create a pull request ( see this pr for some context on how to go about doing that).
The output_style parameter determines the style of the resulting CSS file. It can be any of "nested" (default)
, "expanded", "compact", and "compressed". It is recommended to use "compressed" in production as to reduce the
final file size.
The optional fontawesome_token parameter allows you to specify your personal FontAwesome kit, which is necessary for
FontAwesome v6 and up. This should be set to the identifier part of your FontAwesome kit script src parameter. For
example, if your FontAwesome kit looks like this:
<script src="https://kit.fontawesome.com/e761a01be3.js" crossorigin="anonymous"></script>
Then your fontawesome_token should be e761a01be3.
This is used by the {% font_awesome %} template tag to set up FontAwesome for you. If you don't specify
a fontawesome_token, the template tag will still work, but will then use an older version of FontAwesome (v5.14.0)
.
If you're writing custom SCSS for your application, django-simple-bulma provides a mechanism for compiling it for you.
This is provided mainly because django-simple-bulma may cause conflicts and issues with other tools to compile SCSS
for you.
To use this feature, please specify the custom_scss key when defining your BULMA_SETTINGS. This should be a list of
strings, containing relative paths to .scss files to be compiled.
BULMA_SETTINGS = {
"custom_scss": [
"css/base/base.scss", # This is okay
"my_app/static/css/base/base.scss", # This also is okay
"C:\Users\MainDawg\my_app\static\..." # Don't do this, though.
],
}
The default Django behavior when collecting static files is to keep the containing file structure for them when they're copied over to the final staticfiles directory. We do the same thing, so all directories and subdirectories will still be intact in your staticfiles folder after they've been collected.
Here's the strategy the finder uses:
static/, assume that the base path ends there and use the rest of the path as a relative path
to the resource.settings.py to search for the file using that relative path.ValueException asking you to double-check the filepath.django-simple-bulma v3.0 includes significant changes to support Bulma 1.0+ and focuses on actively maintained extensions only. This is a breaking change that requires migration steps.
The following extensions have been removed due to being unmaintained or incompatible with Bulma 1.0+:
bulma-badgebulma-carouselbulma-checkradiobulma-collapsiblebulma-coolcheckboxesbulma-dividerbulma-megamenubulma-pageloaderbulma-pricingtablebulma-quickviewbulma-ribbonbulma-sliderbulma-stepsbulma-switchbulma-tagsinputbulma-timelineOnly actively maintained, Bulma 1.0+ compatible extensions are now supported:
Remove any unsupported extensions from your configuration:
# Before (v2.x)
BULMA_SETTINGS = {
"extensions": [
"bulma-collapsible", # ❌ No longer supported
"bulma-calendar", # ✅ Still supported (new maintained version)
"bulma-tooltip", # ✅ Still supported
"bulma-tagsinput", # ❌ No longer supported
"bulma-badge", # ❌ No longer supported
# ... other removed extensions
],
# ... other settings remain the same
}
# After (v3.0+)
BULMA_SETTINGS = {
"extensions": [
"bulma-calendar", # ✅ Updated to maintained version
"bulma-tooltip", # ✅ Updated to maintained version
"bulma-responsive-tables", # ✅ New JustBoil extension
"bulma-switch-control", # ✅ New JustBoil extension
"bulma-radio", # ✅ New JustBoil extension
"bulma-checkbox", # ✅ New JustBoil extension
"bulma-upload-control", # ✅ New JustBoil extension
],
# ... other settings remain the same
}
If you were using removed extensions, here are specific, modern alternatives that work well with Bulma:
For form controls (checkradio, switch, slider):
<input type="range"> for sliders, styled with CSS custom propertiesFor carousel components:
For layout components (collapsible, steps, timeline):
is-hidden modifier with custom JavaScript toggle functionsFor UI elements (badge, ribbon, divider):
tag component or notification is-small for badge-like elements::before/::after pseudo-elements with Bulma colorshr element with custom CSS or title component stylingFor advanced components:
modal/dropdown componentsloader mixin and custom positioningmodal component and custom JavaScriptAfter updating your settings:
python manage.py collectstatic to rebuild your CSSIf you have custom CSS that depends on removed extensions:
@import statements referencing removed extensionsThis project uses UV for dependency management and development workflows. UV is a fast Python package manager that simplifies development setup.
Install UV (if you haven't already):
# On macOS and Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# On Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
# Or using pip
pip install uv
Clone the repository:
git clone https://github.com/python-discord/django-simple-bulma.git
cd django-simple-bulma
Install dependencies:
# Install all dependencies including dev dependencies
uv sync --all-extras
We use pre-commit hooks to ensure code quality. Install them with:
uv run pre-commit install
This will run our linting checks automatically before each commit.
sass installed, please note that it is incompatible with this project. There is a namespace
conflict between sass and libsass which will make django-simple-bulma crash when you attempt to do
a collectstatic. To solve this, just uninstall sass and use libsass instead.If you run into any other problems with this app,
please create an issue, and I will be happy to help
you with it. You can also find me on Discord as lemon#0001 at https://discord.gg/python.
FAQs
Django application to add the Bulma CSS framework and its extensions
We found that django-simple-bulma demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.