Substitute relative paths with absolute links.

docs/ACKNOWLEDGEMENTS.md

@@ -36,5 +36,5 @@ We promote the use of the [Tenzing webapp](https://rollercoaster.shinyapps.io/te
 
 Figures have been created from images in the [Noun Project](https://thenounproject.com) repository, contributed by [Alice Design](https://thenounproject.com/rose-alice-design/), [Andrejs Kirma](https://thenounproject.com/andrejs/), [DinosoftLab](https://thenounproject.com/dinosoftlab/), [Luis Prado](https://thenounproject.com/Luis/), [Sergey Demushkin](https://thenounproject.com/mockturtle/), [Thuy Nguyen](https://thenounproject.com/milkghost/), [vectlab](https://thenounproject.com/vectlabmail/), and [Victor Llavata Bartual](https://thenounproject.com/victor.llavata/). 
 
-The pages are regularly updated by the [Open Science Ambassadors](../community/ambassadors/). The last major update was made on June 2024 by [Anna Guttesen](https://orcid.org/0000-0003-0284-1578), [Lara Nikel](https://www.ndcn.ox.ac.uk/team/lara-nikel), [Lilian Weber](https://orcid.org/0000-0001-9727-9623), [Ying-Qiu (Akina) Zheng](https://orcid.org/0000-0003-1236-0700), [Juju Fars](https://orcid.org/0000-0001-7771-5029), [Bernd Taschler](https://orcid.org/0000-0001-6574-4789), [Yingshi Feng](https://orcid.org/0000-0001-9065-4945).
-We thank them for all the work they have put to make this possible. 
\ No newline at end of file
+The pages are regularly updated by the [Open Science Ambassadors]({% link docs/community/ambassadors.md %}). The last major update was made on June 2024 by [Anna Guttesen](https://orcid.org/0000-0003-0284-1578), [Lara Nikel](https://www.ndcn.ox.ac.uk/team/lara-nikel), [Lilian Weber](https://orcid.org/0000-0001-9727-9623), [Ying-Qiu (Akina) Zheng](https://orcid.org/0000-0003-1236-0700), [Juju Fars](https://orcid.org/0000-0001-7771-5029), [Bernd Taschler](https://orcid.org/0000-0001-6574-4789), [Yingshi Feng](https://orcid.org/0000-0001-9065-4945).
+We thank them for all the work they have put to make this possible. 

docs/CONTRIBUTING.md

@@ -18,7 +18,7 @@ This repository is designed to be used by members of the Wellcome Centre for Int
 
 ---
 
-We want to ensure that every user and contributor feels welcome and included in the WIN Open Neuroimaging community. We ask all contributors and community members to follow the [code of conduct](../community/CODE_OF_CONDUCT) in all community interactions.
+We want to ensure that every user and contributor feels welcome and included in the WIN Open Neuroimaging community. We ask all contributors and community members to follow the [code of conduct]({% link docs/community/CODE_OF_CONDUCT.md %}) in all community interactions.
 
 **We hope that this guideline document will make it as easy as possible for you to get involved.**
 
@@ -30,11 +30,11 @@ If you are a WIN member you can join us on the slack channel of the WIN Communit
 
 ## 2. Check what we're working on
 
-We invite you to review our [roadmap](../community/roadmap) and see how we are progressing against our community milestones.
+We invite you to review our [roadmap]({% link docs/community/roadmap.md %}) and see how we are progressing against our community milestones.
 
 ## Or, 3. Jump straight in!
 
 If you are confident using git, markdown, and GitLab pages, you are very welcome to [submit an issue to our GitLab repository](https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues), and submit a merge request.
 
 ### New to GitLab?
-If you'd like to try out GitLab at your own pace, take a look at the [training materials available here](../gitlab).
+If you'd like to try out GitLab at your own pace, take a look at the [training materials available here]({ link docs/gitlab.md %}).

docs/ELN.md

@@ -14,7 +14,7 @@ sub heading
 
 ---
 
-![tools](../../img/logo-labarchives.png)
+![tools]({% link img/logo-labarchives.png %})
 
 Laboratory notebooks document the process of experimentation and discovery, and may be maintained as a legal document admissible as evidence in court of law  (https://en.wikipedia.org/wiki/Electronic_lab_notebook). As such, there is a drive to promote the use of electronic laboratory notebooks (ELNs) over paper lab notebooks to improve fidelity, access and interoperability of this valuable information. Standards have been developed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) to describe minimum requirements in controlling access and editing of entries into an ELN; ELNs providers can apply to be accredited under a given ISO/IEC specification, giving users confidence that the information they enter into them is managed appropriately.
 

docs/ambassadors/application.md

@@ -27,7 +27,7 @@ Below we describe the application process, including how your application will b
 
 Please take note of the [timeline](#timeline). If you apply to the programme, please keep the date of the first meeting free in your schedule.
 
-Please review the notes on [eligibility](../logistics#who-can-be-an-ambassador) and [time commitment](../expectations#time-commitment) before applying.
+Please review the notes on [eligibility]({% link docs/ambassadors/logistics.md %}) and [time commitment]({% link docs/ambassadors/expectations.md %}) before applying.
 
 When you apply you will be asked to confirm that you have discussed your application with your supervisor or line manager and that they are supportive of your participation in the Ambassadors programme.
 
@@ -54,7 +54,7 @@ The above linked application form asks 3 questions to assess your interest and i
 
 Please note that no prior experience with open science related projects or activities is required!
 
-You will then be asked to let us know about any logistical constraints you might have with participation according to our [proposed schedule](../programme#schedule).
+You will then be asked to let us know about any logistical constraints you might have with participation according to our [proposed schedule]({% link docs/ambassadors/programme.md %}).
 
 We would like our Ambassadors to represent the full diversity of our community. We therefore ask applicants if they consider themselves to be a member of one or more historically excluded groups. We will also ask for your career stage, to ensure we get diverse representation.
 

docs/ambassadors/expectations.md

@@ -31,9 +31,9 @@ We would like WIN Open Ambassadors to undertake the following activities:
 - Contribute to WIN Open Science policy.
 
 ## Time commitment
-- Participate in Ambassadors meetings as per the [published schedule](../programme#schedule).
+- Participate in Ambassadors meetings as per the [published schedule]({% link docs/ambassadors/programme.md %}).
 - Engage in training, advocacy, and contributing to the Open WIN infrastructure for 3-4 hours per month, in addition to regular meetings (mostly on MS Teams).
 
-In return for their time and commitment, various [rewards and incentives](../benefits) will be offered to the Open WIN Ambassadors. We will continually reflect on and refine our expectations and commitments as we learn from our experience.
+In return for their time and commitment, various [rewards and incentives]({% link docs/ambassadors/benefits.md %}) will be offered to the Open WIN Ambassadors. We will continually reflect on and refine our expectations and commitments as we learn from our experience.
 
 We will work to support Ambassadors in all these activities, with communication channels, training, presentation materials and defined routes of development. This support will develop as the project grows, and you will have an open invitation to suggest any additional ways we could support you in growing our community.

docs/ambassadors/goals.md

@@ -36,7 +36,7 @@ The Open WIN Ambassadors programme is an essential component in achieving the vi
 
 ### 1. Growing our user base
 
-Our overarching goal is to increase the number of users of our [sharing infrastructure](../../tools), so more people can share all stages of their research output, and receive appropriate credit for doing so. This will help us achieve the Open Neuroimaging Project goal of increasing the openness of our research, to facilitate discovery and accelerate the translation of methods and results to the clinic.
+Our overarching goal is to increase the number of users of our [sharing infrastructure]({% link docs/tools.md %}), so more people can share all stages of their research output, and receive appropriate credit for doing so. This will help us achieve the Open Neuroimaging Project goal of increasing the openness of our research, to facilitate discovery and accelerate the translation of methods and results to the clinic.
 
 One of the most effective ways of growing our user base is to capitalise on the skills, reach and influence of a select group of "power users", who can advocate for local change and represent the interests of their colleagues. These power users (our Ambassadors) will have the best understanding of what others needs to see, feel, and experience in their journey in order to successfully adopt an effective open science practice.
 
@@ -187,16 +187,16 @@ Open Community
 - Encourage the community to share pre-prints of their papers.
 
 
-![OS-Survey 2019 slide 3](../../img/open-science-survey-results/Slide3.png)
+![OS-Survey 2019 slide 3]({% link img/open-science-survey-results/Slide3.png %})
 
 - Appreciate the value of open science practices in career development
 
-![OS-Survey 2019 slide 4](../../img/open-science-survey-results/Slide4.png)
+![OS-Survey 2019 slide 4]({% link img/open-science-survey-results/Slide4.png %})
 
 - Appreciate the value of open sharing of code.
 - Encourage the community to realise the value of sharing data within the current limits of our [open data policy](OpenData.md), and equip them with the tools and knowledge to do so.
 
-![OS-Survey 2019 slide 5](../../img/open-science-survey-results/Slide5.png)
+![OS-Survey 2019 slide 5]({% link img/open-science-survey-results/Slide5.png %})
 
 ## Reduce barriers to engaging in open research practices
 
@@ -204,12 +204,12 @@ Open Community
 - Clarify and communicate legal and ethical obligations fo data sharing.
 - Promote and train the community to use the newly developed WIN Open Infrastructure for sharing [data](OpenData.md), [experimental paradigms](OpenParadigms.md), [MR protocols](OpenProtocols.md) and [analysis tools](OpenTools.md)
 
-![OS-Survey 2019 slide 6](../../img/open-science-survey-results/Slide6.png)
+![OS-Survey 2019 slide 6]({% link img/open-science-survey-results/Slide6.png %})
 
-![OS-Survey 2019 slide 7](../../img/open-science-survey-results/Slide7.png)
+![OS-Survey 2019 slide 7]({% link img/open-science-survey-results/Slide7.png %})
 
 ## Create and share documentation
 - Empower the community to learn together as we explore these topics, and share their knowledge on this repository <mark>update when moved</mark> in the form of written documentation.
 - Hold in-person and online training workshops and "hacks" where we can learn together and create documentation.
 
-![OS-Survey 2019 slide 8](../../img/open-science-survey-results/Slide8.png) -->
+![OS-Survey 2019 slide 8]({% link img/open-science-survey-results/Slide8.png %}) -->

docs/ambassadors/logistics.md

@@ -39,7 +39,7 @@ While working on creating documentation, we envisage teams of two people or more
 
 Ambassadors will be encouraged to work openly and publish their work-in-progress via GitLab. Training will be given to ensure all Ambassadors are comfortable and confident with this process.
 
-Ambassadors will be encouraged to join 30-60 minute update and co-working calls, where we will work together on documentation and projects. Calls will take place on MS Teams and we will use [hackmd.io](http://hackmd.io/) to write collaborative notes during the call, using markdown so they can be saved directly to a git repository. We may use [padlet](https://padlet.com) for creative exercises. Take a look at the [programme schedule](../programme) to see how our calls will be structured.
+Ambassadors will be encouraged to join 30-60 minute update and co-working calls, where we will work together on documentation and projects. Calls will take place on MS Teams and we will use [hackmd.io](http://hackmd.io/) to write collaborative notes during the call, using markdown so they can be saved directly to a git repository. We may use [padlet](https://padlet.com) for creative exercises. Take a look at the [programme schedule]({% link docs/ambassadors/programme.md %}) to see how our calls will be structured.
 
 # How long will Ambassadors be in-post for?
 
@@ -49,7 +49,7 @@ The programme will run for roughly one calendar year. All recruited Ambassadors
 
 Anyone! Student, postdoc, core staff, professional services, PI...!
 
-You do not need to have any knowledge or experience of open science. All we ask is that you are interested in contributing your time and energy to support the development of others. But this is not an entirely altruistic affair! By participating in this programme we expect you will directly [benefit](../benefits) in ways which are valuable to your career development and skills as a researcher. It should also be a fun and rewarding experience!
+You do not need to have any knowledge or experience of open science. All we ask is that you are interested in contributing your time and energy to support the development of others. But this is not an entirely altruistic affair! By participating in this programme we expect you will directly [benefit]({% link docs/ambassadors/benefits.md %}) in ways which are valuable to your career development and skills as a researcher. It should also be a fun and rewarding experience!
 
 # How can I become an Ambassador?
 
@@ -57,4 +57,4 @@ A competitive application for the 2025 cohort will be launched in November 2024.
 
 # What is expected of Ambassadors
 
-Take a look at the [expectations](../expectations) of Ambassadors to learn more about the time commitments of participation.
+Take a look at the [expectations]({% link docs/ambassadors/expectations.md %}) of Ambassadors to learn more about the time commitments of participation.

docs/ambassadors/meet_ambassadors.md

@@ -19,20 +19,9 @@ Find out about the current Open WIN Ambassadors
 
 <div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/1025477303?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="What does it mean to be an Open WIN Ambassador?, October 2024"></iframe></div><script src="https://player.vimeo.com/api/player.js"></script>
 
-<!--
-![](../../img/OPEN_WIN_AMBS_PROMO_2024.mp4)
-
-<iframe width="560" height="315" src="https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/blob/33d22c4573b91146a28704164aac85371b49f73a/img/OPEN_WIN_AMBS_PROMO_2024.mp4" frameborder="0" allowfullscreen></iframe>
---- 
-
-<video width="320" height="240" controls>
-  <source src="../../img/OPEN_WIN_AMBS_PROMO_2024.mp4" type="video/mp4">
-</video>
--->
-
 ## The 2024 Ambassadors
 
-![Open WIN Ambassadors 2024](../../../img/img-ambassadors-2024.png)
+![Open WIN Ambassadors 2024]({% link img/img-ambassadors-2024.png %})
 {: .fs-3 .fw-300 }
 
 ### Anna Guttesen
@@ -59,7 +48,7 @@ Ying-Qiu (Akina) is a postdoctoral researcher in the Nuffield Department of Clin
 
 ## The 2022-2023 Ambassadors
 
-![Open WIN Ambassadors 2023](../../../img/img-ambassadors_2023.png)
+![Open WIN Ambassadors 2023]({% link img/img-ambassadors_2023.png %})
 {: .fs-3 .fw-300 }
 
 ### Peter Doohan
@@ -96,7 +85,7 @@ Mohamed is a Senior Physics Support Scientist (Clinical and Pre-clinical) in the
 
 ## The 2021-2022 Ambassadors
 
-![Open WIN Ambassadors 2022](../../../img/img-ambassadors-2022-horizontal.png)
+![Open WIN Ambassadors 2022]({% link img/img-ambassadors-2022-horizontal.png %})
 Open WIN Ambassadors 2021-2022 (left-right): Dejan Draschkow; Yingshi Feng; Verena Sarrazin; Bernd Taschler.
 {: .fs-3 .fw-300 }
 

docs/ambassadors/programme.md

@@ -58,12 +58,12 @@ You may choose to contribute outside of this time, or arrange co-working times w
 <!--
 ## Shadowing
 
-In response to feedback from the 2021-2022 Ambassadors, we have incorporated various opportunities for you to shadow the work of our Community Engagement Coordinator, so you can learn about the operational aspects of doing open science and supporting the wider community. You will be invited to attend the termly [Open WIN Steering Group](../../community/community-who/#open-win-steering-group) meetings, join one-to-one support meetings with researchers seeking to incorporate open science practices in their work, and join a team inbox.
+In response to feedback from the 2021-2022 Ambassadors, we have incorporated various opportunities for you to shadow the work of our Community Engagement Coordinator, so you can learn about the operational aspects of doing open science and supporting the wider community. You will be invited to attend the termly [Open WIN Steering Group]({% link docs/community/community-who.md %}) meetings, join one-to-one support meetings with researchers seeking to incorporate open science practices in their work, and join a team inbox.
 -->
 
 ## Launch and close meetings
 
-In January 2025 you will join the Ambassadors of previous years for a formal introduction to the Open WIN ambassadors programme (delivered by the [Open WIN Steering Group](../../community/community-who#open-win-steering-group), hear the results of our [programme evaluation](../goals/#evaluation-of-the-programme-and-your-experience) and share your expectations and goals for the year ahead. These activities will be held at a College in January 2025, in an informal environment where we can celebrate each others success and contributions, hear from external speakers and have dinner together.
+In January 2025 you will join the Ambassadors of previous years for a formal introduction to the Open WIN ambassadors programme (delivered by the [Open WIN Steering Group]({% link docs/community/community-who.md %}), hear the results of our [programme evaluation]({% link docs/ambassadors/goals.md %}) and share your expectations and goals for the year ahead. These activities will be held at a College in January 2025, in an informal environment where we can celebrate each others success and contributions, hear from external speakers and have dinner together.
 
 ## Schedule
 

docs/analysis.md

@@ -15,7 +15,7 @@ How to share reproducible FSL analysis pipelines
 
 ---
 
-![open-analysis](../../img/img-open-anal-flow.png)
+![open-analysis]({% link img/img-open-anal-flow.png %})
 
 ## Purpose
 
@@ -47,21 +47,19 @@ Coming soon
 
 <br>
 
-<!-- [![For WIN members](../../img/btn-win.png)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/analysis/#for-win-members)      [![For external researchers](../../img/btn-external.png)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/analysis/#for-external-researchers) -->
-
-[![For WIN members](../../img/btn-win.png)](#for-win-members)      [![For external researchers](../../img/btn-external.png)](#for-external-researchers)
+[![For WIN members]({% link img/btn-win.png %})](#for-win-members)      [![For external researchers]({% link img/btn-external.png %})](#for-external-researchers)
 
 ## For WIN members
 ### Benefits
-#### Version control ![version-control](../../img/icon-version-control.png)
-WIN members will be encouraged to develop their analysis pipelines into standalone scripts and store these on the [WIN GitLab instance](https://git.fmrib.ox.ac.uk). We will support our members in using git to version control their code, and employ best practice in ensuring their pipelines are robust and accurate. Find out more about [using GitLab](../gitlab)
+#### Version control ![version-control]({% link img/icon-version-control.png %})
+WIN members will be encouraged to develop their analysis pipelines into standalone scripts and store these on the [WIN GitLab instance](https://git.fmrib.ox.ac.uk). We will support our members in using git to version control their code, and employ best practice in ensuring their pipelines are robust and accurate. Find out more about [using GitLab]({% link docs/gitlab.md %})
 
-#### Citable research output ![doi](../../img/icon-doi.png)
-Versions of analysis code can be assigned a digital object identified (DOI) using [Zenodo](https://zenodo.org) by uploading them from GitLab. Once a DOI has been created, your analysis code becomes a citable object which you can add to your list of research outputs. Find out how to [create a doi for your repository](../gitlab/4-2-you-doi).
+#### Citable research output ![doi]({% link img/icon-doi.png %})
+Versions of analysis code can be assigned a digital object identified (DOI) using [Zenodo](https://zenodo.org) by uploading them from GitLab. Once a DOI has been created, your analysis code becomes a citable object which you can add to your list of research outputs. Find out how to [create a doi for your repository]({% link docs/gitlab/4-2-you-doi.md %}).
 
-#### Reproducible methods detail ![reproduce](../../img/icon-reproduce.png)
+#### Reproducible methods detail ![reproduce]({% link img/icon-reproduce.png %})
 Alongside your analysis code, WIN members will be supported in implementing a "[wrapper](https://techterms.com/definition/wrapper)" script which can:
-1. access data stored on the WIN [Open Data](../data) servers;
+1. access data stored on the WIN [Open Data]({% link docs/data.md %}) servers;
 2. access your GitLab code repository;
 3. pull a stable version of the FSL analysis package in a [Singularity container](https://en.wikipedia.org/wiki/Singularity_(software));
 4. Run the accessed data using the supplied code and the given version of FSL via the container on a high performance cluster.
@@ -76,13 +74,13 @@ External users will be able to access the shared code and singularity containers
 Coming soon
 {: .label .label-yellow }
 
-Detailed guidance on how to use the Open Analysis wrapper will be produced during one of our [documentation hacks](../community/events/doc-hack-1)
+Detailed guidance on how to use the Open Analysis wrapper will be produced during one of our [documentation hacks]({% link docs/community/events/doc-hack-1.md %})
 
 #### Repository template
-You are free to include whatever material you wish in your repository. We have created this [guide on what to include](../gitlab/repo-include) to list some of the pages and sections which may be beneficial for readers. See also our guide on [how to license](../gitlab/repo-license) your material.
+You are free to include whatever material you wish in your repository. We have created this [guide on what to include]({% link docs/gitlab/repo-include.md %}) to list some of the pages and sections which may be beneficial for readers. See also our guide on [how to license]({% link docs/repo-license.md %}) your material.
 
 #### Creating a doi
-We recommend using zenodo to create a doi for your material. See see the [creating a doi](../gitlab/repo-doi) page for instructions.
+We recommend using zenodo to create a doi for your material. See see the [creating a doi]({% link docs/gitlab/repo-doi.md %}) page for instructions.
 
 ## Working group members (alphabetically)
 We are grateful to the following WIN members for their contributions to developing the Open Analysis tools

docs/community.md

@@ -11,7 +11,7 @@ nav_order: 10
 Find out about the Open WIN Community, what we're doing, and how you can be a part of this effort.
 {: .fs-6 .fw-300 }
 
-![people](../../img/img-people.png)
+![people]({% link img/img-people.png %})
 
 ---
 

docs/community/CODE_OF_CONDUCT.md

@@ -38,4 +38,4 @@ We will begin events with a reminder of the Harassment Policy and expected behav
 ## Being a responsible bystander
 In this community we value efforts to promote a positive work environment, free from intimidation and all forms of violence. We are therefore pleased to support the University in enacting the Harassment Policy by acting as responsible bystanders, and doing what we can to promote a safe and conducive work environment. We encourage all community members to be responsible bystanders.
 
-![responsible-bystander-pdf](../../../img/img-responsiblebystanderposterpdf.png)
+![responsible-bystander-pdf]({% link img/img-responsiblebystanderposterpdf.png %})

docs/community/ambassadors.md

@@ -14,6 +14,6 @@ nav_order: 5
 
 The Open WIN Ambassadors are a team of individuals who are significant contributors to the Open WIN Community. 
 
-![Ambassadors as superheros](../../../img/undraw_Powerful_re_frhr.svg)
+![Ambassadors as superheros]({% link img/undraw_Powerful_re_frhr.svg %})
 
 **See the sections below or navigate on the sidebar to find out more about the Open WIN Ambassadors.**

docs/community/community-goals.md

@@ -26,7 +26,7 @@ As these stages near completion, we are entering the second phase of work to bui
 The WIN Open Neuroimaging Community will address the above problems by working together to:
 1. Develop tools, policies and governance recommendations to promote open research practices;
 2. Identify our own barriers to working open and devising strategies to remove these barriers for ourselves and others;
-3. Create documentation and training materials to help others use the [Open WIN Tools](../../tools);
+3. Create documentation and training materials to help others use the [Open WIN Tools]({% link docs/tools.md %});
 4. Build a community of researchers with the expertise and confidence to promote open research practices and the Open WIN Tools in our own labs and to wider audiences.
 
 
@@ -36,4 +36,4 @@ We intend to implement these solutions through regular co-working "hacks". These
 ## Ambassador program
 Alongside the hacks, we will develop the WIN Open Ambassadors programme for launch in 2021, where motivated individuals will be supported in sharing knowledge and sign posting their peers around open research practices and how they are implemented at WIN. The Ambassadors will be significant contributors to the community, and recognised for the value of their contribution. They will be invited to shape the governance of the community, and be consulted on policies, incentives, guiding principles and reward systems which will be devised to promote uptake of open research practices at WIN.
 
-Take a look at our drafted outline for the [Ambassadors program](../../ambassadors). We would love to hear your thoughts on how it should be put together!
+Take a look at our drafted outline for the [Ambassadors program]({% link docs/community/ambassadors.md %}). We would love to hear your thoughts on how it should be put together!

docs/community/community-who.md

@@ -21,13 +21,13 @@ Find out who we are and where we sit in the wider WIN context.
 * [Community Coordinator](#community-coordinator---cassandra-gould-van-praag-sheher)
 * [Open WIN Steering Group](#open-win-steering-group)
 
-![community-schematic](../../../img/img-community-schematic-h400-gold.png)
+![community-schematic]({% link img/img-community-schematic-h400-gold.png %})
 
 We are a community built from around 250 members of the University of Oxford [Wellcome Centre for Integrative Neuroimaging (WIN)](https://www.win.ox.ac.uk). We welcome students, researchers, [core staff](https://www.win.ox.ac.uk/about/core-staff), faculty, and anyone in between!
 
 We were formed to facilitate the dissemination of knowledge and experience from the developers of the Open WIN Tools into the hands of the WIN Members who will make use of them. We are interested in the development of open research practices in our discipline, and informing the policy and incentives around the implementation of open research at WIN.
 
-Anyone can join and contribute to this community, with any level of commitment. You are free to dip in-and-out when you have capacity to engage, and you will always be welcomed into the discussion. We welcome peripheral contributions such as minor edits to documentation, all the way through to leadership of the community. Find out more about this in our [Mountain of Engagement](../mountain-of-engagement) community model.
+Anyone can join and contribute to this community, with any level of commitment. You are free to dip in-and-out when you have capacity to engage, and you will always be welcomed into the discussion. We welcome peripheral contributions such as minor edits to documentation, all the way through to leadership of the community. Find out more about this in our [Mountain of Engagement]({% link docs/community/mountain-of-engagement.md %}) community model.
 
 ## Community members
 
@@ -52,8 +52,8 @@ GitHub: [@cassgvp](https://github.com/cassgvp)
 This community feeds directly into the [WIN Open Neuroimaging Project](https://www.win.ox.ac.uk/open-neuroimaging/open-neuroimaging-project) and its working groups:
 
 * Open Science (lead: [Tom Nichols](https://www.bdi.ox.ac.uk/Team/t-e-nichols))
-* [Open MR Protocols](../../tools/protocols) (lead: [Stuart Clare](https://www.win.ox.ac.uk/people/stuart-clare))
-* [Open Tasks](../../tools/tasks) (lead: [Laurence Hunt](https://www.win.ox.ac.uk/people/laurnece-hunt))
-* [Open Analysis](../../tools/analysis) (lead: [Mark Jenkinson](https://www.win.ox.ac.uk/people/mark-jenkinson))
-* [Open Data](../../tools/data) (lead: [Clare Mackay](https://www.win.ox.ac.uk/people/clare-mackay))
-* [Open WIN Ambassadors programme](../ambassadors) (lead: [Bernd Taschler](https://www.ndcn.ox.ac.uk/team/bernd-taschler))
+* [Open MR Protocols]({% link docs/protocols.md %}) (lead: [Stuart Clare](https://www.win.ox.ac.uk/people/stuart-clare))
+* [Open Tasks]({% link docs/tasks.md %}) (lead: [Laurence Hunt](https://www.win.ox.ac.uk/people/laurnece-hunt))
+* [Open Analysis]({% link docs/analysis.md %}) (lead: [Mark Jenkinson](https://www.win.ox.ac.uk/people/mark-jenkinson))
+* [Open Data]({% link docs/data.md %}) (lead: [Clare Mackay](https://www.win.ox.ac.uk/people/clare-mackay))
+* [Open WIN Ambassadors programme]({% link docs/community/ambassadors.md %}) (lead: [Bernd Taschler](https://www.ndcn.ox.ac.uk/team/bernd-taschler))

docs/community/events/doc-hack-1.md

@@ -21,15 +21,15 @@ Find out what happened on our first hack day!
 
 The aims for the hack day were to:
 1. Introduce interested individuals to the community, and communicate how you may benefit from participation, what kind of activities you may be able to take part in, how you will be recognised for your contribution, and what behaviours or commitment may be expected of you.
-2. Provide training on how to use the Open WIN infrastructure for sharing [MR Protocols](../../../protocols), [experimental task](../../../tasks), [data](../../../data) and [analysis code](../../../analysis)
-3. Provide training on [GitLab](../../../gitlab) and how it will be used to update this repository.
+2. Provide training on how to use the Open WIN infrastructure for sharing [MR Protocols]({% link docs/protocols.md %}), [experimental task]({% link docs/tasks.md %}), [data]({% link docs/data.md %}}) and [analysis code]({% link docs/analysis.md %})
+3. Provide training on [GitLab]({% link docs/gitlab.md %}) and how it will be used to update this repository.
 4. Begin crafting and contributing documentation to share our training with others.
 
 ## How did it go?!
 
 The day was structured around “lightning pitches” from the infrastructure developers to advertise where they would benefit from community engagement, followed by training in how to use GitHub to make contributions (submitting a pull request to [an external repository](https://cassgvp.github.io/git-for-collaborative-documentation)), and then three hours of dedicated time to work with the tools developers to make contributions and build ideas for future interactions. Summary attendance and engagement figures from the hack day are provided in below.
 
-![hack day 1 attendance](../../../../img/img-hackday-1-pies.png){:height="100%" width="100%"}
+![hack day 1 attendance]({% link img/img-hackday-1-pies.png %}){:height="100%" width="100%"}
 
 ## What did we achieve?
 

docs/community/events/doc-hack-template.md

@@ -26,7 +26,7 @@ The event will be hosted via [Wonder](https://www.wonder.me) at [tinyurl.com/Ope
 
 The aim for the hack day is to:
 1. Introduce interested individuals to the community, and communicate how you may benefit from participation, what kind of activities you may be able to take part in, how you will be recognised for your contribution, and what behaviours or commitment may be expected of you.
-2. Provide training on how to use the [Open WIN Tools](../tools.md).
+2. Provide training on how to use the [Open WIN Tools]({% link docs/tools.md %}).
 3. Provide training on GitHub/GitLab and how it will be used to update this repository.
 4. Begin crafting and contributing documentation to share our training with others.
 

docs/community/events/external.md

@@ -19,7 +19,7 @@ Below is a live copy of the [Open Research Calendar](https://openresearchcalenda
 
 Visit [@OpenResearchCal](https://twitter.com/OpenResearchCal) on twitter to find out how to add your events.
 
-![open-research-calendar](../../../../img/img-orc.png)
+![open-research-calendar]({% link img/img-orc.png %})
 
 
 <div class="span3">

docs/community/mountain-of-engagement.md

@@ -17,8 +17,8 @@ How we will work with community members to build growth and sustainability
 
 We want this community to grow in reach and ambition. We also want individual members to have to opportunity to direct their own growth and feel ownership of their community. This sense of ownership will build in sustainability, where each individual takes on partial and momentary responsibility for some aspect.
 
-![mountain-of-engagement](../../../img/img-m-o-e.png)
+![mountain-of-engagement]({% link img/img-m-o-e.png %})
 
 To achieve individual and community growth, we are following the "Mountain of Engagement" model. This is a tool for conceptualising how people will interact with your community, and building an understanding of how different people might grow from their first interaction to taking on some form of responsibility. Not all community members will progress to leadership, but it is useful to think about what actions or events may lead people to progress.  
 
-We have used the Mountain of Engagement model to consider how our imaginary [personas](../personas-and-pathways) might interact with the Open WIN community. This exercise has provided useful insight into how we can support progression for a variety of people.
+We have used the Mountain of Engagement model to consider how our imaginary [personas]({% link docs/community/personas-and-pathways.md %}) might interact with the Open WIN community. This exercise has provided useful insight into how we can support progression for a variety of people.

docs/community/personas-and-pathways.md

@@ -16,7 +16,7 @@ Who will our Community Members be, how will they find us and how will we support
 
 This exercise helped us to think about who might be interested in joining our community, how we can connect with them, and the journey they might go on. It is designed to help us reach different audiences and be welcoming to diverse contributors.
 
-**Follow the sections linked in the side bar to walk through the exercise and understand how we arrived at our [persona descriptions and described their pathways](../personas-and-pathways-descriptions) to engagement with this community.**
+**Follow the sections linked in the side bar to walk through the exercise and understand how we arrived at our [persona descriptions and described their pathways]({% link docs/community/personas-and-pathways-descriptions.md %}) to engagement with this community.**
 
 Our intention is to update this document as we gain a clearer idea of who we are engaging with or missing from the community. Please contact us if any of the ideas presented here do not resonate with you, or if they hit the right note! 🎶