Captions

Author: pomber

xmdx/demo/cake.mdx

@@ -48,7 +48,7 @@ unusual content and layouts.
 0.3 –> 3.7
 But first I need to show you how this works
 3.7 –> 7.9
-we are going to start with this small react app
+we are going to start with this small React app
 8 –> 14
 this is using Next.js but the same applies to
 any app that has the MDX loader
@@ -216,13 +216,33 @@ and run the transformation on build-time
 />
 
 ```srt
-I usually write content that has steps, like tutorials or any type of walkthrough where you explain something step by step.
-
-Markdown doesn't have any specific syntax for grouping things in steps. But we can use MDX to extend markdown and introduce our syntax.
-
-The implementation of the Step component we are using here doesn't matter, we are just using it for grouping elements.
-
-If you are new to MDX, this may not be the best introduction. The typical use-case for MDX is embedding interactive components in markdown. But here we are taking a different approach, and using it more as a syntax extension for markdown.
+1 -> 4.3
+I usually write content that has steps
+4.3 -> 10.7
+like tutorials or any type of walkthrough
+where you explain something step by step
+10.7 -> 16.3
+markdown doesn't have any specific syntax
+for grouping things in steps
+16.3 -> 23.7
+but we can use MDX to extend markdown
+and introduce our syntax
+23.7 -> 28.1
+the implementation of the Step component
+we are using here doesn't matter
+28.1 -> 31.8
+we are just using it for grouping elements
+31.8 -> 35.2
+if you are new to MDX,
+this may not be the best introduction
+35.2 -> 40
+the typical use-case for MDX is embedding
+interactive components in markdown
+40 -> 42.7
+but here we are taking a different approach,
+42.7 -> 47.68
+and using it more
+as a syntax extension for markdown
 ```
 
 ---
@@ -252,19 +272,31 @@ If you are new to MDX, this may not be the best introduction. The typical use-ca
 />
 
 ```srt
-Now, based on the MDX file that has steps, we can write another Wrapper component.
-
-In this case, in the children prop, we get one React element for each step.
-
-So we can keep track of what step we are showing using React state, and let the user change the current step with a button.
-
--> click
-
--> click
-
-Ok, now I want to show the same content but with a different layout.
-
-There's a technique called scrollytelling. You may have seen it on some websites, as the user scrolls down there's some part of the layout that sticks to the screen while the rest is scrolled away. Let's do that.
+0 -> 5.9
+now, based on the MDX file that has steps,
+we can write another Wrapper component
+5.9 -> 12
+in this case, in the children prop,
+we get one React element for each step
+12 -> 16.4
+so we can keep track of
+what step we are showing using React state
+16.4 -> 21
+and let the user change the current step
+with a button
+25 -> 30.4
+ok, now I want to show the same content
+but with a different layout
+30.4 -> 36.4
+there's a technique called scrollytelling,
+you may have seen it on some websites
+36.4 -> 42
+as the user scrolls down there's some
+part of the layout that sticks to the screen
+42 -> 45.1
+while the rest is scrolled away
+45.1 -> 47
+let's do that
 ```
 
 ---
@@ -285,21 +317,26 @@ There's a technique called scrollytelling. You may have seen it on some websites
 />
 
 ```srt
-Since this is a lightning talk I'll import the ScrollytellingLayout component. I'll share the link to the repo later if you want to see how it works.
-
-The ScrollytellingLayout component takes two props, one for the left-side that can be scrolled, and the other for the sticky part on the right.
-
-When the user scrolls to a new step
-
---> scroll
-
-we show the corresponding element from the sticker list.
-
---> scroll
-
---> scroll
-
-Now, instead of showing the step number, let's add the sticker content to the MDX file.
+0 -> 7
+since this is a lightning talk
+I'll import the ScrollytellingLayout component
+7 -> 12.5
+I'll share the link to the repo later
+if you want to see how it works
+12.5 -> 17.2
+the ScrollytellingLayout component
+takes two props
+17.2 -> 23.8
+one for the left-side that can be scrolled,
+and the other for the sticky part on the right
+23.8 -> 27.2
+when the user scrolls to a new step
+27.2 -> 30.4
+we show the corresponding element
+from the sticker list
+36.2 -> 44
+now, instead of showing the step number,
+let's add the sticker content to the MDX file
 ```
 
 ---
@@ -316,9 +353,15 @@ Now, instead of showing the step number, let's add the sticker content to the MD
 />
 
 ```srt
-Suppose we want to show some code in the sticky part of the layout.
-
-There isn't any specific syntax for this, so we need to create our convention. Like, for example, we put the sticky part of the step as the first element.
+2.8 -> 7.5
+suppose we want to show some code
+in the sticky part of the layout
+7.5 -> 14
+there isn't any specific syntax for this,
+so we need to create our own convention
+14 -> 19
+like, for example, we put the sticky part
+of the step as the first element
 ```
 
 ---
@@ -338,17 +381,17 @@ There isn't any specific syntax for this, so we need to create our convention. L
 />
 
 ```srt
-Now, doing some array transformation, we get the list of steps and the list of stickers and pass them to the same Layout component.
-
-So when the user scrolls
-
---> scrolls
-
-the code on the right
-
---> scrolls
-
-should change accordingly.
+0.8 -> 3.8
+now, doing some array transformations
+3.8 -> 10.2
+we get the list of steps and the list of stickers
+and pass them to the same Layout component
+10.2 -> 12.5
+so when the user scrolls...
+13.5 -> 15
+the code on the right...
+15 -> 19
+should change accordingly
 ```
 
 ---
@@ -369,21 +412,22 @@ should change accordingly.
 />
 
 ```srt
-Just for fun, I have a Terminal component that animates between code transitions,
-
-so we can use it for the stickers.
-
---> scrolls
-
---> scrolls
-
---> scrolls
-
---> scrolls 0
-
-I've been experimenting with another layout for walkthroughs,
-instead of changing the steps using the scroll like in this example,
-we can synchronize the steps with some media, like a video or audio, maybe a podcast, and change the steps as the media progress.
+1 -> 7.5
+just for fun, I have a Terminal component
+that animates between code transitions
+7.5 -> 10
+so we can use it for the stickers
+21.7 -> 25.4
+I've been experimenting with
+another layout for walkthroughs
+25.4 -> 30.2
+instead of changing the steps
+using the scroll like in this example
+30.2 -> 38.1
+we can synchronize the steps with some media,
+like a video or audio, maybe a podcast
+28.1 -> 43
+and change the steps as the media progress
 ```
 
 ---
@@ -399,7 +443,12 @@ we can synchronize the steps with some media, like a video or audio, maybe a pod
 />
 
 ```srt
-To do that, in the MDX file, we need to specify the media file and the time range for each step.
+0.6 -> 3
+to do that,
+in the MDX file
+3 -> 9
+we need to specify the media file
+and the time range for each step
 ```
 
 ---
@@ -415,19 +464,24 @@ To do that, in the MDX file, we need to specify the media file and the time rang
 />
 
 ```srt
-Once we have that, we can extract it from the children on the Wrapper, and pass it to another React component.
-
-This time is the TalkLayout component, that solves all the synching for us.
-
-And you should see the steps changing every time I snap the fingers.
-
---> snap 1
-
---> snap 2
-
-Some of you may have noticed that this looks similar to the layout of this talk that I'm giving right now.
-
-And it is.
+0.6 -> 8
+once we have that, we can extract it
+from the children on the Wrapper
+8 -> 10.2
+and pass it to another React component
+10.2 -> 18
+this time is the TalkLayout component,
+that will solve all the synching for us
+18 -> 23
+and you should see the steps changing
+every time I snap the fingers
+26.3 -> 32.1
+some of you may have noticed that this
+looks similar to the layout of this talk
+32.1 -> 34.1
+that I'm giving right now
+34.1 -> 37
+and it is
 ```
 
 ---
@@ -436,32 +490,39 @@ And it is.
 <Browser url="/" zoom={0.4} />
 <Editor
   code="cake.mdx"
-  focus="23:30"
+  focus="489:509"
   lang="md"
   tab="demo/cake.mdx"
   tabs={["demo/cake.mdx", "pages/index.js"]}
 />
 
 ```srt
-This talk was built using this same technique. It's all MDX.
-
-For example, here on the left, you can see the code for the step you are currently watching.
+0.7 -> 4.4
+this talk was built using this same technique
+4.4 -> 7.3
+it's all MDX
+7.3 -> 9.7
+for example, here on the left
+9.7 -> 15
+you can see the code for the step
+you are currently watching
 ```
 
 ---
 
-<Video src="016.webm" start={0} end={0} />
+<Video src="016.webm" start={0} end={4} />
 <Browser url="/" zoom={0.4} />
 <Editor
   code="cake.mdx"
-  focus="23:30"
+  focus="513:526"
   lang="md"
   tab="demo/cake.mdx"
   tabs={["demo/cake.mdx", "pages/index.js"]}
 />
 
 ```srt
-And the next step.
+0 -> 4
+and here is the next step
 ```
 
 ---
@@ -477,14 +538,33 @@ And the next step.
 />
 
 ```srt
-Ok, that's all.
-
-The takeaway is: you can use MDX to build your own dialect tailored for any specific layout.
-
-I leave you here the links to the repo of the talk. Not the slides, but the talk itself. You run yarn dev and you can watch this talk again.
-
-Also, there's my twitter, and the components we used.
-Most of them come from a new project I'm working on, it's called Code Hike and it focuses on code walkthroughs and tools for making it easy to explain code.
-
-Thank you.
+1.5 -> 4.2
+and, that's all
+that's all I have
+4.2 -> 12.8
+the takeaway is: you can use MDX to build
+your own dialect tailored for any specific layout
+12.8 -> 16.2
+I leave you here the links
+to the repo of the talk
+16.2 -> 18
+not the slides
+but the talk itself
+18 -> 22.7
+you run yarn dev
+and you can watch this talk again
+22.7 -> 26.7
+also, there's my twitter,
+and the components we used
+26.7 -> 29.5
+most of them come
+from a new project I'm working on
+29.5 -> 34.5
+it's called Code Hike
+and it focuses on code walkthroughs
+34.5 -> 40
+and tools for making it easy
+to explain code
+40 -> 42
+thank you!
 ```