diff --git a/_posts/2022-05-31-SUGCH-2022-1.md b/_posts/2022-05-31-SUGCH-2022-1.md
index 3991bbfaa5d8c..9a1a599e89c23 100644
--- a/_posts/2022-05-31-SUGCH-2022-1.md
+++ b/_posts/2022-05-31-SUGCH-2022-1.md
@@ -11,11 +11,11 @@ Our last online meetup already dates a while back - not to mention our last _in-
 
 [Tobias Studer](https://twitter.com/studert) gave an interesting overview over Sitecore's composable DXP landscape and how Sitecore has changed. Thanks for preseting on such short notice.
 
-<blockquote class="twitter-tweet"><p lang="en" dir="ltr">coming up next at <a href="https://twitter.com/hashtag/SUGCH?src=hash&amp;ref_src=twsrc%5Etfw">#SUGCH</a> : using geaphql with <a href="https://twitter.com/hashtag/Sitecore?src=hash&amp;ref_src=twsrc%5Etfw">#Sitecore</a> by Thomas Wittek <a href="https://t.co/uOwYsWRbjq">pic.twitter.com/uOwYsWRbjq</a></p>&mdash; SUG CH (@sugch) <a href="https://twitter.com/sugch/status/1531685107278413826?ref_src=twsrc%5Etfw">May 31, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
-
 [Thomas Wittek](https://www.linkedin.com/in/thomaswittek1/) showed us why and how to work with GraphQL by creating custom schemas, creating custom endpoints and demonstrated how to write data through mutations.
 
-[Reto Hugi](https://twitter.com/retohugi) presented his learnings and findings from working on a Headless/Next.js project which sparked some interesting discussions around Next.js and caching.
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">coming up next at <a href="https://twitter.com/hashtag/SUGCH?src=hash&amp;ref_src=twsrc%5Etfw">#SUGCH</a> : using geaphql with <a href="https://twitter.com/hashtag/Sitecore?src=hash&amp;ref_src=twsrc%5Etfw">#Sitecore</a> by Thomas Wittek <a href="https://t.co/uOwYsWRbjq">pic.twitter.com/uOwYsWRbjq</a></p>&mdash; SUG CH (@sugch) <a href="https://twitter.com/sugch/status/1531685107278413826?ref_src=twsrc%5Etfw">May 31, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+[Reto Hugi](https://twitter.com/retohugi) presented his learnings and findings from working on a Headless/Next.js project which sparked some interesting discussions around Next.js and caching. See the [slide deck of the presentation](/assets/Reto-Hugi_SUGCH-2022-NextJS-JSS-Learnings.pdf) for details.
 
 <blockquote class="twitter-tweet"><p lang="en" dir="ltr">next <a href="https://twitter.com/retohugi?ref_src=twsrc%5Etfw">@retohugi</a> with „cloud, container, k8s, headless, oh my!“ <a href="https://twitter.com/hashtag/SUGCH?src=hash&amp;ref_src=twsrc%5Etfw">#SUGCH</a> <a href="https://t.co/Mm7MxEcKyc">pic.twitter.com/Mm7MxEcKyc</a></p>&mdash; SUG CH (@sugch) <a href="https://twitter.com/sugch/status/1531697912928927747?ref_src=twsrc%5Etfw">May 31, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
 
diff --git a/assets/Reto-Hugi_SUGCH-2022-NextJS-JSS-Learnings.pdf b/assets/Reto-Hugi_SUGCH-2022-NextJS-JSS-Learnings.pdf
new file mode 100644
index 0000000000000..ea884d6b4dcb5
Binary files /dev/null and b/assets/Reto-Hugi_SUGCH-2022-NextJS-JSS-Learnings.pdf differ