docs: fix broken links to guidance

documentation/extensions/dei/guidance.md

@@ -12,10 +12,10 @@ This isn’t a reporting process, it’s an opportunity to collect and share dat
 
 This guidance is for those who want to publish information using the DEI Data Standard in the context of their grant information. The guidance in this section focuses on the fields and codes defined in the DEI Extension.
 
-If you are new to publishing 360Giving data but are doing so with a view to also including DEI Data Standard data, we suggest you begin at the [Guidance for Publishers](../../guidance/index.md). This will help you understand the key principles involved in publishing 360Giving data. Once you are familiar with the steps and process, you will be able use this guidance to understand how to integrate the DEI Data Standard data into your 360Giving data publication.
+If you are new to publishing 360Giving data but are doing so with a view to also including DEI Data Standard data, we suggest you begin at the [Guidance for Publishers](https://www.360giving.org/publish/guidance/). This will help you understand the key principles involved in publishing 360Giving data. Once you are familiar with the steps and process, you will be able use this guidance to understand how to integrate the DEI Data Standard data into your 360Giving data publication.
 
 If you are already a 360Giving publisher, or are otherwise already familiar with how to publish 360Giving data, this guidance will help you integrate the DEI Data Standard data alongside your existing 360Giving grants data.
-If you publish or plan to publish data about grants made to individuals, it is not possible to publish DEI data alongside your 360Giving grants data as, combined with other data published, this risks making grant recipients personally identifiable. However, it is possible to collect this data and share it in aggregate, for example on your own website. For more on this, see the [data protection section](../../individuals/publisher-guidance.md#demographic-data) of our grants to individuals guide.
+If you publish or plan to publish data about grants made to individuals, it is not possible to publish DEI data alongside your 360Giving grants data as, combined with other data published, this risks making grant recipients personally identifiable. However, it is possible to collect this data and share it in aggregate, for example on your own website. For more on this, see the [Remove personal data about grants for individuals section](https://www.360giving.org/publish/guidance/prepare/remove-sensitive-info/#Remove-personal-data-about-grants-for-individuals) of our guide to removing personal and sensitive information.
 
 
 <div class="box box--teal">

documentation/technical/codelists.md

@@ -122,7 +122,7 @@ A codelist with values to specify that a grant is intended for redistribution, b
 
 The codes from this codelist can be published in the field **For Regrant Type**. The **For Regrant Type field** can only be included once with a single code per grant.
 
-For further explanation of how to use the Regrant Type codelist, including examples, read the [360Giving guide to regranting](../guidance/regranting).
+For further explanation of how to use the Regrant Type codelist, including examples, read the [360Giving guide to regranting](https://www.360giving.org/publish/guidance/prepare/decide-what-to-publish/regranting-data/).
 
 ```eval_rst
 .. csv-table::
@@ -141,7 +141,7 @@ A codelist with values to specify a grant's geographical scope, broken down into
 
 The codes from this codelist can be published in the field **Location Scope**. The **Location Scope field** can only be included once with a single code per grant.
 
-For further explanation of the location scope codelist, including examples, read the [360Giving guide to location data](../guidance/location-guide.md).
+For further explanation of the location scope codelist, including examples, read the [360Giving guide to location data](https://www.360giving.org/publish/guidance/prepare/decide-what-to-publish/location-data-guide/).
 
 ```eval_rst
 .. csv-table::

documentation/technical/identifiers.md

@@ -49,7 +49,7 @@ For organisation identifiers, we strongly encourage you to use an officially rec
 
 ## Get your prefix
 
-To register a prefix for your organisation see the [publisher guidance.](../../guidance/prepare-data)
+To register a prefix for your organisation see the [publisher guidance.](https://www.360giving.org/publish/guidance/plan/register/)
 
 All registered prefixes should start with 360G.
 ```eval_rst

documentation/technical/index.md

@@ -20,7 +20,7 @@ In this guidance you will find:
 - Guidance about metadata
 - Guidance about codelists
 
-If you are just getting started with sharing 360Giving data, start by reading the [Guidance for publishers section.](../guidance/index.md)
+If you are just getting started with sharing 360Giving data, start by reading the [Guidance for publishers section.](https://www.360giving.org/publish/guidance/)
 
 ```eval_rst
 .. toctree::

documentation/technical/metadata.md

@@ -128,7 +128,7 @@ If it is not possible to know this information before the data is published - or
 
 This is the canonical URI of the license that applies to the data in the file or package. This should be a Public Domain Dedication or <a href="https://opendefinition.org/licenses/" target="_blank">Open Definition Conformant license.</a>
 
-For further details see our guidance about [open licensing.](../../guidance/publish-data-openly)
+For further details see our guidance about [open licensing.](https://www.360giving.org/publish/guidance/publish/)
 
 ```eval_rst
 .. _example-meta-sheet:

documentation/technical/reference.md

@@ -4,7 +4,7 @@ This page provides reference information on publishing to the 360Giving Data Sta
 
 It assumes some technical knowledge.
 
-If you are just getting started with the 360Giving Data Standard, visit the [guidance for publishers section.](../guidance/index.md)
+If you are just getting started with the 360Giving Data Standard, visit the [guidance for publishers.](https://www.360giving.org/publish/guidance/)
 
 
 ## Data formats