diff --git a/docs/1.getting-started/10.deployment.md b/docs/1.getting-started/10.deployment.md
index 5b17574f89..4b341e6a7d 100644
--- a/docs/1.getting-started/10.deployment.md
+++ b/docs/1.getting-started/10.deployment.md
@@ -64,6 +64,10 @@ By default, the workload gets distributed to the workers with the round robin st
 
 :read-more{to="https://nitro.unjs.io/deploy/node" title="the Nitro documentation for node-server preset"}
 
+::tip{icon="i-ph-video" to="https://www.youtube.com/watch?v=0x1H6K5yOfs" target="\_blank"}
+Watch Daniel Roe's short video on the topic.
+::
+
 ## Static Hosting
 
 There are two ways to deploy a Nuxt application to any static hosting services:
diff --git a/docs/2.guide/2.directory-structure/1.components.md b/docs/2.guide/2.directory-structure/1.components.md
index f4cf6c7e97..8fb3a0c59f 100644
--- a/docs/2.guide/2.directory-structure/1.components.md
+++ b/docs/2.guide/2.directory-structure/1.components.md
@@ -82,6 +82,10 @@ const MyButton = resolveComponent('MyButton')
 If you are using `resolveComponent` to handle dynamic components, make sure not to insert anything but the name of the component, which must be a string and not a variable.
 ::
 
+::tip{icon="i-ph-video" to="https://www.youtube.com/watch?v=4kq8E5IUM2U" target="\_blank"}
+Watch Daniel Roe's short video about `resolveComponent`.
+::
+
 Alternatively, though not recommended, you can register all your components globally, which will create async chunks for all your components and make them available throughout your application.
 
 ```diff