Developer Documentation Made Easy With Scribe

With Scribe you can create fantastic developer documentation quickly and easily using their browser plugin or premium screen recording application. More information at scribe.how/jack-herrington
0:00 Introduction
0:58 Scribe Usage
11:31 Outroduction

[@jherr]

Try out Scribe today on my personalized signup link at scribe.how/jack-herrington !

[@jherr]

Hahah, thanks. :)

[@user-mq6zb7xy6d]

@@jherr Sure , u deserve more than that thanks for everything that u provide us

[@zzej]

this has to be the best sponsored video iv'e seen. ty for introducing me to scribe :)

[@alvarocastillocorrea2610]

Scribe is super helpful, it saved me tons of time documenting processes for user to use apps seamlessly.

[@bobdpa]

Awesome!

[@blue_berry_pie64]

That what I need now ❤🎉

[@maciejfigat8237]

Thank you for the video. I was just trying to do a quick documentation for a recruitment project. Wish me luck.

[@josemonge4604]

I liked the markdown feature a lot

[@the16tha.i.26]

This Vedio came in the perfect time to help me with the documantation.
Also whats up with your voice mann you sound soo cool.

[@modoudiao9660]

great share

[@aghileslounis]

Scribe is an amazing product

[@jherr]

Agreed.

[@user-mq6zb7xy6d]

great

[@SithLordBishop]

interview:
"whats your greatest weakness"
"documentation"

[@rohitkharche7562]

Now we would also love a video on full text search with algolia just like docs have for searching.

[@jherr]

I’ll ask for that. They already took my recommendation for supporting markdown. It’s not implemented yet tho.

[@rohitkharche7562]

That would be great, if they also support that too, for now I will stick to Docsearch by algolia

[@cahva2]

I actually tried this but the good stuff is behind paywall and the price for using this maybe once a month is too steep

[@user-qg3ep3ec3u]

Why it should be useful when we have openapi for apis and storybook for frontend ?

[@WilliamShrek]

This is ScribeGPT.

[@kakaique2000]

8:04 Maybe forgot to blur your e-mail all way through

[@Gigusx]

The beginning jumped out at me. Obviously one wouldn't go through all the steps with screenshots every single time, it's the classic example of why habit-batching is the way to go. What you would do is Write -> Make a screenshot and name it by number -> Write a quick note in Markdown with the number corresponding to the screenshot (e.g. [!1]) -> continue writing.
Only later would you move all the screenshots together. We can even write a simple script to change their names automatically. And file paths to screenshots can be automated with a macro.
I'm guessing you made it sound inefficient intentionally just to make a point, but I really hope nobody's documenting like that, cause that'd be miserable lol.

[@jherr]

Kinda depends on the complexity of the documentation for me, if it's short then I'll do something like this, if it's really long then yeah, I'd probably screenshot as I go and then stitch it together later. But, what I do find is that I often forget to get a critical screenshot along the way and I need to redo up to that point after. Which is something that is completely avoided by Scribe because Scribe records everything.

[@Gigusx]

@@jherr It's definitely solving a few problems! I think that the sweet spot will be somewhere in the middle, still, with the kind of visual aid that Scribe offers and longer-form text. Either way, I still have to play around with Scribe but the recording feature looks great.

[@r.h.u.k.a]

Nahhhh I'll continue using Notion heheh

[@DanteMishima]

Docusaurus hasn't steered me wrong so far

[@lardosian]

@@DanteMishima We use Docusaurus as well.

[@Kermin00]

I believe that your email leaked at 8:03.

[@jherr]

I do try to obscure it, but it's an open "secret". I get direct emails from viewers all the time.