-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README file #55
README file #55
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## devel #55 +/- ##
===========================================
- Coverage 92.61% 82.36% -10.26%
===========================================
Files 7 7
Lines 447 448 +1
===========================================
- Hits 414 369 -45
- Misses 33 79 +46 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @JagGlo,
Firstly, I want to thank youn for the effort and dedication you've put into creating the documentation for the project, it shows!
After reviewing the documentation, I believe there's an opportunity for us to further align it with the strategic vision of the unbiased project. While the R package component is undoubtedly important and will be thoroughly documented through GitHub Pages and pkgdown, the core value and unique selling proposition of unbiased actually lie in its API, DB integration, and our development practices, especially our commitment to extensive code coverage. These elements are what truly differentiate unbiased as a production-ready solution for integration with eCRF / EDC software.
Therefore, I suggest we pivot our documentation focus towards highlighting the API, DB, and development practices. By doing so, we can more accurately showcase unbiased's strengths and its readiness for critical applications in clinical research environments. This approach will not only differentiate our project but also clearly communicate its main benefits and applications to our target audience.
delate comparative part
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work, let's create a followup issues if those places with remarks were not planned / intended.
closes #31