Organize repo

[rsyoh-97]

@zstumgoren Do you have tips on how to organize the repo? We're thinking of separate folders for "data" (raw/processed data), "scripts" (for all the data work) and "website" (html, css, etc.)

[miguelito34]

Current thoughts, bold indicates actual folders, unbolded indicate plain files. Notably, within the "website" folder, is there any best practice for organizing

• data
  • raw
  • processed
• notebooks (mostly used as sandbox)
• scripts (mostly for data pipeline)
  • data_wrangling
    • scripts that pull and clean data for analysis; would dump cleaned data into processed data folder
  • analysis
    • scripts that generate variables to be fed into jinja scripts within website folder
• website (holds html, css, JS files)
  • templates (html templates go here)
  • script(s) that pull analyzed data/key variables from analysis scripts and generates html for county pages
  • site
    • homepage html file
    • counties
      • individual html file for each county
  • CSS files
  • JS files

[zstumgoren]

@rsyoh-97 I talked this through with @miguelito34 after class but ping back if any other questions arise

[miguelito34]

Per conversation with Serdar:

• data
  • raw
  • processed
• notebooks (mostly used as sandbox)
• scripts
  • data_wrangling
    • scripts that pull from source and clean data for analysis; dump cleaned data into processed data folder
  • analysis
    • scripts that generate variables to be fed into jinja templating scripts
  • templates (html templates go here)
  • county page html rendering script
• website (holds html, css, JS files)
  • homepage html file
  • county-data
    • individual html file for each county
  • static
    • CSS
    • JS

Will reformat the repo (before we get coding too much), upon discussion.