Update change log and migration guide

docs/change-log.md

@@ -1,11 +1,18 @@
 # Change Log
 
-## Next release
+## v1.0.0
-- Add support for Empatica devices (all sensors)
+- Add a new [Where do I start?](../setup/where-do-i-start/) page.
-- Add logo
+- You can [extend](../datastreams/add-new-data-streams/) RAPIDS with your own [data streams](../datastreams/data-streams-introduction/). Data streams are data collected with other sensing apps besides AWARE (like Beiwe, mindLAMP), and stored in other data containers (databases, files) besides MySQL.
-- Move Citation page to the Setup section
+- Support to analyze Empatica wearable data (thanks to Joe Kim and  Brinnae Bent from the [DBDP](https://dbdp.org/))
-- Add `config.yaml` validation schema and documentation.
+- Support to analyze AWARE data stored in [CSV files](../datastreams/aware-csv/) and InfluxDB databases (the latter thanks to Neil Singh)
-- Add time at home Doryab location feature and home coordinates to location file
+- Support to analyze data collected over [multiple time zones](../setup/configuration/#multiple-timezones)
+- Support for [sleep intraday features](../features/fitbit-sleep-intraday/) from the core team and also from the community (thanks to Stephen Price)
+- Add RAPIDS new logo
+- Move Citation and Minimal Example page to the Setup section
+- Add `config.yaml` validation schema and documentation. Now it's more difficult to modify the `config.yaml` file with invalid values.
+- Add new `time at home` Doryab location feature
+- Add and home coordinates to the location data file so location providers can build features based on it.
+- If you are migrating from RAPIDS 0.4.3 or older, check this [guide](../migrating-from-old-versions/#migrating-from-rapids-04x-or-older)
 ## v0.4.3
 - Fix bug when any of the rows from any sensor do not belong a time segment
 ## v0.4.2

docs/migrating-from-old-versions.md

@@ -2,7 +2,10 @@
 
 ## Migrating from RAPIDS 0.4.x or older
 
-There are three actions that you need to take if you were using RAPIDS `0.4.3` or older ([before Feb 9th, 2021](https://github.com/carissalow/rapids/releases/tag/v0.4.3)):
+There are four actions that you need to take if you were using RAPIDS `0.4.3` or older ([before Feb 9th, 2021](https://github.com/carissalow/rapids/releases/tag/v0.4.3)):
+
+??? check "Check the new Where do I start? page"
+      Check the new [Where do I start?](../setup/where-do-i-start/) page. Hopefully, it is a better overview of RAPIDS and provides answers to Frequently Asked Questions.
 
 ??? check "Deploy RAPIDS in a new folder"
 
@@ -38,7 +41,7 @@ The most relevant changes to RAPIDS that you need to know about are:
       In the future, you will not have to change your raw data; you will be able to just change column mappings/values in the data stream's `format.yaml` file.
 
 ??? danger "We introduced multiple time zones"
-      The default is still a single time zone (America/New_York). See how to handle [multiple time zones](../setup/configuration/#multiple-timezones)
+      You can now process data from participants that visited multiple time zones. The default is still a single time zone (America/New_York). See how to handle [multiple time zones](../setup/configuration/#multiple-timezones)
 
 ??? danger "The keyword `multiple` is now `infer`"
       When processing data from smartphones, RAPIDS allows you to [infer](../setup/configuration/#participant-files) the OS of a smartphone by using the keyword `multiple` in the `[PLATFORM]` key of participant files. Now RAPIDS uses `infer` instead of `multiple` Nonetheless, `multiple` still works for backward compatibility.

docs/team.md

@@ -78,6 +78,16 @@ If you are interested in contributing feel free to submit a pull request or cont
 ??? abstract "About"
     - [Personal Website](https://runsdata.org/)
 
+###  Stephen Price
+
+??? abstract "About"
+    Carnegie Mellon University
+
+###  Neil Singh
+
+??? abstract "About"
+    University of Virginia
+
 ## Advisors
 
 ### Afsaneh Doryab