Turn 'core functionality' into a cheatsheet

[penelopeysm]

core functionality includes some not very core functionality. also the demonstrations are a bit too complex imo

I think it makes sense to turn it into a cheatsheet, 'learn Turing in 5 minutes' kind of thing (see https://learnxinyminutes.com/), and each section in it should link to more thorough docs on the page

that way it becomes something where

1. new users can quickly gauge what Turing is capable of doing

2. existing users who just need a refresher on syntax can see it immediately without wading through loads of text

3. the text is grouped onto individual pages nicely

[shravanngoswamii]

I’d love to see this happen. Let me know how I can help!

[penelopeysm]

A first step might be to just enumerate the topics that we want to cover. e.g.

• model definition
• conditioning and fixing
• MCMC sampling
• optimisation
• VI
• ...

then check which of those have docs pages, and write those that don't exist yet.

[shravanngoswamii]

I will work on this -- do you have any suggestions like we add this in current quarto site or make something cool using Astro or maybe Svelte ...

[penelopeysm]

I don't think I had anything fancy in mind -- I pretty much just wanted to reorganise and streamline content. Did you have something else in mind?

[shravanngoswamii]

I am not sure, just had a thought about making something cool -- some visual simulations, maybe Pluto notebooks or something like this use of Pluto: https://computationalthinking.mit.edu/Fall24/
Or a Astro site doing something same. Maybe video tutorials explaining how things work -- there is not much content in video form for Turing. Like explaining what Turing is capable of and perform some really cool experiments with it...

Ideas are scattered right now!

[penelopeysm]

I didn't intend to do anything fancy. That said, I think you should feel empowered to try things out if you have ideas. From a technical perspective I think it would be better if that was self-contained on a different repo. The docs repo is already fairly complicated and I would rather we not mix and match frameworks (we will always need Quarto for code execution so there's no getting rid of that). There is also an added maintenance cost, the team is very small right now and web dev experience is pretty much you and I, so you would have to be willing to maintain what you write (this includes regular updates eg whenever a new Turing version is released). If that's okay with you, though, you should feel free to go ahead and experiment.

[shravanngoswamii]

Ohkay, Let me try something! Happy to maintain what I write and other things that I understand better...