Currently what we can think of:

• Generator/renderer for QGIS report
• QGIS expression shortcut for common FbF elements

There might be more along the way

• Make python3-oq-engine-master depends on NFS server (this should be already the case, due to shared_dir)
• Make python3-oq-engine-worker a standalone package that just contains init scripts for celery and add dependency on NFS client (this should be already the case, due to shared_dir)
• Init scripts installed by python3-oq-engine-worker should not be enabled at boo

The tidyrisk pkgdown sites should have a prominent "part of tidyrisk" link in the header, similar to the tidyverse sites. Explore how the tidysite template accomplishes this and adapt the technique (note that tidysite is (C)rstudio with no open license).

Through Docker, users can conveniently run riskParityPortfolio directly on their favorite browsers. But currently there is no documentation on our side on how to initialize the Docker container, though. We should have a simple tutorial on that.

@keblu we should update the way people cite the package; check my 3 points added to the github page. I follow David Hsieh practice. We should now push so that people cite our contribution. Please fix the webpage in line with Github. Thx

The existing MDK documentation on the docs site is poor and inadequate

https://oasislmf.github.io/docs/oasis_mdk.html

and there is no user guide with examples for the different MDK commands and subcommands. A simple quickstart guide using PiWind would be an enhancement.

1. Issue: When user click on Submit dataset and then OK, he is re-directed on a blank Submit data page.
   Fix: When user click on Submit dataset and then OK, re-direct to Dataset detail page of the submitted dataset.

Patchwork is now stable for multigrob alignment. Remove ggpubr calls in favor of patchwork.

This is a proposed iteration plan for finalizing EWEA(Early Warning and Early Action) tool

Simple Legend annotations

🚧 TODO

👷‍♂️ :construction_worke