Commit a11d0268 authored by Bernd Taschler's avatar Bernd Taschler
Browse files

fix more relative links

parent e99c476a
Pipeline #13835 passed with stages
in 2 minutes and 8 seconds
......@@ -20,7 +20,7 @@ Markdown is a simple syntax for formatting text and adding graphics to documenta
Using markdown also supports you to use "heading" identifiers, rather than simply changing the font size. This is because it is so *easy* to use heading syntax and it is comparatively complex to change a font size! This makes for content which is more accessible to screen readers used by individuals with a visual impairment ✌🏻 ✌🏼 ✌🏽 ✌🏾 ✌🏿
Markdown is used by GitHub to translate your text and formatting into webpage (GitHub Pages) content. You will be writing your documentation (maybe in [Atom](1-3-atom.md)) using markdown syntax, and it will automatically be rendered into something beautiful on your Pages site.
Markdown is used by GitHub to translate your text and formatting into webpage (GitHub Pages) content. You will be writing your documentation (maybe in [Atom](../1-3-atom)) using markdown syntax, and it will automatically be rendered into something beautiful on your Pages site.
There are *many* markdown tutorials online which you can follow. I've listed the syntax I use most commonly below:
......
......@@ -20,9 +20,9 @@ Currently your "test-git-project" exists online and your computer is configured
In your terminal, move to the directory where you would like your local version of the repository to be stored. Enter the "Create a new repository" commands into your terminal, one line at a time.
Note you will be asked for the SSH key password you generated when you [first accessed your gitlab account](2-1-starting-gitlab-account.md).
Note you will be asked for the SSH key password you generated when you [first accessed your gitlab account](../2-1-starting-gitlab-account).
Below is a brief explanation of what each line is doing. You'll learn more about some of these commands in the [git basics tutorial](2-4-starting-git-basics.md).
Below is a brief explanation of what each line is doing. You'll learn more about some of these commands in the [git basics tutorial](../2-4-starting-git-basics).
After entering these commands, return to the [gitlab webpage](https://git.fmrib.ox.ac.uk) and refresh your project. You will now see that the instructions for creating a new project have gone and the commit message you just entered is shown on the top.
......
......@@ -27,7 +27,7 @@ In the spirit of inclusivity, I'm going to show you the git commands I know, and
## Watch and learn
We're not yet going to actually practice doing these things right now. I'd just like you to become familiar with (memorize?!) them. You'll get a chance to use them when you have a go at [contributing to this repository](3-3-play-with-this-page.md), and again when you [make your pages site](4-2-Make-your-Pages-site.md).
We're not yet going to actually practice doing these things right now. I'd just like you to become familiar with (memorize?!) them. You'll get a chance to use them when you have a go at [contributing to this repository](../3-3-collaborating-play-with-this-page), and again when you make your [GitLab pages](../4-4-create-gitlab-pages-site) or [GitHub pages](../4-3-you-make-your-pages-site) site.
## The three(ish) stages of adding to your repository online
......
......@@ -63,7 +63,7 @@ First confirm you are working on the new branch with the command below:
Then open your text editor and make and save the changes.
Finally, add, commit and save the changes as described in the earlier [git basics](2-4-git-basics.md)
Finally, add, commit and save the changes as described in the earlier [git basics](../2-4-starting-git-basics)
Notice the git gave me a helpful error which told me that it din't know where to push my changes - there was not "upstream branch" - and very kindly told me what commands I need to enter to set the upstream to be this branch on my copy of the repository. Thanks, Git.
......
......@@ -30,7 +30,7 @@ Coming soon
Below is a list of numbers. For your first contribution to someone else's documentation, I would like you to write your name, your pronouns, today's date, and your GitHub profile link against one of these numbers. If you don't know your profile link, click your profile icon (top right side) and open 'Your Profile' in a new tab. You can use the URL of that page to build your GitHub profile link. Use the link format: `[Link text here](LINK URL HERE)`. If you want to get jazzy, you can do something more complicated, like add a picture or some formatting! I invite you to freestyle or keep it functional as you wish.
Use the procedure described earlier to [fork, clone, branch, edit, push, and submit a pull request](../3-2-fork-their-repo.md) to update the lines below.
Use the procedure described earlier to [fork, clone, branch, edit, push, and submit a pull request](../3-2-collaborating-fork-their-repo) to update the lines below.
We're going to assume we're in a "class" setting right now, and I'm expecting your pull requests to come in. I'll accept them as soon as I can! If we're not in an active tutorial, I'll still aim to get to them as soon as I can, but please accept my apologies if it is not instantaneous. Often collaboration is asynchronous!
......
......@@ -15,7 +15,7 @@ How to create a doi in zenodo for your GitLab project
---
*Note this is a duplicate of [tutorial 4.2 Create a doi](4-2-you-doi)*
*Note this is a duplicate of [tutorial 4.2 Create a DOI](../4-2-you-doi)*
Zenodo is free to use tool for creating a digital object identifier (doi) for your shared resources. A doi is essential for enabling other researchers to cite and reuse your material, and for you to receive proper attribution. Your doi entry will include your [ORCID ID](https://info.orcid.org/benefits-for-researchers/), so it can be tracked against all your other research outputs.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment