|
|
||
|---|---|---|
| .. | ||
| .github | ||
| api | ||
| public | ||
| web | ||
| .gitignore | ||
| .vercelignore | ||
| .yarnrc | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| vercel.json | ||
| yarn.lock | ||
Installing
yarn installyarn startYtoSet up and develop “~path/to/the/repo/manifold”? [Y/n]Manifold MarketstoWhich scope should contain your project? [Y/n]YtoLink to existing project? [Y/n]opengraph-imagetoWhat’s the name of your existing project?
Quickstart
- To test locally:
yarn startThe local image preview is broken for some reason; but the service works. E.g. tryhttp://localhost:3000/manifold.png - To deploy: push to Github
- note: (Not
devbecause that's reserved for Vercel) - note2: (Or
cd .. && vercel --prod, I think)
For more info, see Contributing.md
(Everything below is from the original repo)
Development
- Code of interest is contained in the
api/_libdirectory, i.e.template.tsis the page that renders the UI. - Edit
parseRequest(req: IncomingMessage)inparser.tsto add/edit query parameters. - Note: When testing a remote branch on vercel, the og-image previews that apps load will point to
https://manifold-og-image.vercel.app/m.png?question=etc., (see relevant code inSEO.tsx) and not your remote branch. You have to find your opengraph-image branch's url and replace the part beforem.pngwith it.- You can also preview the image locally, e.g.
http://localhost:3000/m.png?question=etc. - Every time you change the template code you'll have to change the query parameter slightly as the image will likely be cached.
- You can also preview the image locally, e.g.
- You can find your remote branch's opengraph-image url by click
Visit Previewon Github: 
Open Graph Image as a Service
Serverless service that generates dynamic Open Graph images that you can embed in your <meta> tags.
For each keystroke, headless chromium is used to render an HTML page and take a screenshot of the result which gets cached.
See the image embedded in the tweet for a real use case.
What is an Open Graph Image?
Have you ever posted a hyperlink to Twitter, Facebook, or Slack and seen an image popup?
How did your social network know how to "unfurl" the URL and get an image?
The answer is in your <head>.
The Open Graph protocol says you can put a <meta> tag in the <head> of a webpage to define this image.
It looks like the following:
<head>
<title>Title</title>
<meta property="og:image" content="http://example.com/logo.jpg" />
</head>
Why use this service?
The short answer is that it would take a long time to painstakingly design an image for every single blog post and every single documentation page. And we don't want the exact same image for every blog post because that wouldn't make the article stand out when it was shared to Twitter.
That's where og-image.vercel.app comes in. We can simply pass the title of our blog post to our generator service and it will generate the image for us on the fly!
It looks like the following:
<head>
<title>Hello World</title>
<meta
property="og:image"
content="https://og-image.vercel.app/Hello%20World.png"
/>
</head>
Now try changing the text Hello%20World to the title of your choosing and watch the magic happen ✨
Deploy your own
You'll want to fork this repository and deploy your own image generator.
- Click the fork button at the top right of GitHub
- Clone the repo to your local machine with
git clone URL_OF_FORKED_REPO_HERE - Change directory with
cd og-image - Make changes by swapping out images, changing colors, etc (see contributing for more info)
- Remove all configuration inside
vercel.jsonbesidesrewrites - Run locally with
vercel devand visit localhost:3000 (if nothing happens, runnpm install -g vercel) - Deploy to the cloud by running
verceland you'll get a unique URL - Connect Vercel for GitHub to automatically deploy each time you
git push🚀
Authors
- Steven (@styfle) - Vercel
- Evil Rabbit (@evilrabbit) - Vercel