We held a special meeting to discuss the subject of lesson plan slides.
Last year at the community summit we discussed the inclusion of slides and were able to lay out some of the bigger concerns about using them. Since then we have tried a few different things along with coming up with a basic list of what we would want if we had a plugin. Most recently there has been an attempt to use the photoshop comps made about a year ago and try them as google slides. This would have still been a stop-gap measure as many of the concerns brought up are really only solvable via a plugin. Concerns the team has discussed related to the slides include:
- backwards compatibility
- learning curve
- lack of internet
- design consistency between different sets of slides
- ease of updates
We’ve discussed the plugin many times over the past year including in January.
Pros and Cons of Google Slides
- The platform is similar to something many are familiar with as it’s much like PPT or Keynote.
- Allows color changes that would address accessibility issues.
- Allows offline mode and downloading of PDF versions.
- Allows for submission of template on Google Slides’ “repo”.
- There is no way to import the lesson plan content automatically as updates occur.
- May be hard to use.
- Seems to require fixed aspect ratio.
- Keeping design consistency from slide to slide, even with the master template, seems impossible to control with lots of people editing since you can just drag and drop elements on each slide.
The Reveal Option
Reveal came about as an idea after @bethsoderberg‘s initial HTML/CSS cutup earlier this year failed because of the impossibility of controlling vertical height issues. Reveal is just HTML, CSS, and JS and accounts for the slide height issues and theoretically it could also be integrated with a plugin.
@courtneydawn suggested a course of action moving forward that was discussed and agreed to by meeting attendees:
- We go back to creating a document that serves as a requirements definition doc for our pretend plugin.
This will allow us all as a team to say what we think are necessary functionalities of our dream slide plugin
and what would be just nice to have. We finish this by the time WCUSA comes around so we can workshop it with other teams and see if there are people out there who can help us.
- Rework the Google slides (if there is a volunteer) with no design components so that we can see what happens when the aesthetic functionality is not an issue. (@melindahelt volunteered to take this on with her most recent set of slides)
- See if someone who is going to do a test of one of our plans wants to create a set of slides of either Google or Reveal nature.
The overarching goal here is to create a series of functional test cases to look at together so that we can all discuss at WCUSA.
Moving forward @courtneydawn will lead a slides conversation every other week in the weekly team meetings that will establish the scope required for a plugin as well as enable the team to have a true sense of the universe of needs and issues with the slides so that we can make informed decisions at WCUSA.