If you get in trouble, ask for help. Maybe not from Claude but from us. We'll help <3

Good point, I might keep it this way then. Depends on how well the site loads after I hit, like, 1000 videos. 

ihatevake

This works, but may get slow and unwieldy as the amount of content on the site grows. I am considering moving to a proper database like SQL down the road.

Keep the CSV, it's much more accessible and transparent than a database and accessibility is key. We're talking semi-static data as long as you keep vetting videos anyway. If you need better runtime performance, you can make a pre-rendering step where you build a working static site off of the latest "production" commit, and publish the generated site instead of the "source code".

bitcoin

I built a website that organizes bitcoin tutorial videos from across youtube

Good work!!!

> This works, but may get slow and unwieldy as the amount of content on the site grows. I am considering moving to a proper database like SQL down the road.

Keep the CSV, it's much more accessible and transparent than a database and accessibility is key. We're talking semi-static data as long as you keep vetting videos anyway. If you need better runtime performance, you can make a pre-rendering step where you build a working static site off of the latest "production" commit, and publish the generated site instead of the "source code".