git lfs in README

[ClFeSc]

Closes #40

[Dassderdie]

I abused this branch for a bit more documentation stuff - look at the last two commits.

[Dassderdie]

Also: should we maybe change all the npm i into npm ci? This would make sure that all changes in the dependencies are happening deliberately. You should then only run npm i if you know what you're doing. - nevermind - it seems like npm i shouldn't change the package-lock.json (anymore): npm/cli#564 (comment)

[Dassderdie]

@ClFeSc By default the images tracked by git lfs wouldn't render in vscode changes view.
I found git-lfs/git-lfs#440 (comment) . With the command git config diff.lfs.textconv cat it works. Do we want to persist that in the readme too?

I'm not quite sure about the consequences... here (third last point) is the official documentation from git lfs.

[ClFeSc]

@ClFeSc By default the images tracked by git lfs wouldn't render in vscode changes view. I found git-lfs/git-lfs#440 (comment) . With the command git config diff.lfs.textconv cat it works. Do we want to persist that in the readme too?

I'm not quite sure about the consequences... here (third last point) is the official documentation from git lfs.

It worked for me. I don't think there should be a major drawback to using/recommending it.

[ClFeSc]

You're additions look good.

[Dassderdie]

I added it in the last commit.

[Dassderdie]

LGTM