A Contents page would really help the tour

[mark-summerfield]

I really like the tour, especially the fact that you can run and tweak the code as well as read the explanations.

However, what I really miss is a contents page so that I can look at each topic and jump back when I want to recap something. Another advantage of a contents page is that it allows people to see how much they've covered and how much is still to go. The contents could be grouped (as the tour is) so that people can see when they've covered the basics and then each of the further topics.

[PetarKirov]

I really like the tour, especially the fact that you can run and tweak the code as well as read the explanations.

Hi @mark-summerfield, I'm glad you liked it :)

However, what I really miss is a contents page so that I can look at each topic and jump back when I want to recap something. Another advantage of a contents page is that it allows people to see how much they've covered and how much is still to go. The contents could be grouped (as the tour is) so that people can see when they've covered the basics and then each of the further topics.

I'm not sure whether you know, or perhaps you're talking about something different, but the header of the page has a dropdown menu where you can see the table of contents and jump to a different chapter:

I agree that it may be nice to have the tour track which pages you have visited and how many remain. Additionally, there could be a dedicated topics & features page from where you could jump to the first page where something was explained.

[mark-summerfield]

I hadn't seen that. Unfortunately, I first clicked the "D by Examples" menu and that has a single entry, so I wrongly assumed the rest were like that.
So contents is there after all in the menus. I still think a single Contents page would be good though with a link to the left of the Welcome menu and that had links to all the rest.