-
Notifications
You must be signed in to change notification settings - Fork 1k
Creation of a learning pathway for the creation of a sig and codex #6128
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
Creation of a learning pathway for the creation of a sig and codex #6128
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.
Amazing! Thanks a lot @scorreard!!!
I put some comments. My main one would be to remove the community-codex
tutorial so now as I am not sure it works how it is
> 4. Select **Create a new file** | ||
> 5. Fill in the `Name of your file` field with: name of your community + `/metadata/` | ||
> This will create a folder for your community and a new folder for your community called metadata. | ||
> 6. Click on **Commit changes** |
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.
Committing a folder without files in it does not work I think.
One idea: Put the hands-on part until there as a FAQ and add a step "Add your community to the Galaxy CoDex" as a first step for tools, workflows, tutorials.
I would then remove this tutorial.
What do you think?
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.
I moved the hands on part in each tutorial (tools, workflow and tutorials) as the file to create is different each time (and as you said, it's not possible to just create a empty folder). What do you think?
I added a FAQ about "What is a codex" which was the hands-off part of this tutorial
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.
I feel like we should add a section about reviewing the tools in tool_status.tsv
file after. Do you think you could add it?
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.
Are you talking about tools or tutorials?
topics/community/tutorials/community-tutorial-table/tutorial.md
Outdated
Show resolved
Hide resolved
topics/community/tutorials/community-tutorial-table/tutorial.md
Outdated
Show resolved
Hide resolved
topics/community/tutorials/community-tutorial-table/tutorial.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Bérénice Batut <berenice.batut@gmail.com>
Co-authored-by: Bérénice Batut <berenice.batut@gmail.com>
Added Keiler to the contributor list
Co-authored-by: Solenne Correard <54953390+scorreard@users.noreply.github.com>
Co-authored-by: Solenne Correard <54953390+scorreard@users.noreply.github.com>
Co-authored-by: Solenne Correard <54953390+scorreard@users.noreply.github.com>
topics/community/tutorials/community-tutorial-table/tutorial.md
Outdated
Show resolved
Hide resolved
looks good to me! I added support for proper bibtex references, let's get this in and you can add further optimizations later :) Thanks @scorreard @bebatut and @BirdmanRidesAgain! |
The codex training was limited, in order to better guide communities, we created a learning pathway.
Parts of the tuto (include the workflow and tuto tables in the community page) will have to be updated after the All Hands