301final

Group Members:

Yvonne, David, Kate

Team Name:

Node It Alls

Project Name:

Should I Bike It - PDX

Site Deployed At:

http://final301.herokuapp.com/

Problem Statement:

In the erratic Portland weather, it's hard to anticipate the weather on the other side of town, or even in the same spot after a few hours have lapsed.

Do you bike? Whether you're giving it a quick glance or a more in depth look, we give you the updates you need on the state of biking around your favorite spots in Portland.

User Stories:

As a biker in Portland, I would like to know the conditions for the destinations I wish to bike between that day.
As a user of the app, I would like to have commonly-biked-to locations saved in the app to save my effort.
As a commuter, I would like to know that my method of travel is appropriate all day.
As a developer, I want to create clear, DRY code that adheres to the MVC Model.
As a user of the app, I would like to have it available on the go from my mobile phone.
As a developer I want to use object oriented, functional, decoupled programming.
As a developer, I want to leverage third-party information services in my app to save from having to manually collect the data ourselves.
As a developer, I want to harness the privacy allowed by keeping private data persisted on a server as opposed to being in the source code.
As a developer, I want to make use of middleware to streamline my information processing.
As a developer, I'd like to make big bucks off this shit. (ha!)

Requirement Tracker

Documentation Requirements

Include a link to the repo in the footer of the site KATE
Include a link to the live site in the repo's readme AND description KATE
Develop a User Guide YVONNE FRIDAY AM

HTML Requirements

Remove unused/commented out/irrelevant code and process documentation files ALL
Use semantic HTML tags, if it is an important tag but isn't descriptive, use classes, ids, or comments to describe it's purpose ALL
Consistent indentation ALL
Remove redundancies; repeated DOM structures should be templated or programmatically created using JS KATE/YVONNE

CSS Requirements

Clear and meaningful CSS, semantically meaningful class and id names; use proper indentation; correct syntax issues KATE
SMACCS Principles with CSS files KATE
Layout is pleasing across various screen sizes; use a fluid grid KATE/DAVID

JS Requirements

Must pass eslint ALL
Use semantically meaningful variables and function names ALL
Remove source code redundancies with functional programming, object oriented programming, and/or middleware; keep it DRY ALL
Reduce computational redundancy; cache computed results if reused. EVEN make variables for repeated DOM element queries with JQ YVONNE/KATE

Technical Requirements

At least three interlinked pages with clear navigation KATE
At least two pages must accept and process user input KATE
Use jQuery for DOM Manipulation, user event handling, and animations YVONNE/KATE
Mobile-first and responsive design KATE
Process input from an HTML Form with at least one button YVONNE
Encapsulate all data and functions and use object constructors and prototypical inheritance where appropriate KATE/DAVID
Use AJAX to retrieve JSON or XML data; make sure a HOF makes the AJAX call: pass a "next" function to the HOF, HOF should make AJAX request and specify "next(data)" as the callback. "next()" should then call a view function to display the data. HOF should be in a model js file DAVID
Functional programming; use Array methods, HOFs, and at least one closure DAVID
Persist your app's state using WebSQL or other database (if we persist on server-side database we don't need to use the local database); write middleware that handles CRUD operations on your database DAVID
Build a single page app and use client-side routing for at least two routes KATE
Use MVC components that are loosely coupled, semantically labelled, and well documented as MVC in code comments ALL
Deploy to public web server including a server-side app that authenticates to a third party server (weatherunderground) KATE/DAVID

Stretch Goals

Persist at least some of your app's data in two or more WebSQL tables and make SQLite queries that use joins/relations to filter data. (1pt) YES
use a finite state machine that explicitly models the FSM using named inputs (events) and named states (1pt) NO
Include an audio element and use .mp3 format for our media file (1pt) NO
Use JS built in methods .bind() and .apply(); answer the following questions in the sbumission: (1pt) NO

The methods belong to what kind of object? Does each object have its own copy of the method, or are the methods on the prototype for that object?
How does .apply() differ from .call()?

Let users register on your site with a username and password; require login to access some of the site's data:

Use client side authentication as proof of concept (0.25pt) YES
or use server-side authentication (2pt) YES

Persist at least part of your app's state on a server such as Heroku or Firebase (2pt) NO
Make presentation and plan for who shows what ALL FRIDAY AM

User's Guide

'Should I Bike It?' - User’s Guide

'Should I Bike It?' is an app designed with ease of use in mind. Its clean design is meant to draw the eye to the information that matters - quickly and without any distractions.

You never know how the weather might change and whether it’s a good day to take the bike. A look out the window might tell you what it’s like at your current location but what about your destination? You could consult a weather specific webpage and search for all the info that’s important to you or you could quickly glance at 'Should I Bike It?' and get all the information you need within a second.

When you first open up 'Should I Bike It?' you will see the welcome screen and a quick explanation of what it’s all about. After that click on the Configure link on the top of the page and you will be taken to a short form that will ask for your name. Once you enter your name you are then asked to enter a location. This could be anything - your home, the office, your favorite coffee shop or any other place you like to bike to. You don’t have to remember which locations you have already entered - 'Should I Bike It?' will keep track of them for you and you can always see them on the Configuration Page under the Saved Locations heading.

On the Dashboard is where the magic happens. With one glance you can see all the important weather data at your current location and all your other favorite places as well. Armed with this information you can then easily decide on whether you’d like to take your bike. For the really busy among you there’s an extra treat - you don’t even need to look at this info and make your own decision if you don’t want to (or if it is very early in the morning). 'Should I Bike It?' provides a short, simple message that tells you what it’s like outside, what you should bring to be well prepared and if you should get on your bike or should rather leave it at home. Easy peasy lemon squeezy.

Once glance and you know whether to bike it - a simple idea that opens incredible possibilities.

katesowles/301final