// middle of migrating pattern library to package. got the package working yay! quite a few conflicts, package is async currently when compiling CSS

TODO:

• screenshot recipe to share

• form to email lou recipe suggestions (suggestionBox)

• type of dessert: (pie, cookie, cake, other);

• Spices how to section

• change taco soup recipe back to original. -"meal" where you add multiple recipes to a stage to look only at those (ie: pie crust & filling)

• multiplicity in recipe

• Make pie recipes link to pie crust

• consider making alphanav verticle so you can just tap any letter. include all all letters, they're disabled when filtered out

• authentication : one (long) password that is passed around with word of mouth : before I can disable recipes, I need to put them in the server (css would not make it secure)

  • is it time to make an api? no
  1. make a route that returns data.json
  2. Add to data requiresAuth
  3. Do Javascript to filter them out in the server before sending the JSON.
  4. (All other filters should remain front end. The data isn't so big anyway, it's just text)

Recipes to add

• gravy?
• wassail
• garlic bread
• harlo vegan chocolate cake https://www.mydarlingvegan.com/vegan-chocolate-hazelnut-zucchini-cake/
• harlo vegan butternut squash soup https://cookieandkate.com/roasted-butternut-squash-soup/
• em "Grilled Chicken Thighs with Alaba.." Em text Mon Aug 17th.

TO DEPLOY:

npm run deploy

BORKER

https://funtranslations.com/chef

Available Scripts

In the project directory, you can run:

npm start

http://localhost:3000 The page will reload if you make edits.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify