This is a React Application that queries the NASA Photo of the Day API and returns 25 results to the user. If the user clicks on a photo, the app will return details about that photo from the NASA API. 
[Home_Mobile](https://user-images.githubusercontent.com/65795477/125976547-f39ebe7f-00e5-4988-b107-ff53a5ca906f.jpeg)
what's up at NASA is a working, interactive, full-stack application that receives data from a custom API that we designed. The app allows users to learn more about programming languages, their icons, their authors, and their creation date.
- As a user of what's up at NASA, I want to be able to view the top programming language and view the properties of each language so I can have all the information in a centralized location.
- As a user of what's up at NASA, I want to be able to create comments about programming language to be add to the database so that I can interact with the app.
- As a user of what's up at NASA, I want to be able to see my created post so that I know my post is saved.
- As a user of what's up at NASA, I want to be able to update a post incase I make a mistake.
- As a user of what's up at NASA, I want to be able to delete my post so that I can remove any unwanted post.
Our team used Agile workflow for this sprint.
We implemented Git Feature Branch Workflow. All pull requests in Github were reviewed by another team member before being merged into the main branch.
Cut problems into smaller pieces and console.log any unknown data. This was our first project as a team and so we relied heavily upon each other to debug our own problems. We learned a lot about communication, division of labor, project management, and how to utilize each of our individual strengths. Read documentation!!! Most of the answers are available if you know where and how to search.
One of the key feature of React is the composition of the functional components. Components are reuseable functions in React, and in order to efficiently build our app, we had to carefully decide on a uniform set of data and plan who would work on which components. Before diving into the creating the app, it was important to understand the components hierarchy.
React Components The Component Hierarchy diagram, above, represents of how the components are structured in our app. In what's up at NASA, there are 8 components. Each being a child of the 'App' components, except for the NavHeader and the Footer component.
In this case, all of the event listeners and the main API calls were done in the 'App.js' file and that data is passed down to Languages and then Language.
By creating our own API, what's up at NASA is able to make dynamic request. For this app, the programming languages endpoint was used. So different props variables were created to make multiple calls.
Creating a responsive App. what's up at NASA uses React bootstap paired with Flexbox and media queries in order to make it responsive across mobile, tablet, and desktop widths.
User Stories (Stretch Goals)
- As a user of what's up at NASA, I want a search feature that allows me to search either programing languages or paradigm and get a result of different usage. (edited)
This application uses a Node, Express, and Mongoose API. There is Create, Read, Update, and Destroy functionality built throughout the app. The front-end uses React and leverages the backend API RESTfully to Create, Read, Update, and Destroy resources. This app uses CSS Grid and Flexbox along with media queries to make your app responsive across mobile, tablet, and desktop widths.
yarn install