-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorial gawen #36
Tutorial gawen #36
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great tutorial!
Since this is a collaborative effort, if someone wants to add or change something, they are able to do so.
The only thing I'm not sure about is, where we should store images that belong to the documentation. We could also store them in the same directory as the document itself, which will make it easier to reference them in Markdown rather than having to go two directories up first.
Not sure why the Github Actions "check" fails. I actually dont even remember why it is there ... but it was me who added it ;-) |
I agree. I am going to change this. |
Fixes #35 .
Changes proposed in this pull request:
It is a pretty long tutorial. I would like feedbacks :
-...
I decided to do the tutorial on a data pretty hard to exploit ; if needed, I can do it again with an easier data structure.
There may be English mistakes, I will try to correct them later.