-
Notifications
You must be signed in to change notification settings - Fork 95
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
Create a folder with common mistakes for beginners #105
Conversation
In this folder we will include common mistakes and missconceptions about the way we use Unikraft/kraft and try to also offer some solutions to them. Signed-off-by: Andrei Mutu <andrei.mutu@stud.acs.upb.ro>
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.
Hi @mandrei12, thank you for this.
Few comments:
- The start of the
index.md
file should look similar to other session index files.
Take this example.
It should have a title and a link name. - The
index.md
file should also include the other small files (USoC.md
in this example) by using thereadfile
shortcode.
Look here for an example.
There should be a title inside theindex.md
file that describes the mistake shortly, then thereadfile
shortcode just adds the content to the page.
This is done in order to be able to include the small files in other places, like sessions, docs, etc. - The
USoC.md
file should be placen inside acontent/
directory and should be named differently.
The name should be a 3-4 word description of the problem itself (e.g.Unikraft-branch-layout
or something along those lines).
For every comment above, you can check the structure of a hackathon session, this directory should look very similar.
I'm adding here draft items to add to the PR:
|
Superseded by #391 |
In this folder we will include common mistakes and missconceptions
about the way we use Unikraft/kraft and try to also offer some
solutions to them.
Signed-off-by: Andrei Mutu andrei.mutu@stud.acs.upb.ro