This repository has been archived by the owner on Feb 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
Things we use
Seamus Smith edited this page May 12, 2022
·
20 revisions
Here are all the frameworks, libraries, and other things we use in this project.
-
- The framework we use for our entire app
- Uses Python, so future students can easily maintain this app
-
- OAuth swiss army knife. Allows us to integrate with Google
-
- Integration with google (duh)
- Calendar docs: https://developers.google.com/resources/api-libraries/documentation/calendar/v3/python/latest/index.html
-
- Easy to use pre-made styles.
- When making new components, use Bootstrap's styles. Bootstrap has a ton of pre-made components, and you are just wasting your time writing your own CSS.
- Only create entirely new classes as a last resort. This should only be in the case where you add on to a style or need an entirely new component not provided by Bootstrap.
-
- An extensible CSS preprocessor
- Bootstrap uses it, so we can easily modify it's styles and color scheme.
- All CSS is valid SCSS, so you don't even need to know how to use Sass in order to write it.
- btw we gitignore all
*.css
files, so you have to write your styles in.scss
-
- Distribution of Vue.js made for progressive enhancement of pages, particularly for server-side rendered websites.
- Can easily be imported with just a script tag
- Makes implementing client side UI logic easy, so we can write less JavaScript.
-
- Free to use icons we can use
-
- Embeddable rich text editor
- Things we use
- Heroku Maintaining
- Creating a dev environment
- Documentation Guidelines
- Calendar Integration Schema