-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keep profile images in repo #110
Comments
Oh no :/ so you mean like storing them in a folder (permanently) and accessing them from here? We'd need to double check to be safe on the GDPR side + I'd also want to ask for consent. Just thinking out loud - wouldn't be another alternative to capture a random screenshot of the website and adding that as an image on the website? Or, even better, create a link card instead? |
oh yes, we for sure cannot do that without asking first! a link card could be good, but I struggled getting that working with hugo. Want to give it a try @cosimameyer ? If we can get link cards, then we can simplify the json information too (like getting page title etc from OG directly) |
I looked into it yesterday; I don't have a working solution yet but I'm on it :) |
I had an idea. I don't know what you are thinking, but what if we setup a script that runs curl to fetch website info, grab the og data and add the og data to the Json? That could also minimize the information we ask people to supply to us, as we would get it from the source? |
ok, one of the main reasons the website build fails is becuase the profile image from this repo's url does not resolve anymore.
While I have tried capturing this in Hugo so that it does not fail, it just keeps happening.
I wonder if we might keep the images in this repo, as a way to combat that?
The text was updated successfully, but these errors were encountered: