✔ everything looks good!

Resume

I think it looks good! Two minor things:

• "AngularJS" is the technical term for "Angular 1.0". For Angular 2.0 or higher, always use the term "Angular". That's probably all your Angular experience, so find/replace it everywhere.
• for the first bullet point about your project has some room for improvement, I think:

This Capstone Project was the culmination of what I learned in LaunchCode's LC101 course, combining a robust Java backend, utilizing MySQL for database management, with an AngularJS frontend.

I like the first half. The second half ... I donno. The overall thing you're trying to convey is that *you figured out how to use Java, Angular, and MySQL together. The intended reader should know what all these things are, for example, you don't need to explain that MySQL is the database. I'm tempted by just saying:

This Capstone Project was the culmination of what I learned in LaunchCode's LC101 course, combining Java, Angular, and MySQL into a single application.

That's everything I can think of. Looks good!

LinkedIn

✔ looks good!

Github

✔ also fine!

Everything looks good.
Nice work on using Moqups!

Your vision of weaving together recipes, inventory, and grocery lists strikes me as both intricate and easy-to-communicate. You'll have interesting application-specific logic - for example, subtracting inventory from a recipe to generate a grocery list. In short, I like this idea a lot.

While I love your feature list, it is also probably beyond the minimum you'll need to get a job. If you came to class with user login and foods about to expire C.R.U.D., and really any one of the other three features, I'm sure Koko would not think twice to send you for job interviews. I know that you've got a lot on your plate (food joke!), so consider how you could best trim it down.

For example, while it'd be great to hit a food api, maybe it'd be easier to have a hardcoded list of recipies loaded from a text file, or stored in your database? I'm not trying to talk you out of the food API, instead I'm trying to brainstorm options.

My other observation is that you've got Thymeleaf on your API list and not Angular. Is that a deliberate decision to avoid Angular, or an oversight? Nowadays most apps are built with a JS framework on the front end (e.g. Angular) and a strongly typed language on the back end (e.g. Java). Server side views with templating languages like Thymeleaf will never be phased out entirely, but servers returning json to front-end frameworks like Angular will be dominant, more complex, and more powerful.

Overall: good job. Assignment accepted. See you in 1.8 weeks.