Want to contribute? Some ideas:

[SKeeneCode]

Some people have been asking ways they can contribute - so here are some ways someone might want to help - in no particular order:

• some of the codebase for tornadofx lacks proper code documentation. Someone could pick a small part of tornadofx and ensure the code is well commented. Remember, comments should explain why not how and there is no need to comment code that is self-documenting.
• a code review to ensure the kotlin coding standards are followed. Here is one such example that did great work but ultimately was never merged: [Refactorization & Cleanup] Controls.kt tornadofx#824 someone may want to take this over for this repo, or do the same to another part of the codebase.
• features are welcome - although they shouldn't break existing functionality. Here's one that seems to have gone inactive Adding an option to make drawer with horizontal text tornadofx#1283 - likewise giving your thoughts/review on features waiting to be merged is also welcome (such as for Workspace footer implementation #30 ).
• some bug fixes for the original tornadofx should also be applied here (such as [#1318] Fix leaking fragments tornadofx#1319) - also reviewing bug fixes waiting to be merged (such as fix currentWindow keeping reference to old modalstage #32 ).
• tornadofx2 is hoping to upgrade to 1.4.32 soon (see Kotlin 1.4.x #26 ). Helping this IMO is higher priority.
• eventually I would like to see Split code into core and submodules for non-core code #5 renewed and finished.
• compatibility with other javafx controls libraries. The DSL builders tornadofx uses for javafx controls are great and it would be useful to expand that to other libraries such as controlsfx https://github.com/edvin/tornadofx-controlsfx but it hasn't been updated for a few years now. The other big library I can think of that could do with this treatment would be jfoenix.
• test test tests... never enough tests. If you want a bit of practice writing tests it wont be hard to find an area that could do with more.

That's all I can think of for now :)

[pavlus]

Regarding "a code review to ensure the kotlin coding standards are followed. ", I think it would be great to add CONTRIBUTION.md file to the root of the project, along with configuration file for code style.