##About:

Describe this feature’s purpose here.

This feature addresses the dom construction of a detailed view for future & pending trips.

Story:

As a user, I want to click future trips, so that I can see both approved and pending future trips.

Concerns:

• apply dark mode
• .hidden toggle
• What if there are no future trips?
• what if there are no pending trips?
• what if there are no pending or no future trips?

##About:

Describe this feature's purpose here.
In the first iteration, I noticed some redundancies in classes. For the sake of time and managing brain power, I decided to air on the side of WET code rather than fine tuning during this first iteration

Story:

As a dev, I want utilize inheritance, so that I can DRY up my classes.

Concerns:

• Which class is my parent class?

##About:

Describe this feature’s purpose here.

This feature is an attempt to separate duties of classes. It's possible that this shouldn't be a class, but rather a feature that will be added on to the login portion.

Story:

As a dev, I want to be able to enter in a number associated with a traveler's id, so that I can find all data associated with that travelers.

Concerns:

• is there a function/method to find a traveler based on their id number

About:

Describe this feature’s purpose here.

This addresses the wish to have a reset button added in a form.

Story:

As a user, I want to click a button, so that I can reset a form to its original value.

Concerns:

• dark mode
• where should the reset button be?
• should it appear at a certain time or any time?
• reset for estimage
• reset for request submit

About:

Describe this feature’s purpose here.
This feature addresses the dom construction of a detailed view for possible trips.

Story:

As a user, I want to open a separate page with all the possible destinations, so that I can see all possible trips.

Concerns:

• apply dark mode
• .hidden toggle
• filtering a part of this iteration or set on the backburner.

##About:

Describe this feature’s purpose here.
This feature addresses the form structure a user would want to interact with when booking a site.

Story:

As a user, I want a form, so that I can book my next trip.

As a dev, I want a form with four pieces: 2 text boxes (for num of travelers & duration of trip), a calendar (for start date), and a drop down for where to so that a user can make a selection and POST a trip if they choose to.

Concerns:

• once all fields are filled, only then is an estimate is returned
• have picture & breakdown available
• make note that 10% fee already included
• have reset button?
• POST/submit button appears at estimate
• dark mode
• when posted, update of front page ect al occurs

##About:

Describe this feature’s purpose here.

This feature addresses the dom construction of a detailed view for current trips.

Story:

As a user, I want to click on current trips, so that I can see my current trips.

Concerns:

• apply dark mode
• .hidden toggle
• if no current trip, what displays instead?

##About:

Describe this feature’s purpose here.
This addresses some of the unused methods of the Traveler class and areas of refactoring.

Story:

As a dev, I want a concise traveler class, so that I can easily find breakpoints within my code.

Concerns:

• Edit past, present, and future in html or in class to keep consistency.
• Refactor "total" and "yearly total" estimates
• assess the benefits of having the class contain it's own trips array

##About:

Describe this feature’s purpose here.
This feature addresses the need for a single instance of a destination to easily access specific information about a single destination.

Story:

As a dev, I want a Destination class, so that I can easily create a new instance of a destination for viewing purposes when browsing places to book.

Concerns:

• Are property names consistent with API data?
• Is there a need for defaults?
• Is it redundant?

##About:

Describe this feature’s purpose here.

The purpose of this feature is to give the user the option to view the page via dark or light mode.

Story:

As a user, I want a dark mode button, so that I can choose to use it or not. .

Concerns:

• logo visible still?
• text visible
• button colors ok black or white?
• contrast problems?
• check wave
• check lighthouse

##About:

Describe this feature’s purpose here.
This addresses the question if a user would want to see their pending trips separate from the past, present, and future trips.

Story:

As a user, I want a separate section, so that I can view my pending trips.

• display at bottom of main page
• pending trips: default message || name of destination & trip #
• darkmode
• separate domUpdate when booking is submitted.

##About:

Describe this feature’s purpose here.

This feature addresses the dom construction of a detailed view for past trips.

Story:

As a user, I want to click on past trips, so that I can see my past trips.

Concerns:

• apply dark mode
• .hidden toggle
• display 'total' here

##About:

Describe this feature’s purpose here.

This addressed iteration 1's need of having the total price displayed (must include 10% fee somewhere).

Story:

As a user, I want to know how much I've spent on traveling, so that I can share with friends.

Concerns:

• where should this number be displayed?
• how should the travel agent's fee be noted/included
• is this interactive or "static"

##About:

Describe this feature’s purpose here.
To alter the summary of how many total trips and how much has been spent on those trips displayed on the main dashboard.

Story:

As a user, I want to open my dashboard, so that I can see my personal summary data.

Concerns:

• instantiate a traveler
• get length of myTrips to display (domUpdates)
• get totalExpenses to display (domUpdates)

##About:

Describe this feature’s purpose here.
Change monetary stat to include a comma (ie 23,000 not 23000) for easier readability

Story:

As a user I want a comma in my stats, so that I can read how much I've spent easier.

Concerns:

• Where does this belong? (class or dom?)

##About:

Describe this feature’s purpose here.

This feature addresses iteration 1 dashboard build out. The goal is to create a skeleton of HTML that sets up our scripts and provides easy structure to adjust for SCSS with a mobile first process.

Story:

As a user, I want to have a clean & concise dashboard, so that I can see my trip logs.

Concerns:

• semantic HTML
• choose dyslexic friendly font
• what's viewed upon load
• what's interactive
• select images
• have alt text
• check data for images
• check data images for alt text
• settle color scheme
• check colorblindness
• run lighthouse now
• light house screen shot
• run wave now
• wave screen shot
• address any issues brought up by both

About:

Describe this feature’s purpose here.

Although created and passing the tests, the Destination class is never once used up to Iteration 3.

Story:

As a dev, I want to create an agent space, so that as an agent, new Destinations could be posted.

##About:

Describe this feature’s purpose here.

This builds out the Traveler Class.

Story:

As a dev, I want to have a Traveler class, so that I can pass in an object as an argument and return data pertaining to a specific Traveler.

Concerns:

• does the constructor contain properties to hold a Travelers data
• should find all of traveler's trips
• should filter if their trips are approved or pending
• should calculate total amount of money spent on travels, total
• should find past trips
• should find current trips
• should find future trips

##About:

Describe this feature’s purpose here.

Although the site is responsive, best viewing is done on a mobile device. This addresses the need for breakpoints on a large screen.

Story:

As a user, I want to login into my account on a desktop, so that I can see everything in a more horizontal rather than vertical manner.

Concerns:

• do additional divs need to be included
• rem, em, or vw/vh?

##About:

Describe this feature’s purpose here.
This feature creates a single instantiation of a trip that can be used during the Iteration 2 for booking and POSTing purposes.

Story:

As a dev, I want to have a Trip class, so that I can easily POST a new object to my trips API.

Concerns:

• is there a default value for ID to account for a new POST?
• is there space for all data to be stored?
• is there a method that calculates a single trips estimated cost?

##About:

Describe this feature’s purpose here.

This enhancement allows the user to understand and see the fee attached to their travel expenses (10% fee).

Story:

As a user, I want to click on my total amount spent, so that I can see the break down of travel agency fees.

Concerns:

• Does dark mode apply to elements
• is it obvious where to click to get this information