Oh, that is awesome. Thank you so much.
1 Like
Created a simple doc as a cheat sheet for the Tutorial Maker with images to give people some visuals of what the markdown do. Please let me if I am missing anything and I will try my best to keep this up-to-date
2 Likes
Oh, wow! That’s super cool! Would you mind if I build off of this for my Tutorial Tutorial?
Not at all, please use it. I plan on adding to it to show how to connect it to github for uploading images/gifs/videos and creating skill maps for educators.
This is great, thanks for sharing. Does anyone have any guidance for making blocks in extensions work? I’m building tutorials for microbit makecode and want to use some extensions. I tried the packages code suggested here: https://makecode.com/writing-docs/snippets#package but that did not work. I may have done it wrong. Any guidance or suggestions would be appreciated.
That is the format to use; e.g. one of our built in examples loading a repo: https://github.com/microsoft/pxt-microbit/blob/63df3029a60b8cb11576b3caeb0c9eb390c1b91d/docs/projects/turtle-spiral.md?plain=1#L31 or a built in package pxt-microbit/docs/reference/radio/packet.md at 63df3029a60b8cb11576b3caeb0c9eb390c1b91d · microsoft/pxt-microbit – if you can share the tutorial you’re trying we can figure out what’s missing
Thanks for the examples. I’m doing something wrong. Here is the result: https://bmoran23.github.io/microbittutorialnoisesense/noiseTutorial
See how the extension blocks are grey and just show text.
And here is the markdown: https://github.com/bmoran23/microbittutorialnoisesense/blob/master/noiseTutorial.md?plain=1
Any idea what I’m doing wrong?
hm, plugging in the text to the tutorial tool does work, which leaves me to think it’s an with the other files in the extension – for tutorials loaded from github they get added as a normal extension, so the pxt.json imports / main.ts also apply. When i load that tutorial from github into a project, it ends up as https://makecode.microbit.org/_HXLV6vPdpK8K, which is pegged to 0.0.1 released 2 days ago
Releasing a new version should work (but also check to confirm that e.g. you want the code that currently exists in main.ts)