formr is open source software. You are welcome to help improve it. Depending on your technical background, there are several options.
If you know the relevant software stack (e.g., R, PHP, JavaScript, CSS, HTML), you can send us pull requests on Github to quash bugs, add features, add tests, etc.
If you want to test formr or contribute to its development, follow our instructions.
The setup instructions are not suitable for production, i.e. running a secure formr installation on the public web.
formr allows for very complex study designs. Not all of the potential use cases are documented. In some places, the documentation is out of date or hard to understand.
If you have implemented a study in formr, especially if you've done something difficult, we and other users would greatly appreciate, if you write up a case study.
Ideally, that would consist of some description of the study design, a link to the preprint or publication if applicable, as well as the exported study JSON file (Run->Export).
We use Github Discussions for community support. We try to find the time to answer questions. If you answer some of the questions we didn't get to yet, we'll try especially hard to answer your own questions. We also appreciate if you post back with the solution, if you found one yourself.
Unfortunately, our documentation currently lives in four places:
- The old Google Group which we closed down because of the spam.
- The new Github Discussions
- The repository Wiki which is intended for case studies, brief tutorials, frequently asked questions, and so on.
- The documentation on the website itself, which is accessible while using formr.
Editing the Github and the Wiki should be easy. We use Markdown, which is basically plain text.
The documentation files for the website are on Github. Even if you are not a technical person, the documentation is just plain HTML, so easy to edit. You can edit it directly on Github using the "Pencil" button. This will create a pull request, i.e. we get a chance to review your change before it makes it into the website.
We appreciate any efforts to move questions/solutions from the Google Group to the Wiki or website documentation, or from the Wiki to the website documentation.