add tailgraph OG image

README.md

@@ -76,6 +76,7 @@ See https://swyxkit.netlify.app/ (see [Deploy Logs](https://app.netlify.com/site
 		- [Comments are rendered and sanitized](https://github.com/developit/snarkdown/issues/70)
 		- `full`, `feature`, and `popout` [bleed layout](https://ryanmulligan.dev/blog/layout-breakouts/) classes on desktop - `feature` enabled by default for code samples! ([details and code samples here](https://swyxkit.netlify.app/layout-breakouts-in-swyxkit))
 		- Top level blog URLs (`/myblog` instead of `/blog/myblog` - [why](https://www.swyx.io/namespacing-sites/))
+    - Autogenerated (overridable) og:images via an external service https://github.com/sw-yx/swyxkit/pull/161
 	- General features
 		- Navlink hover effect
 		- [Mobile/Responsive styling](https://swyxkit.netlify.app/mobileresponsive-styling-with-tailwind)
@@ -162,6 +163,31 @@ Open a new GitHub issue on your new repo, write some title and markdown in the b
 
 You should see it refetched in local dev or in the deployed site pretty quickly. You can configure SvelteKit to build each blog page up front, or on demand. Up to you to trade off speed and flexibility.
 
+Here's a full reference of the frontmatter we have included - ALL of this is optional and some of have aliases you can discover in `/src/lib/content.js`. Feel free to customize/simplify of course.
+
+```markdown
+---
+title: my great title
+subtitle: my great subtitle
+description: my great description
+slug: my-title
+tags:
+  - foo
+  - bar
+  - baz
+category: blog
+image: https://my_image_url.com/img-4.png
+date: 2023-04-22
+canonical: https://official-site.com/my-title
+---
+
+my great intro
+
+## my subtitle
+
+lorem ipsum 
+```
+
 If your `Published` post (any post with one of the labels set in `GH_PUBLISHED_TAGS`) doesn't show up, you may have forgotten to set `APPROVED_POSTERS_GH_USERNAME` to your GitHub username in `siteConfig`.
 
 If all of this is annoying feel free to rip out the GitHub Issues CMS wiring and do your own content pipeline, I'm not your boss. MDSveX is already set up in this repo if you prefer not having a disconnected content toolchain from your codebase (which is fine, I just like having it in a different place for a better editing experience). See also my blogpost on [the benefits of using GitHub Issues as CMS](https://swyxkit.netlify.app/moving-to-a-github-cms).