cookwherever VS Gridsome

Cook Wherever: https://cookwherever.com/

Cooking is hard. I want to cook more but I am usually too hungry to focus. I am building a site to help you with all stages of cooking, not just showing you ingredients and directions.

I have also realized the knowledge I have amassed for the “why” of cooking helps me cook without needing recipes mostly. I use ML/NLP to extract entities from ingredients and directions so contextual information can be provided to someone who is curious (ex. “you preheat your oven because …”)

I really like content creators, but following videos while cooking is a no-go for my attention span. I’m working on it, but directions will work as time stamps into a video for a recipe.

[1] https://github.com/cookwherever/cookwherever

TL;DR ive been consolidating my cooking knowledge in an open source recipe site https://github.com/cookwherever/cookwherever

Hey! I am excited to see people developing in this space since this is where my head is also at. Up until two years ago I was eating canned chili and soylent before I was shown the light with The Food Lab and Salt, Fat, Acid and Heat. Ever since I have been trying to share my knowledge on cooking with others with varying levels of success.

What has become clear to me is that there is no one size fits all approach to teaching cooking since it is usually a very cultural experience for most people (as many in the comments have pointed out). That said, SFAH makes the argument that most cuisines are much closer than people think when you consider the functional properties of the ingredients that you are cooking. Pizza is just pasta with yeast *Italian grandmothers slowly turn their heads towards this atrocity*

All of this to say, I believe recipes are critical to jump start the creative process of cooking. When any type of possible failure on the path to completion is experienced (ex. missing ingredient, burnt cookies, etc.) there MUST be some way of recovering or at the very least understanding how that happened.

I have been slowing taking notes on all the cooking knowledge I have come across and have been putting it along side the recipes that inspire me. Forcing learning on someone in the kitchen, who is already probably pretty hungry if cooking is seen as a chore, is not productive. Sharing the joy you get from the art that is cooking is IMPERATIVE for any type of educational resource.

If you are interested in my progress, or want to contribute go check it out! https://github.com/cookwherever/cookwherever

completely unrelated to your post, but just wanted to say thanks for your work on the rebooting of nyt’s ingredient parser. I use it in my project here: https://github.com/cookwherever/cookwherever (site is currently down due to the server being physically moved from our house lol). If you are interested in talking more about how i’m using it I would love to share :)

Thanks for reading!

The web tech stack is actually one of my biggest regrets. It's a static site generator called Gridsome[0] that the maintainers abandoned about three months after I used it to launch the TinyPilot website.

At the time I made the TinyPilot site, I was very excited about Vue, so a Vue-based SSG seemed great. Since then, I've come to find SPAs and most frontend frameworks to be way too much complexity, so I've moved away from Vue, but the TinyPilot website is still stuck on Vue 2.x and bootstrap-vue (which is tied to Vue 2 and Bootstrap 4).

So, it keeps creaking along, but building the 100ish pages on the site takes about five minutes, whereas I think something like Hugo could probably do it in a few seconds. Plus, we get random runtime errors[1] that are pretty hard to debug.

[0] https://gridsome.org/

[1] https://github.com/nuxt/nuxt/issues/5800

Nuxt.js and Gridsome are tailor-made for Vue.js developers.

Gridsome — Jamstack SSG tool for Vue developers

Node is basically back-end Javascript. While powerful alone, almost exclusively you will use a back-end framework like Next.js or Gatsby when using React, and then maybe Nuxt or Gridsome in Vue.

Among other thoughts, I considered a possibility of migration to a newer tech stack (because I can). Don't get me wrong, I actually love Gridsome (which is underneath my website now). But it's quite obsolete, and it's actually a dead project now.

One downside of Gridsome is that development seems to have stopped if you look at their github. For that reason I've recently switched my Gridsome clients to Nuxt

I definitely think Nuxt is worth learning for more than just a static site. However, there is a Gatsby-like Vue framework that focuses on SSG: https://gridsome.org/

Gridsome

All the Static Site Generators have been in the market for many years. With time, they get new improvements and upgrades as well. While considering SSG frameworks, like Gatsby, Nuxt, Gridsome, Next, and many more have been on the developer’s list for a long time. But when we talk about blazing fast web performance as per core web vital, then we have to do a lot of work in the available frameworks, after connecting a lot of dots (in terms of web performance), but still, we cannot achieve the web performance as per our need if we consider a use case of a large website where 20+ components are in one page.