Tech Balanced Home

This is the final project for "Phase 1" of the DigitalCrafts Flex Class. The project is to build a web application as a group with libraries and APIs. For the credit of the course, our project must be in accordance with the requirements laid out below to fulfill Texas State requirements for credit for the course.

Project Description

This project features a web application that will comprehensively manage the household, with functions including sorting daily chores, creating shopping lists, paying bills, managing appointments and etc. In this group project, our main focus is on the chores page, on which the head of household can assign duties to other family members, while family members can view their coming-up chores, change the status as they finish and receive notification messages.

Our app's mission is to improve household efficiency and to relieve the head of household(whether the mom or dad)'s burden through technologies.

About Us

Our team includes:

• Audy Arandela
• Erika Aguirre
• Robert L Arnold III
• Lanzhen Wang

Tech Used

This app used the following technoloies:

• jQuery UI
• Bulma
• Firebase
• Cloud Firestore

Our repo is connected to Travis CI and deployed through XXXXX.

Tech Requirements for course purpose

This app must:

• Use at least one JavaScript library that is not jQuery. Examples:

  • Moment.js
  • Marked
  • jQuery UI
  • chessboard.js
  • Additional List

• Use a CSS framework. Examples:

  • Bootstrap
  • Bulma
  • Foundation

• Access at least two remote APIs using AJAX. Examples:

  • Firebase
  • Cloud Firestore
  • TheCatAPI
  • Google Maps
  • Big List of Public APIs
  • Another Big List of Public APIs
  • Note that loading a JavaScript or CSS library from a CDN does not fulfill this requirement. You must use AJAX.

• Your project must have a README.md file written using Markdown with at least the following:

  • Explanation of what the project is / what it does.
  • What technologies you used.
  • List of team members.

• Deployment of your application to somewhere other than GitHub Pages. Examples:

  • Amazon S3
  • Google Cloud
  • Netlify
  • Neocities
  • Surge
  • Note that you do not need to purchase a domain name for your project. But it should be reachable via a public URL somewhere.

• Your repo must be connected to Travis CI:

  • You must run at least one test in your Travis CI build (hint: test for StandardJS)
  • Put a build status badge in your README.md that links to your latest build

• Code must follow some organization scheme.

  • Everything cannot be in one super long file.
  • Break different parts of the code into different files / modules.
  • No "spaghetti code".
  • Bonus / optional: consider using a build system with npm scripts, browserify, or webpack