You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe that separating slides into slides.html, slides.css and slides.js would be a good approach.
Use case: I use the template for a presentation. Upstream some bugs get fixed. I have to manually port my slides to the new template to have both the new CSS and JS with my old slides (or vice-versa).
By having it in separeted files, I would only have to update/download the new files and copy the css and js into the folder where my presentation is.
cons: 2 more connections to the server
pros: way easier to read presentation file and css/js upgrade method
it is an easy change but before that, what do you think?
The text was updated successfully, but these errors were encountered:
I totally understand why you want to do that, but I want to keep this template "standalone".
You can easily split the file in 3 different if you prefer, but I'd like to keep it like that by default.
Hi,
I believe that separating slides into slides.html, slides.css and slides.js would be a good approach.
Use case: I use the template for a presentation. Upstream some bugs get fixed. I have to manually port my slides to the new template to have both the new CSS and JS with my old slides (or vice-versa).
By having it in separeted files, I would only have to update/download the new files and copy the css and js into the folder where my presentation is.
cons: 2 more connections to the server
pros: way easier to read presentation file and css/js upgrade method
it is an easy change but before that, what do you think?
The text was updated successfully, but these errors were encountered: