Thanks for feedback @rokkirokki. Could you provide more details on what problems or headscratchers with customizing Misago look exactly are you having now?
I agree that this field is lacking currently, but different folk have different backgrounds and problems, so I'm trying to get a clearer picture here for how can I make this easier for you and your team.
Well, making custom looks need some tinkering with code and forking such, which is out of the question for many. But still many would want to make their forums look their own, you know. This might be the fact that people are going for FlaskBB for example because it's easy to customize every template it has. They also have community made themes. this would be big thing for many you see.
In fact at the moment only thing that is still kinda tipping the scale towards FlaskBB, but I'm not making that decision. It's totally up to our sysadmin to choose which we start to run and that's made only based on technical terms, not with any fancypansy blingbling for the sake of looks :)
So if yours is satisfactory for him we go for Misago but if he decides that FlaskBB is fine by his standards (he's a bit OCD on the stuff running on his box you see :) then it's going to be that.
I'd suggest to look into this and take this seriously in consideration. I'm sure it would be big thing to boost popularity of your efforts.
Otherwise all looks fine and dandy! So keep up the good work!
Thanks for more context!
I understand where you are coming from, but the way I feel about this currently, there is a split between web developers that embraced modern approach (eg. node.js, bundlers, js and css processors) and old ones (I just find the file, edit it, taadaa!).
I will make things easier for people running their communities on Misago, but sadly it will never be the level of "just edit the template and it works". Misago is JavaScript application consuming the API from Python application. If you want to customize generated HTML, you need to fork the frontend. Currently, this requires you to fork the entire repo, but when new frontend hits, you will have to fork only the repo with frontend. Next improvement will be that you won't really have to really modify whole that lot in your fork. You may want to stick to editing just the Sass variables for theme colors, generate output css file, and then upload just that CSS file on your site via admin control panel.
Or if you want to add extra CSS bit to your site, say override the CSS for .navbar .navbar-brand. Admin panel will have simple editor letting you add extra CSS snippet on top of already-existing CSS.
This is the course I'm taking with how customizing Misago will look like. Maybe we will have web UI for changing the SCSS variables without having to do it on your machine, don't know yet.
That would be excellent improvement if one could do basic customization via UI without any hassle. Colors and such. Of course full theming always needs hack'n'slash and it's just the way it is. If only there would be even couple dozen of community made themes for not-so-savvy people to choose from.
Of course you need to decide what you want for your project and follow that path, it's of course how it is and should be.
Just throwing some spare cents here...
You don’t have to make excuses for yourself. Any argument-backed feedback is valuable and appeeciated, yours included. :)
I understand that customization is main pain, and I will be trying to make it as easy as possible for people - I am simply unable to inplement improvements at pace I would want to :C
Thanks!
I totally understand this. Especially when there isn't an army of developers behind the project. So relax and keep it good and proper rather than haste and release some gibberish!
Any news about now front end, i am waiting you release it
Sorry. Don't expect news about new frontend before summer comes. New frontend requires GraphQL API, and I haven't started working on that.
Next release will be Misago 0.20. It will be a big release that adds those features:
settings.py to admin panel.
Good news, applause for perseverance.
@123 long time no see ;)
I'll be posting year summary and new roadmap likely first week of 2019.