One of my recent projects at the Turing school, Sweater Weather, is a local API that takes map and directions data from MapQuest + MapQuest Geocoding, plus weather data from OpenWeather, and tells a requester what conditions to expect at their time of arrival.

I was curious about Flows in Postman, so I decided to give them a shot with my homebuilt API - specifically to see if the weather was sufficiently sunny to go forward with the trip plan, or "abandon trip."

Flows is essentially a way to daisychain API requests together, and add conditional or reactionary steps based on the data from each. It's a low-code solution, enabling folks who are less familiar with javascript to configure requests in sequence and manipulate and sort results.

(Many thanks to Beth at Beth's Testing Blog for the primer which helped my early understanding of the tool!)

• What worked well in your process?
• What was difficult/where did you struggle?
• What feedback/discussion did you have with your peer?
• Is there anything you want to change about your approach to the next technical challenge?
• If this isn’t your first technical challenge:

Were you able to improve your approach? What went better?

Answer these Check for Understanding questions as you work through the assignments.

1. What is HTML?

Hypertext Markup Language, the standard markup language for Web pages. HTML describes the structure of a web page and consists of a series of elements.

2. What is an HTML element?

To make a copy of this rubric:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
2. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

• I named my directories correctly.