Refactor CRMTP site

To align with AATP site and establish a UNTP extensions convention.

website/docs/business-case/BusinessCaseTemplates.md

@@ -0,0 +1,20 @@
+---
+sidebar_position: 5
+title: Business Case Templates
+---
+
+import Disclaimer from '../\_disclaimer.mdx';
+
+<Disclaimer />
+
+
+## Cost Benefit Modeling Template
+
+The spreadsheet template below provides a very simple tool to assist with the first-pass estimate of CRMTP implementation costs and benefits for individual businesses. It allows the user to choose how to weight each benefit category to suit their own circumstances. It also allows users to model break-even point with different assumptions about uptake rate across trading partners.
+
+**Spreadsheet model TBD**
+
+
+
+
+

website/docs/business-case/CaseStudies.md

@@ -0,0 +1,34 @@
+---
+sidebar_position: 10
+title: Case Studies
+---
+
+import Disclaimer from '../\_disclaimer.mdx';
+
+<Disclaimer />
+
+## Summary
+
+|Case Study|Date|Summary|
+|--|--|--|
+|[BC Government Mines Permit](#bc-government-mines-permit)|Aug-Dec 2023|Verified usability of the UNTP Digital Conformity Credential as the basis for a regulatory permit.|
+|[Mining Association of Canada - TSM credential](#mining-association-of-canada-tsm-credential) |Jan-Apr 2024  | Verified usability of the UNTP Digital Conformity Credential as the basis for a mine ststainability certificate.|
+
+
+
+### BC Government Mines Permit
+
+Some words about mines permit 
+
+* Participants were..
+* Technical deliverables were..
+* Outcomes were..
+
+
+### Mining Association of Canada TSM Credential
+
+Some words about TSM 
+
+* Participants were..
+* Technical deliverables were..
+* Outcomes were..

website/docs/business-case/index.md

@@ -0,0 +1,6 @@
+---
+sidebar_position: 10
+title: Business Case
+---
+
+

website/docs/guidance/Cobalt.md

@@ -0,0 +1,47 @@
+---
+sidebar_position: 10
+title: Cobalt
+---
+
+import Disclaimer from '../\_disclaimer.mdx';
+
+<Disclaimer />
+
+## Cobalt Value Chain
+
+The cobalt value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. 
+
+diagram goes here
+
+Any actor that has an identifier of a cobalt product, minsite, or refinery can find the issued credentials and verify them.  In general, downstream actors will be verifiers of upstream credentials. 
+
+## Implementation Guidance
+
+Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the CRMTP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. 
+
+|Role|Issuer of|Comments|
+|--|--|--|
+|Mine site|cobalt passport|comments |
+|Certifier |cobalt credential| |
+|Regulator|Mine Permit| |
+|etc| | |
+
+
+## Identity Anchors
+
+
+|Role|Identity Anchor Type|Comment|
+|--|--|--|
+| | | |
+
+
+
+
+TBD
+
+
+
+
+
+
+

website/docs/guidance/Copper.md

@@ -0,0 +1,54 @@
+---
+sidebar_position: 10
+title: Copper 
+---
+
+import Disclaimer from '../\_disclaimer.mdx';
+
+<Disclaimer />
+
+## Copper Value Chain
+
+The copper value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. 
+
+diagram goes here
+
+Any actor that has an identifier of a copper product, minsite, or refinery can find the issued credentials and verify them.  In general, downstream actors will be verifiers of upstream credentials. 
+
+## Implementation Guidance
+
+Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the AATP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. 
+
+|Role|Issuer of|Comments|
+|--|--|--|
+|Mine site|Copper passport|comments |
+|Certifier |CopperMark credential| |
+|Regulator|Mine Permit| |
+|etc| | |
+
+
+## Identity Anchors
+
+Identity anchors add increased trust to the CRMTP ecosystem because they link the DIDs (Self-issued IDs) of actors such as miners and refiners to authoritative registers such as Business registers. They are very simple credentials and are simple to issue. Their purpose and detailed implementation guidance are provided in the UNTP [Digital Identity Anchor (DIA)](https://uncefact.github.io/spec-untp/docs/specification/DigitalIdentityAnchor) specification.  The DIA is mapped to CRMTP identifiers in the [Identifiers](../specification/Identifiers) section of this website. The table below lists the specific identity anchors relevant for actors in the industry. Each actor SHOULD request the corresponding identity credential from their registrar and should make it discoverable by 
+
+* linking it to their DID `serviceEndpoint` as described in [DIA DID discovery](https://uncefact.github.io/spec-untp/docs/specification/DigitalIdentityAnchor#via-did-service-endpoint)
+* adding it to their registry entry as a link type as described in [DIA Resolver Discovery](https://uncefact.github.io/spec-untp/docs/specification/DigitalIdentityAnchor#via-identity-resolver)
+
+These tasks will normally be facilitated by the registrar such as the national business register.
+
+|Role|Identity Anchor Type|Comment|
+|--|--|--|
+| | | |
+
+
+## Buyers (Retailers & Brands)
+
+
+TBD
+
+
+
+
+
+
+

website/docs/guidance/Lithium.md

@@ -0,0 +1,47 @@
+---
+sidebar_position: 12
+title: Lithium
+---
+
+import Disclaimer from '../\_disclaimer.mdx';
+
+<Disclaimer />
+
+## Lithium Value Chain
+
+The lithium value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. 
+
+diagram goes here
+
+Any actor that has an identifier of a lithium  product, minsite, or refinery can find the issued credentials and verify them.  In general, downstream actors will be verifiers of upstream credentials. 
+
+## Implementation Guidance
+
+Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the CRMTP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. 
+
+|Role|Issuer of|Comments|
+|--|--|--|
+|Mine site|Lithium passport|comments |
+|Certifier |Lithium credential| |
+|Regulator|Mine Permit| |
+|etc| | |
+
+
+## Identity Anchors
+
+
+|Role|Identity Anchor Type|Comment|
+|--|--|--|
+| | | |
+
+
+
+
+TBD
+
+
+
+
+
+
+

website/docs/guidance/Nickel.md

@@ -0,0 +1,47 @@
+---
+sidebar_position: 10
+title: Nickel
+---
+
+import Disclaimer from '../\_disclaimer.mdx';
+
+<Disclaimer />
+
+## Nickel Value Chain
+
+The nickel value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. 
+
+diagram goes here
+
+Any actor that has an identifier of a nickel product, minsite, or refinery can find the issued credentials and verify them.  In general, downstream actors will be verifiers of upstream credentials. 
+
+## Implementation Guidance
+
+Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the CRMTP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. 
+
+|Role|Issuer of|Comments|
+|--|--|--|
+|Mine site|Nickel passport|comments |
+|Certifier |Nickel credential| |
+|Regulator|Mine Permit| |
+|etc| | |
+
+
+## Identity Anchors
+
+
+|Role|Identity Anchor Type|Comment|
+|--|--|--|
+| | | |
+
+
+
+
+TBD
+
+
+
+
+
+
+

website/docs/guidance/index.md

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 20
-title: Guidance for Implementers
+sidebar_position: 15
+title: Guidance
 ---
 
 import Disclaimer from '../\_disclaimer.mdx';

website/docs/guidance/testing.md

@@ -9,5 +9,10 @@ import Disclaimer from '../\_disclaimer.mdx';
 
 An explanation of testing services can be found in the “Testing Services” section of the [UNTP site](https://uncefact.github.io/spec-untp/docs/tools-and-support/TestService). The tools and guidance for their use can be accessed [here](https://github.com/uncefact/tests-untp).
 
-Results from early implementations will enable the CRM project team to create CRM-specific testing services, as needed.
+Test implementations assist individual implementers and communities of implementers to test your conformance with UNTP-CRM, prior to broad adoption. 
+These tools allow early implementers to manually create trial digital credentials, and publish them so they can be accessed by other pilot implementers, such as trading partners, customs authorities, and investors. You can find other planned implementers here, with whom you can test your test implementation. 
+
+* A description of tools for undertaking a test implementation can be found at the [UNTP site](https://uncefact.github.io/tests-untp/).
+* The tools and guidance for their use can be accessed [here](https://uncefact.github.io/tests-untp/docs/mock-apps/).
+
 

website/docs/register/index.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 30
-title: Implementers
+title: Register
 ---
 
 This section of the site describes the various types of UNTP-CRM implementers, their roles and function. As you read, consider which role your organization would play as a UNTP-CRM implementer.