Getting such feature into Misago is little more complex than this. Not only you'll need to edit JS for UI to support such feature, but you'll also have to implement it in application's backend. This would involve:
- adding "answer" field on thread model that would point to post model (or be null)
- adding its serialization to JSON api
- writing JSON api for setting and changing selected answer
Assuming that one's familiar with the technologies involved and the codebase, and will not implement feature in configurable matter, or include tests suite for it, one may have relatively okay implemementation after 8-12 hours of work. It's much harder to estimate somebody new to codebase, or without experience with technology stack.
Still, if you persist, you are up to great learning experience.
As for starting up with the frontend, I would start with setting up Misago locally for development, following project's readme. Next, I would clone Misago near to your project, uninstall Misago from your virtualenv and create directory named
misago that would be symlinked to
misago directory in cloned repo. That way your Misago forum will use codebase you've just cloned instead of one buried within your virtualenv. Next, I would edit cloned
frontend/gulpfile.js to point to my dev installation's
theme directory, so my custom frontend would be easily accessible for deploying, instead of being buried in Misago's source.