Covid Open Survey (CO-OP Survey) project. Design and front-end development. Dev fork of: https://github.com/gedankenstuecke/opensurvey https://www.opencovid.care
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
nicolas arduin 138d91720b Sketch source file 1 month ago
_design Sketch source file 1 month ago
locale updated translations after alice 5 months ago
main better description 5 months ago
open_survey some translation done! 6 months ago
src add anneke's website 6 months ago
static added logos in the footer 6 months ago
.gitignore add de & es locale 6 months ago
LICENSE Create LICENSE 8 months ago
Pipfile get app together 8 months ago
Pipfile.lock Bump django from 3.0.6 to 3.0.7 7 months ago
Procfile get app together 8 months ago
README.md Add handling of "onboarding event already exists on OpenClinica" on login if user already has created an account and deleted it before 6 months ago
dump.rdb correct open humans links 6 months ago
env.sample adds basic export task and needed variables 7 months ago
manage.py initial django commit 8 months ago
package.json Front-end design start. 6 months ago
postcss.config.js Front-end design start. 6 months ago
yarn.lock Bump lodash from 4.17.17 to 4.17.19 6 months ago

README.md

Demo of how Open Humans to OpenClinica workflow can work

Install

Assumes you have a basic understanding of how Django, pipenv, & heroku work:

  • pipenv install
  • pipenv shell
  • heroku local:run python manage.py migrate
  • heroku local

Web-server should be up on 127.0.0.1:5000

Setup

Copy the env.sample as .env and fill in the missing bits. Required:

  • An Open Humans project
  • Having a Participate enabled Open Clinica survey and the corresponding token to add participants etc.

Demo deployment runs on https://opensurveytest.herokuapp.com/

Logging in with Open Humans will:

  • Create Open Clinica participant
  • Schedule first survey for them
  • Get participant access survey_token
  • Email this via Open Humans to just registered participant

Design dev

Assumes you have a basic understanding of how node and yarn/npm work.
Node version used: 12.16.1

We use PostCSS to enhance browser compatibility, accessibility and preformances.
A package.json and a postcss.config.js config file exist at the document root. Add or remove plugin from there.

In order to edit the styles, you need to:

  • run yarn install or npm i
  • edit the styles in src > css > parts
  • run yarn watch or npm run watch while in developement (watches the changes)
  • run yarn build or npm run dev for production

The optimized and minified style file is under static > css

Translations / i18n

#### Activate a new language

To activate a new language edit the LANGUAGES setting in settings.py

LANGUAGES = [
  ('en', _('English')),
  ('fr', _('French')),
  ('de', _('German')),
]

You need to do this first before translating because the language name itself needs to be translated.

Add a new language

To add a new language simply add a new directory in /locale with the language code as name, for example: /locale/fr for french.

Then to generate the translation files run:

python manage.py makemessages

It will create django.po files inside each /<lang>/LC_MESSAGES directory.

You can edit these files directly with any text editor or specialized software / web application.

Once the translations are complete, to generate the binary files optimized for consumption by Django, run:

python manage.py compilemessages

It will create django.mo files inside each /<lang>/LC_MESSAGES directory.