Lessons naming convention

[camilavargasp]

As for now, I'm trying to name the few lessons we are using to test the new workflow in a logical way that is easily adaptable to other lessons. Some general rules:

• Use lower snakecase
• Start with the tool or type of lesson (r, github, activity, lecture)
• Use github in name for lessons that include Git and GitHub?
• lecture would be all the non-technical lessons that are presented in a more lecture format
• activities are all hands-on activities that do not involve coding (generally associated to a non-technical lesson)

[camilavargasp]

Note: I added the images for each lesson in the inst/images folder. However, I did not edit names of these files.

[oharac]

I think that should be fine - it is keying off of the folder name, tied to the lesson name, so all the files inside the folder will come along for the ride

[oharac]

Because a data folder in inst potentially conflicts with accessing a data folder elsewhere in the package, I renamed that folder to lesson_data, and to keep the structure similar I renamed the image folder to lesson_img. Everything else should be fine. For ease of code so far, these get copied over into the newly created course directory with the same names, into the materials folder, so materials/lesson_data and materials/lesson_img - while the lessons themselves are stored as .qmds in materials/lessons.

Additionally, I added a license (MIT for now).