diff --git a/pages/contribute/editorial_board_guide.md b/pages/contribute/editorial_board_guide.md index c8866563a..a9d426a9b 100644 --- a/pages/contribute/editorial_board_guide.md +++ b/pages/contribute/editorial_board_guide.md @@ -108,12 +108,14 @@ To generate a new page it is sufficient to simply copy the TEMPLATE file in the - add the author names to the contributors list. - optional: change the title into an appropriate one. -1. Describe shortly which changes you made in the description of your commit below the page. Commit to the master branch by clicking `Commit new file`. +1. Describe shortly which changes you made in the description of your commit below the page. Commit to a new branch and click `Commit new file`. {% include image.html file="commit_to_master_github.png" inline=true alt="Commit new file in GitHub." %} +1. Wait till another editor approves your changes. After approval, the branch can be merged and changes will be applied. + 1. If the markdown file is named *example.md* the page will be rendered at https://rdmkit.elixir-europe.org/example. This link can be provided to the contributor through the issue. -{% include callout.html type="note" content="It is not a problem to immediately duplicate pages in the master branch, but be aware that new content always needs to be pushed to another branch which will give you the option to open a pull request." %} +{% include callout.html type="note" content="Always make a new branch when making changes to the website, this to prevent little mistakes and to enforce approval from other editors." %} ### Advanced: working on your own feature branch and pushing local changes diff --git a/pages/contribute/tool_resource_update.md b/pages/contribute/tool_resource_update.md index 4613aa51c..85ca5b933 100644 --- a/pages/contribute/tool_resource_update.md +++ b/pages/contribute/tool_resource_update.md @@ -24,7 +24,7 @@ The table consists of 5 columns: - **description**: A short description of the tool or resource. Try to not use the characters `"` or `'` - **registry**: 3 registries are supported: [Bio.tools](https://bio.tools), [FAIRsharing.org](https://fairsharing.org/) and [TeSS](https://tess.elixir-europe.org/). The keywords you can use respectively are: `biotools`, `fairsharing`, `fairsharing-coll` and `tess`, specifying the id or query with a colon). FAIRsharing collections have an ID that follows the pattern `bsg-s000XXX`. List multiple registries using a comma `, ` between the keywords to separate the key:value pairs. The values that are given in the table will always overrule the automatic links. If no FAIRsharing ID, Bio.tools ID or TeSS Query is available for a source, you can overwrite the automatic linking by adding 'NA' as registry. - **related_pages**: This is used to tag the tools so it is listed on the correct page. We only allow page_id that are linked to a page. To find out what the page_id of a page is, please check its metadata attribute `page_id` at the top of the markdown file or the [Website overview](website_overview) page. Since the Data life cycle pages are not listing tools, we do not allow these page_id in the tool table. page_id allowed in the tool table are page_id from the following sections: `Your domain`, `Your role`, `Your tasks` and `Tool assembly`. List multiple page_id by using a comma `, ` between them. -- **country** : If a tool can only be used in a specific country, list those countries with there Alpha-2 code. For a complete list of all country code please visit the [IBAN](https://www.iban.com/country-codes) website. A flag will appear in the `related pages` column. + | name | url | description | registry | related_pages | |----------|----------------------------------|-------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------------|