-
Notifications
You must be signed in to change notification settings - Fork 3
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
Slides structure #35
Comments
unless ive understood you wrong .... i think we just want one images folder. |
So actually I think we what an image folder per slide folder for images in a single slide deck. Then another global image folder for stuff that's used crossed them. This code won't ever change though. I've figured it out as I've done it and I can implement pretty easily. |
mmmm still reckon single images folder means less complication and less duplication |
If the images in one slide deck overlap with the others a bunch then yeah. But the majority of slide images are in a single slide deck. So then if we have one images folder it's not easy to see which image relates to each slide. Plus if we want to delete an image we have to search to see all the slide decks that they're in. |
very well - separate folders it is |
We should attempt to have a consistent structure between the slides in these folders and how the slides are placed for devlopment.
At the moment the filepaths within a course being developed will be different for the ones in here. Plus the names of the slide folders are inconsistent.
I'd propose
A slides folder in each course which is identical to this slides repo.
For shiny it would go
shiny_course/slides/shiny/
Then inside this folder there would be
images
shiny01/ - images just for this slide and image
shiny02/ - images just for this slide and the slides files.
Then we just need to look at it a bit more to try and get the filepaths to not be changed when copying over.
Probably it's just having /images.
The text was updated successfully, but these errors were encountered: