Inspiration
As students, we've seen our fair share of bad presentation slides. Too much text, bland colours, abhorrent animations. These are all hallmarks of a slide deck gone wrong. We seek to solve this problem, by giving slide makers a helping hand in the creation process.
What it does
Slide Linter scans your currently selected slide and performs an analysis on its contents. It checks for a variety of different common mistakes such as:
- Title too long
- Too many words on the slide
- Too many animations
- Too many pictures
How we built it
We used Google's App Script environment to build and test the application. We used HTML and Javascript to implement server-side and client-side applications that communicate together over the network to parse slide contents and return a list of rule violations.
Challenges we ran into
- Issues with Google's script editor made it difficult to collaborate on code together and format code
Accomplishments that we're proud of
- Working product
- Didn't crash
- We got sleep
What we learned
- Javascript is hard
- What are callbacks?
- Asynchronous execution
What's next for Slide Linter
- More lint rules
- Option to ignore rules for a particular slide or entire presentation
- Automatically running the scan for each slide instead of having to click a button
- Automatically fixing/providing suggestions for lint errors
- Distinction between warnings and errors
Built With
- google-slides
- html5
- javascript

Log in or sign up for Devpost to join the conversation.