Remove 'try as tutorial' link/button for docview

[ganicke]

Remove the "Try this tutorial" button/links due to malformed URL's when opened in sidedocs vs. docs view. If it's desired to keep these, then we could modify the open url logic in the render.

Erroneous URL formed from sidedocs view:

https://arcade.makecode.com/---docs#doc:#tutorial:/tutorials/chase-the-pizza

...from markdown:

### ~button /#tutorial:/tutorials/chase-the-pizza

Try this tutorial!

### ~

RE: #6604 (comment)

[kiki-lee]

I would much rather that we fixt the URL

[Jaqster]

There's a lot wrong with these pages (in addition to the link being wrong in the side docs view).
For example, for this page https://arcade.makecode.com/tutorials/chase-the-pizza I saw -

• some markdown tags not getting parsed correctly
  

• some emojis not showing up
  

• weird nested table for each step
  

• some blocks not rendering correctly and then showing up throughout the tutorial steps
  

• bullet point formatting in some places
  

I'm trying to pull some metrics to see how popular these pages are and whether it's worth it to fix them or just trash them.

[ganicke]

The document renderer hasn't kept up with the markdown changes to support tutorials. These don't really serve as document pages as they are almost always launched as tutorials. In the past, there was parity with viewing tutorial markdown as a page and running it as a tutorial. We're past that now. Maybe it's time to implement something like ### @tutorialOnly true in the markdown so it's "virtually" removed from the document space.

[Jaqster]

Okay, let me pull the usage data, and we can figure out what we want to do here based on that.

[Jaqster]

Okay, so it looks like a significant amount of people in the last month went to these pages. So we can't kill them. @ganicke - what's the minimal amount of work we could do to update the renderer (or just manually fix a couple of the most popular tutorial docs pages)? I do think having a @Tutorialonly flag going forward would be good too.

[ganicke]

@Jaqster - I guess these standalone tutorials still have some longevity to them. Since they've been optimized by @kiki-lee as tutorials, I'd hate to modify them down just so they render well as doc pages.

Hmm, let's see what we might do -

1. We could remove ./tutorials/ from the document tree such that this subpath is only valid for non-document type requests (using an exclusion rule, redirect, etc.).
2. We could make document view only versions (copies) of these, put them in their own subpath ./tutorial-pages/, and dumb down the markdown a bit to make the render work properly.
3. Update the render code to better display (document view) the markdown elements that aren't working now (headings, emojis, that crazy div stacking, etc). This is a bit of dev work.

[Jaqster]

@riknoll - do you have a feel for the level of effort option 3 would be to update the docs markdown renderer? If it's too much work, then I would say option 2 sounds good if we can redirect (I don't know how people are finding these links).

[riknoll]

it's a decent chunk of work, but probably a good idea in the long term. i'd really like to see us unify our markdown parsing code a bit more. right now it's split between the webapp and our docs code which is why we have disparities like this.

that being said, it's probably too much work for this release. we should still plan to do this at some point though.

[Jaqster]

Okay. I just created a bug so we don't lose it for next time - #6676. Galen, you can probably just close this PR.

[ganicke]

Close this PR as updates to doc rendering will address the problems discussed here.