Remove hand-made TOC since there is now an automatic one available, r…

[WildGenius]

…eorganise and lightly edit sections, add link to Nabhan native PDF vid, add link to Dunlosky et al. paper, add link to comparison of Evergreen notes to Zettelkasten, add link to another implementation example forum topic.

GitHub tweet announcing automatic TOC https://twitter.com/github/status/1376636651963842562 If you plan to add a publishing form to your css library anytime soon, feel free to edit it back, otherwise it seems a bit misleading to have "share" there. If it's not too brazen of me, could you move (some) TODOs to a private fork? I assume you don't want other people seeing them, though there are a few useful placeholders. Also some trivial style edits.

[hannesfrank]

Thanks @WildGenius for all your effort! I agree with your changes. The builtin TOC is awesome!

I just "reverted" two changes to keep the idea of an awesome list being an index into a topic:

• Keep the links to other platforms in the front as opposed to the tutorials. I see that tutorials are the first thing you need, but the link list is short enough be easily scrollable.
• Unabbreviated the description: I think explicitly naming the important parts helps (like an index does).

I don't mind people seeing (most of) the todos. Maybe someone will actually do them some day :p I'll look through them when I find time and add them as issues if they are of "help wanted" type.