Cool!

Suggestion: Show the times in terms of now (using browser's local time), e.g. "in 2 hours" etc. At the very least, include the timezone. I find it confusing when sites publish scheduled times without timezone or relative time, because you never know what system they're using to store the times. Could be UTC, could be my local timezone, could be the timezone of the game... I don't know unless you tell me. Maybe take a look how Google does this (search for a game and see the knowledge card; they explicitly show timezones)

Also, maybe an oversight: the README/comments here say you're using api.football-data.org but the footer of the site says you're using worldcup.sfg.io.

Overall, cool project and nicely timed. I know it's not easy to ship side projects on a schedule like that :)

Hey, nice site, I was looking into API's and such for my simple site: http://feed.football what API are you pulling that data from and how did you hide the key on the front end?

Hi, sorry Im not sure on the API being used. But just to let you know you can access an API by creating your own endpoint to call, which then calls the target API. In which case your not exposing the target API's key as its backend code. Then you can ensure only your users are using their particular key and for example rate limit them yourself.

Hope this helps

Hi, sorry for the delay in responding but as one of the earlier answers mentioned, I'm using the football-data.org API.

I did not hide the key as you can get your own free key from their service :)

From README.md on the project's GitHub:

> Data provided by: https://api.football-data.org/