appliedepi / slides

Other
6 stars 2 forks source link

Slides structure #35

Open jarvisc1 opened 6 days ago

jarvisc1 commented 6 days ago

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.

aspina7 commented 6 days ago

unless ive understood you wrong .... i think we just want one images folder. I think if its the same folder structure, we should just be able to cut/paste and we shouldnt have filepath issues....

jarvisc1 commented 6 days ago

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.

aspina7 commented 5 days ago

mmmm still reckon single images folder means less complication and less duplication

jarvisc1 commented 5 days ago

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.

aspina7 commented 5 days ago

very well - separate folders it is