Formats for tutorials and screencasts

[sohilpandya]

So we need to decide upon a format for all the learning videos that we'll be creating. Here is the rough format that has been proposed by @nelsonic in the discussion we've had earlier.

1. Brief Intro (30 sec)

• name and what the topic you are covering

2. Show the end result (1 min)

• What will the user see at the end of the tutorial, this is important as we don't want the user to sit through the whole video if the end result is not what they are looking for

3. Run through the tutorial (4 - 5 min)
4. Retrospective / debrief

• tell them what they've achieved and also to find us on GitHub etc.

This would mean that individual videos are no longer than 6 -7 mins. If a video has more content, we can split it up and have it as parts. (e.g. part - 1, part - 2)

What do you think of the format? Feedback Welcome!

[Cleop]

This is the script for the words used in the tachyons-bootstrap video in case anyone wants to use the same wording in the future: dwyl/tachyons-bootstrap#9 (comment)

(WELCOME)- Hello, my name is Cleo and I'm a developer at dwyl. This is an introduction to tachyons-bootstrap.

<-- a bit in the middle giving a longer description and why t-b is super cool -->

(WHAT) So let's build something! Go to http://tachyons-bootstrap.dwyl.com, and select the Forms section in the contents. We're going to create our own basic form. (telling the viewer what they're going to make)

(CONCLUSION)- We hope you enjoyed this video please subscribe and check out our other resources on github using the link below.

[nelsonic]

The only thing to note/remember is:

(what's in it for me?)

There's no need to "over-sell" it to the audience, but we should "frame" the intro from the perspective of the audience specifically so they know why this is a good decision for them:

• The Learner (developer): pitch it in simple language but don't "dumb it down" so more experienced people don't feel like it's "not relevant" to them.
• The Team/Technical Lead (or "CTO" / technical decision maker): explain how the technology gives specific benefits. e.g:
  • "increase team productivity as features can be built faster.
  • reduce time wasted on fixing UI bugs/conflicts because all styles are self-contained
  • "lower total cost of ownership" over the lifespan of the project.