Category customization

You are only able to enter custom suffix that will cause Misago to add custom css classes containing it to items on categories and threads lists. Misago defines few example classes out of the box that you may find in the docs.

I've found this approach better than writing complex forms for letting folk to click trough list and page styles. Template complexity is sane that way, and it spares me the rabbithole of "could you add form for customizing XYZ" requests. ;)

Have you looked at the html generated by Misago after setting the class? This very thread's in category that has "green" as its defined css class. This results in Misago adding page-thread-green css class to this page. So to style page-header-bg I can use .page-thread-green .page-header-bg selector in my CSS. This is same for category's threads list.

Loading custom CSS is possible by editing the misago/base.html and misago/categories/base.html templates. This is tricky tough because you'll need to copy them to your own forum's theme/templates directory as misago/base.html and misago/categories/base.html. This will make Misago load your copies instead of defaults. Now edit your theme/templates/misago/base.html and find this line:

{% include "misago/head.html" %}

Edit it to include your own custom block:

{% include "misago/head.html" %}
{% block extra-css %}{% endblock extra-css %}

Not edit theme/templates/misago/categories/base.html and find in it:

{% block title %}

Edit it to look like this:

{% block extra-css %}
<link href="{% static 'my-custom.css' %}" rel="stylesheet">
{% endblock extra-css %}


{% block title %}

Also find:

{% load i18n %}

And change it to:

{% load i18n staticfiles %}

Now create theme/static/my-custom.css file. After those modifications Misago should include it on category page. Likewise you may add your custom template block to other templates like misago/threads/thread.html to include custom css at thread view.

Looks like a bug in Misago then. I'll be releasing next alpha in few days, I'll have a look on this by then.

You should never hardcode /static/ url's - this will break your app the moment you'll change default static files store to something else, like S3 or just fingerprinted assets.

I don't see anything else to bring up here.