Skip to content
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

Stand up initial client side setup to populate app with dynamic content #65

Closed
hspinks opened this issue Mar 20, 2020 · 3 comments
Closed
Labels
client Mobile client/app component feature New feature or request
Projects

Comments

@hspinks
Copy link
Collaborator

hspinks commented Mar 20, 2020

Using server side setup from #64, integrate dynamic content into the app. Should bake the initial content directly into app bundle for offline functionality, but server side content can override

@hspinks hspinks added the feature New feature or request label Mar 20, 2020
@hspinks hspinks added this to the v0.1 milestone Mar 20, 2020
@hspinks hspinks added the client Mobile client/app component label Mar 20, 2020
@hspinks hspinks added this to To do in Engineering Mar 20, 2020
@advayDev1
Copy link
Contributor

advayDev1 commented Mar 20, 2020

@hspinks #24 was originally vNext, while this is v0.1, please clarify timeline for dynamic content

@advayDev1 advayDev1 self-assigned this Mar 20, 2020
@hspinks hspinks modified the milestones: v0.1, vNext Mar 20, 2020
@hspinks
Copy link
Collaborator Author

hspinks commented Mar 20, 2020

@advayDev1 good catch, moved to vNext

advayDev1 referenced this issue in madvay/who-covid-app Mar 21, 2020
- Make screen content data-driven.  Content is now separat from code and pm/design can iterate without us using YAML.
- Introduce UserContext, which specified the facets of a user for which customc content can be provided.  If content is unavailable for a paricular context, there is a backoff priority.
- Provide option to fetch flows and images from web.  If it isn't there, use baked in version.
- Have content be served from GitHub pages for now.

Added dependency: js-yaml to parse YAML files.  Most used yaml package on npm, 10.5MM monthlies, depended on by some of the biggest open source projects: https://www.npmjs.com/browse/depended/js-yaml

Cough and wash hands images are CC0/PD: https://thenounproject.com/term/infectious-disease/613/ ; https://thenounproject.com/Iconathon1/collection/clean-water/?i=8138

Distance image is OC ;)
advayDev1 referenced this issue in madvay/who-covid-app Mar 21, 2020
- Make screen content data-driven.  Content is now separat from code and pm/design can iterate without us using YAML.
- Introduce UserContext, which specified the facets of a user for which customc content can be provided.  If content is unavailable for a paricular context, there is a backoff priority.
- Provide option to fetch flows and images from web.  If it isn't there, use baked in version.
- Have content be served from GitHub pages for now.

Added dependency: js-yaml to parse YAML files.  Most used yaml package on npm, 10.5MM monthlies, depended on by some of the biggest open source projects: https://www.npmjs.com/browse/depended/js-yaml

Cough and wash hands images are CC0/PD: https://thenounproject.com/term/infectious-disease/613/ ; https://thenounproject.com/Iconathon1/collection/clean-water/?i=8138

Distance image is OC ;)
advayDev1 referenced this issue in madvay/who-covid-app Mar 21, 2020
- Make screen content data-driven.  Content is now separat from code and pm/design can iterate without us using YAML.
- Introduce UserContext, which specified the facets of a user for which customc content can be provided.  If content is unavailable for a paricular context, there is a backoff priority.
- Provide option to fetch flows and images from web.  If it isn't there, use baked in version.
- Have content be served from GitHub pages for now.

Added dependency: js-yaml to parse YAML files.  Most used yaml package on npm, 10.5MM monthlies, depended on by some of the biggest open source projects: https://www.npmjs.com/browse/depended/js-yaml

Cough and wash hands images are CC0/PD: https://thenounproject.com/term/infectious-disease/613/ ; https://thenounproject.com/Iconathon1/collection/clean-water/?i=8138

Distance image is OC ;)
advayDev1 referenced this issue in madvay/who-covid-app Mar 21, 2020
- Make screen content data-driven.  Content is now separat from code and pm/design can iterate without us using YAML.
- Introduce UserContext, which specified the facets of a user for which customc content can be provided.  If content is unavailable for a paricular context, there is a backoff priority.
- Provide option to fetch flows and images from web.  If it isn't there, use baked in version.
- Have content be served from GitHub pages for now.

Added dependency: js-yaml to parse YAML files.  Most used yaml package on npm, 10.5MM monthlies, depended on by some of the biggest open source projects: https://www.npmjs.com/browse/depended/js-yaml

Cough and wash hands images are CC0/PD: https://thenounproject.com/term/infectious-disease/613/ ; https://thenounproject.com/Iconathon1/collection/clean-water/?i=8138

Distance image is OC ;)
advayDev1 referenced this issue in madvay/who-covid-app Mar 21, 2020
- Make screen content data-driven.  Content is now separat from code and pm/design can iterate without us using YAML.
- Introduce UserContext, which specified the facets of a user for which customc content can be provided.  If content is unavailable for a paricular context, there is a backoff priority.
- Provide option to fetch flows and images from web.  If it isn't there, use baked in version.
- Have content be served from GitHub pages for now.

Added dependency: js-yaml to parse YAML files.  Most used yaml package on npm, 10.5MM monthlies, depended on by some of the biggest open source projects: https://www.npmjs.com/browse/depended/js-yaml

Cough and wash hands images are CC0/PD: https://thenounproject.com/term/infectious-disease/613/ ; https://thenounproject.com/Iconathon1/collection/clean-water/?i=8138

Distance image is OC ;)
advayDev1 added a commit that referenced this issue Mar 21, 2020
* Dynamic content flow #24, #64, #65

- Make screen content data-driven.  Content is now separat from code and pm/design can iterate without us using YAML.
- Introduce UserContext, which specified the facets of a user for which customc content can be provided.  If content is unavailable for a paricular context, there is a backoff priority.
- Provide option to fetch flows and images from web.  If it isn't there, use baked in version.
- Have content be served from GitHub pages for now.

Added dependency: js-yaml to parse YAML files.  Most used yaml package on npm, 10.5MM monthlies, depended on by some of the biggest open source projects: https://www.npmjs.com/browse/depended/js-yaml

Cough and wash hands images are CC0/PD: https://thenounproject.com/term/infectious-disease/613/ ; https://thenounproject.com/Iconathon1/collection/clean-water/?i=8138

Distance image is OC ;)

* [nit] Keep LICENSE file names around until I get ACK from PJ/Pat
@hspinks hspinks modified the milestones: vNext, v1.0 Mar 27, 2020
@hspinks
Copy link
Collaborator Author

hspinks commented Mar 30, 2020

Closed in #588

@hspinks hspinks closed this as completed Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Mobile client/app component feature New feature or request
Projects
No open projects
Engineering
  
To do
Development

No branches or pull requests

2 participants