• Add HRT name to Logo
• Restore existing background image
• Set up existing fonts
• Set up existing color scheme
• Add placeholder text to search inputs
• Style Inputs
• Add intersection finder
  • Street 1 input
  • Street 2 input
  • Search button

Form a team of 2 to 5 people

Gather with at least one other person to create a team around an idea or a problem that's interesting to you.

Spend a few minutes asking these questions:

• What's our shared vision?
  • Talk about what goal you want to accomplish as a team.
• What's in it for me?
  • Talk about each individual's motivation - what do you as an individual want to learn or accomplish?
• What talents do we bring to the table?
  • Share a bit of your experience and skills
• Set working agreements
  • What agreements do you as a team want to make this weekend go well?
  • Suggestions:
    • Show Up On Time: Agree on when you'll get here on Saturday (or at least show up at all!)
    • "Art of the Possible" - no idea is stupid, let's consider everything
    • Be Present - when you're here, you're here, be intentional with your time.

That's it! Now you have a clear goal for your team to accomplish and you know why each of you are here.

Implement base route with react-router.

Should be a friendlier version of:

1. Install your dependencies with

$ npm install

1. Start the server with

$ npm start

Create and determine how to implement a style guide.

Find a problem that's worth solving

Grab a lean canvas, if you don't have one already:

Then, use stickie notes to fill in Box 1, "Problem" (nothing else!).

How to write a problem statement:

Choose one of these two formats, and write your problem on a stickie.

• I believe [type of people] experience [type of problem] when doing [type of task]
• I believe [type of people] experience [type of problem] because of [limit or constraint]

You can have more than problem statement, but no more than 3.

Should allow the user to provide location by

• Geolocation
• opt in to always use geolocation
• Bus Stop Number
• Intersection

When user inputs information, route changes to Stops List.

Header exists mainly to toggle between Stop and Route modes.

Lay out routes for the application based on those in hrtb.us.

Existing routes can be divided into ways to find:

• Stops - #/stop
• Stop - #/stop/3535
• Routes - #/route
• Route - #/route/14
• Instructions
• Feedback

Or at least it doesn't confirm when it does.

Problem:

https://github.com/yannbertrand/trailpack-gulp manages our gulp but doesn't create an initial dist bundle this should be corrected.

Solution:
setup the default trails task to manage the dist bundle.

Should get the user's location, and display a list of nearby stops.

Who's your customer?

Fill in Box 2 on your lean canvas.

Ask yourself:

• Who do I think this problem (from Box #1) is most painful for?
• Who do I think my "early adopter" will be?

Be specific. Instead of saying "Teenagers", maybe "Girls who are in a public high school from a middle income family who has a cell phone."

Badge should be closer to right edge of container div.

Inactive Stops (Stops with no buses arriving soon) still have their names displayed, but are styled differently and have a "No buses coming" message.

The previous readme was before the migration to trailsjs.io, so we should update the documentation to reflect that.

Reference
.

Behavior and styles should be roughly similar to existing hrtb.us. Don't worry about detail view for now.