Aimed predominantly at beginners and intermediates.
Professional build is being removed, but link back to previous versions.
Install. Update. Pandoc builds. Issues.
[ ] Aim to keep issues simple
Personal issues should remain personal (e.g. #102)
Perhaps a tags are enough: "don't worry about this!", "for beginners only", etc
[ ] Simplify initial README so it's easier to digest
Show it, don't say it. Gifs and videos.
Might be wise to move compiler stuff, and "be careful when" to another location? or use <details> to shorten everything down!
Pain points: how to create a card? How to simplify a chunk of code? etc.
From time to time, easiest way for internal links is to hover over link in Visual Studio Code[^2]
This can also be done with the Marked App (external links at least) Preview -> Validate External Links
[x] Semantic Versioning is a useful reminder
44
[x] #135
Make sure the data files work smoothly with Pandoc
I feel the stripped versions are quicker to use.
[^1]: So far the way I've approached this has been unsuccessful. I don't really know how often people are using this tool, or how long it serves them. At least one person has a very old version, and another only needed it for a very short spell.
[^2]: Using a link check tool online is another option, but it display all Github's links too.
[^3]: We're not using templates or anything like that, but it's helpful to note you can change the theme easily if you want to, either by editing the --css-variables or --highlight-style and manually editing the css. I don't think I'll include all the themes by default as some of them are a bit rubbish.
[^4]: If I can't easily do this for both Github and Marked with the same markdown code, I'm not wasting my time. Eventually it might be nice to have a small indy site for this.
<details>to shorten everything down!-stripped.htmlcode (don't copy some of the tags)25
npm, but a couple of notes on how to use Pandoc.[^3]Preview -> Validate External Links44
[^1]: So far the way I've approached this has been unsuccessful. I don't really know how often people are using this tool, or how long it serves them. At least one person has a very old version, and another only needed it for a very short spell.
[^2]: Using a link check tool online is another option, but it display all Github's links too.
[^3]: We're not using templates or anything like that, but it's helpful to note you can change the theme easily if you want to, either by editing the
--css-variablesor--highlight-styleand manually editing the css. I don't think I'll include all the themes by default as some of them are a bit rubbish.[^4]: If I can't easily do this for both Github and Marked with the same markdown code, I'm not wasting my time. Eventually it might be nice to have a small indy site for this.