Api/new data structure

[rsteckline]

What kind of change does this PR introduce?

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor(DRY-ing up/ reorganizing code, etc.)
• Small fix (Corrected a typo, removed a comment, etc.)

Issue/feature/bug description:

Restructuring components to return functionality for new API response

Checklist before requesting a review

• I ran the code locally and verified that there are no visible errors.
• I have performed a self-review of my code
• I have refactored my code before this push
• The commit message follows our guidelines
• My code follows the code style of this project.

What’s next:

Testing and redeployment error check

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
laboulangerie	✅ Ready (Inspect)	Visit Preview	Feb 10, 2024 8:24pm

[dsstevens]

Great job restructuring how the application is handling the reformatted API response so that we can better parse out and display the recipe. In part two when we implement a CSS preprocessor, our breakpoints and styling will be more concise and better handled. Thanks for dealing with my breakpoints!