Release 2.6.0 - Multiple theme support

This solves a major problem with multiple themes and theme switching outlined in #86. In 2.5.0, this would produce duplicate .js files, but in 2.6.0 this should no longer be happening, which should allow the development of multiple themes, for example if your site needs a dark theme and a light theme to switch between.

What's Changed

• Allow omitting JS resources on templatetag call by @jchristgit in #94

New Contributors

• @jchristgit made their first contribution in #94

Full Changelog: v2.5.0...v2.6.0

Release 2.5.0 - Dynamic stylesheet IDs

This release adds an id to the stylesheet element that you add by doing {% bulma %}, which makes it easier to set up theme switching when you have multiple themes defined.

It also bumps Bulma to v0.9.3, and bumps all extensions to the latest versions.

What's Changed

• Added hyperlinks to extensions list in README. by @max1666 in #79
• Add id to stylesheet element by @GDWR in #84

New Contributors

• @max1666 made their first contribution in #79
• @GDWR made their first contribution in #84

Release 2.4.0 - Ohhh, so that's how submodules work!

Turns out I've been using submodules under some bad assumptions. I assumed submodules would just stay up-to-date without any human intervention, but as it turns out, that's not the case.

So, we haven't actually updated the Bulma version since August 2020. Sorry about that.

To solve this, I had to run git submodule update --recursive --remote, and this went through and updated all the submodules to the latest commit.

So now, django-simple-bulma is finally running Bulma 0.9.2. 🎉

Release 2.3.1 - Custom SCSS bugfix

A stupid bug made it into 2.3.0 - only 1 simultaneous custom SCSS was supported!

This release fixes that bug, and also has a fix for the bug reported in #71.

Release 2.3.0 - Better custom SCSS!

This release adds smarter handling for custom SCSS.

This resolves two problems with the previous implementation:

• Deeply nested static files were not supported by the previous implementation. These would in fact crash when we tried to mkdir the relative folder structure, because the os.mkdir didn't pass parents=True to allow creating the full path.

• We required the static folders to be defined in STATICFILES_DIRS, even though they were in standard locations. This is kind of smelly, because Django will find all files as long as they are in a static folder inside the app root, for example.

The new implementation just uses all the Finders you have activated to solve this problem, even if they're custom Finders with highly tailored find methods. This makes the implementation far more resilient and flexible.

✨ This change should be fully backwards-compatible. ✨

Release 2.2.0

This release adds an extension for handling modal events. Yet another quality of life improvement so that you don't need to implement this yourself. It also bumps the Bulma version to v0.9.2

• This release bumps Bulma to version 0.9.2
• Add bulma-modal custom extension

Release 2.1.0

You can now define multiple themes! This will allow your app to have a dark theme and a light theme, or to solve accessibility problems easily. It also solves a few minor issues, and bumps the Bulma version to v0.9.1.

• This release bumps Bulma to version 0.9.1
• Support for multiple themes
• Update tooltip extension submodule to new repo
• Guarantee DOM loading in bulma-dropdown.js
• Add index.sass to sass_files_searches

Release 2.0.3

A bugfix release with fixes an issue with bulma-megamenu. Because of a typo in MANIFEST.in, this was not being included in the source distribution.

Release 2.0.2

Another minor change to the release workflow, this time to introduce recursive submodule checkouts.

Release 2.0.1

This release will hopefully resolve the bug we're having described in #61

Specifically, it changes the release workflow so that we are checking out all the submodules before we try to build the source distribution.