All Projects → COVID19Tracking → Website

COVID19Tracking / Website

Licence: apache-2.0
The COVID Tracking Project website

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Website

vue-production-server-proxy
Boilerplate for Vue project ready for production, with neat implementation of "devServer proxy" in production environment, using Nginx
Stars: ✭ 27 (-94.36%)
Mutual labels:  production
b2-sdk-python
Python library to access B2 cloud storage.
Stars: ✭ 124 (-74.11%)
Mutual labels:  production
Redux Remotedev
Redux DevTools for production (web and React Native) with a highly flexible API.
Stars: ✭ 265 (-44.68%)
Mutual labels:  production
openprofiling-node
OpenProfiling is a toolkit for collecting profiling data from production workload safely.
Stars: ✭ 60 (-87.47%)
Mutual labels:  production
Django-on-Docker-with-Heroku-and-OpenCV
Deploy Django on Docker to Heroku and include OpenCV
Stars: ✭ 24 (-94.99%)
Mutual labels:  production
food-help
A clone of popular food and business review web app yelp
Stars: ✭ 24 (-94.99%)
Mutual labels:  production
defcon
DefCon - Status page and API for production status
Stars: ✭ 12 (-97.49%)
Mutual labels:  production
Elm Companies
🌲 A list of companies using Elm in production.
Stars: ✭ 365 (-23.8%)
Mutual labels:  production
gosane
A sane and simple Go REST API template.
Stars: ✭ 81 (-83.09%)
Mutual labels:  production
Deep Learning In Production
In this repository, I will share some useful notes and references about deploying deep learning-based models in production.
Stars: ✭ 3,104 (+548.02%)
Mutual labels:  production
restrictfe
TYPO3 extension restrictfe. Blocks access to frontend and allows to show it only to some defined exception's like if the request is from an authorized backend user, has specific IP, header etc.
Stars: ✭ 12 (-97.49%)
Mutual labels:  production
reactnative-android-production
Step by step guid for compiling and installing React Native Android app [ bundled release version ] to your test device.
Stars: ✭ 51 (-89.35%)
Mutual labels:  production
cache-trace
A collection of Twitter's anonymized production cache traces.
Stars: ✭ 89 (-81.42%)
Mutual labels:  production
pro-chat
Full featured chat app built with 💙 Expo & Firebase 🔥
Stars: ✭ 24 (-94.99%)
Mutual labels:  production
Covid Tracking Data
Stars: ✭ 271 (-43.42%)
Mutual labels:  production
editions
📆🆕 Daily Edition app
Stars: ✭ 42 (-91.23%)
Mutual labels:  production
DMIA ProductionML 2021 Spring
Репозиторий направления Production ML, весна 2021
Stars: ✭ 42 (-91.23%)
Mutual labels:  production
Production Data Science
Production Data Science: a workflow for collaborative data science aimed at production
Stars: ✭ 388 (-19%)
Mutual labels:  production
Dgraph
Native GraphQL Database with graph backend
Stars: ✭ 17,127 (+3475.57%)
Mutual labels:  production
chomp-decomposition
Staffjoy Suite (V1) Microservice - Demand to Shift Decomposition
Stars: ✭ 41 (-91.44%)
Mutual labels:  production

COVID Tracking Project

The COVID Tracking Project collects information from 50 U.S. states, the District of Columbia, and 5 other U.S. territories to provide the most comprehensive testing data we can collect for the novel coronavirus, SARS-CoV-2.

This repository is for the project's website: https://covidtracking.com/.

Documentation

Additional documentation can be found at our documentation and Storybook website.

Development

The website is built on GatsbyJS. If you are not familiar with Gatsby, we suggest checking out their excellent documentation.

Install

First, you'll need the Gatsby command line interface installed globally:

npm install -g gatsby-cli

Then, install all dependencies by running:

yarn install

The website is built from two separate data sources: our own API for COVID data, and Contentful for content. To download the most recent COVID data and setup a .env file with a copy of read-only API keys to Contentful, run:

yarn setup

You can also run yarn setup:api-repo if you just want to download data and not touch the .env file.

To run the website locally, use:

yarn develop

The project takes 8-10 minutes to build.

The site is now running at http://localhost:8000. Any changes you make to code is live-updated. There is a GraphQL preview tool available at http://localhost:8000/___graphql to see what data is exposed to the website.

Note that any changes you make while running Gatsby will automatically checked with ESLint, so check your console as you save files.

Organization

Components live in src/components and are organized as follows:

  • /charts - Visualizations
  • /common - Components that are used more than once and those that are used across different parts of the website
  • /layout - Components that control the layout of the website (i.e. headers and footers)
  • /pages - Components that are only used once or have a defined scope to a particular part of the website (i.e. StateGrade has to do with states) belong in their respective directory in /pages
  • /utils - Utilities. (If a particular component doesn't have any associated styles, there's a good chance it's a utility.)

Testing

Coverage Status

We use Jest for automated testing, and all test files for Gatsby are located in ./src/__tests__. Test files are structured following their related components. To run tests, use yarn test.

When you make a change to an interface, you will need to update the Jest snapshot for tests to complete successfully:

yarn test:update

Before pushing your local branch to the repository, make sure to run yarn test:dev. This will make sure the project is linted and all tests pass. Make sure that every test passes. Pull requests are automatically checked against these same tests.

Storybook

View our Storybook

All common components throughout the site are documented in Storybook. You can find all our component stories in /src/stories.

To preview the storybook locally, just run:

yarn storybook

The storybook is now available at http://localhost:6006.

How to contribute

No matter how you choose to help, we would love to have you as part of the project. Check our Contributing Guide for information on how to file issues and make pull requests.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].