Tutorial Creators

Educators' Lounge
41

OK; so you have a few things happening here, @rymc88 . Feel free to take a look at my fork at https://github.com/alex-kulcsar/Unit-1-Skillmap. Skillmap URL remains similar to yours: https://arcade.makecode.com/--skillmap#github:alex-kulcsar/Unit-1-Skillmap/blob/master/skillmap.md

A few tips that I discovered while working with your incredible skillmap.

  • Test your skillmaps and tutorials in private / incognito windows. Any problems with permissions should surface this way.
  • The MakeCode servers may cache your skillmap and/or tutorials. Because of that, you will need to push a new release anytime you make a change. That brings me to my next tip!
  • You really need to do the source management through a MakeCode editor. The pxt.json file is crucial to your tutorials and skillmaps working. If it is malformed or if something is missing, then something is bound to break.
    • Once you create the project in a MakeCode editor and push it to GitHub, then you can use any tool that you like to edit existing files.
    • To add new Markdown files, use the file explorer tool within a MakeCode editor. This will ensure that the pxt.json file gets updated correctly.
    • You can use another git management tool to push assets (e.g., images) to your repo.
    • Use a MakeCode editor to push new releases of your project. Creating a release using standard git tools will not purge cached data.

Here is a list of changes that I made to your repo in order to get my version to work.

  1. Open the GitHub repo in MakeCode Arcade. It looks like you already have authored at least part of the project from the MakeCode Arcade editor, so the repo should load into your editor just fine for you.
  2. Create your tutorial files (e.g., Lab-1-2.md) using the file explorer tool in the editor. Note that this will create new files in the root of your repo.
  3. Copy the code from your existing tutorial files and paste into the new ones that you created.
  4. Adjust the URLs for the nodes / activities.
    • You can simplify the URLs. Instead of pointing to the file blob, just point to the tutorial file without the .md extension. For example, the activity link to Lab 1.2 would be https://github.com/rymc88/Unit-1-Skillmap/Lab-1-2.
    • URLs to other assets (e.g., images) still need to point to the raw assets, as you have already done.
  5. Commit the changes and publish a new release of your project using the tools in the MakeCode editor.

Most of these tips are in the MakeCode documentation, but they’re a bit scattered right now. I know that @KIKIvsIT is working really hard on pulling documentation together for writing awesome skillmaps and tutorials like yours. I’m thinking we may need to create a workshop, too. :wink: :wink:

Again, great job, @rymc88 ! I’m really happy that you’re turning some of these lessons and units from our TEALS curriculum into skillmaps and tutorials.

Holler if you need anything.

1 Like