Update links from individuals to IETF drafts (#44)

* Update links from IDs to drafts
* Add the emulator and did:web generator links

Signed-off-by: steve lasker <[email protected]>

Author: SteveLasker

README.md

@@ -4,7 +4,7 @@ title: What Is SCITT
 permalink: /index
 nav_order: 0
 ---
-
+ 
 # What Is SCITT
 
 The **S**upply **C**hain **I**ntegrity, **T**ransparency and **T**rust (SCITT) initiative is a set of proposed [IETF internet standards]({{ site.ietf-scitt }}){:target="_blank"} for managing the compliance of goods and services across end-to-end supply chains.
@@ -41,4 +41,4 @@ A SCITT instance will persist verifiable claims to its ledger. Any optional evid
 
 While a SCITT instance should provide a default storage, there's no limit on what storage services are used. For package managers that support breadths of content types, the evidence may be stored alongside the artifact by which the claim is being made. For package managers that limit the content types to the specific package type, a SCITT instance should provide default storage persistence.
 
-For more info, see: [Supply Chains]({% link supply-chain.md %})
+For more info, see: [Supply Chains]({% link supply-chain.md %})

_config.yml

@@ -17,6 +17,7 @@ title: SCITT - Supply Chain Integrity and Trust
 # email: your-email@example.com
 description: >- # this means to ignore newlines until "baseurl:"
   The Supply Chain Integrity, Transparency and Trust (SCITT) initiative is a set of proposed industry standards for managing the compliance of goods and services across end-to-end supply chains.
+# baseurl: "/scitt-web" # use this line for local rendering and forked rendering. Revert to below before committing to the upstream project
 baseurl: "/" # the subpath of your site, e.g. /blog
 # url: "" # the base hostname & protocol for your site, e.g. http://example.com
 # twitter_username: SCITT
@@ -54,13 +55,19 @@ nav_external_links:
     url: https://datatracker.ietf.org/wg/scitt/
     hide_icon: false
   - title: "SCITT Architecture"
-    url: https://datatracker.ietf.org/doc/draft-birkholz-scitt-architecture/
+    url: https://datatracker.ietf.org/doc/draft-ietf-scitt-architecture/
     hide_icon: false
   - title: "SCITT Receipts"
     url: https://datatracker.ietf.org/doc/draft-birkholz-scitt-receipts/
     hide_icon: false
   - title: "SCITT Software Use Case"
-    url: https://datatracker.ietf.org/doc/draft-birkholz-scitt-software-use-cases/
+    url: https://datatracker.ietf.org/doc/draft-ietf-scitt-software-use-cases/
+    hide_icon: false
+  - title: "SCITT Emulator"
+    url: https://github.com/scitt-community/scitt-api-emulator
+    hide_icon: false
+  - title: "did:web generator"
+    url: https://github.com/scitt-community/did-web-demo
     hide_icon: false
 
 ##############################

site-development.md

@@ -2,7 +2,7 @@
 
 These pages are currently built with [jekyll](https://jekyllrb.com/).
 
-Following the great [video from Bill Raymond](https://www.youtube.com/watch?v=owHfKAbJ6_M), you can build, test, iterate locally, without having to install or manage the jekyll dependencies.
+Following the great [video from Bill Raymond](https://youtu.be/zijOXpZzdvs?t=372), you can build, test, iterate locally, without having to install or manage the jekyll dependencies.
 
 For detailed steps: [BillRaymond/my-jekyll-docker-website](https://github.com/BillRaymond/my-jekyll-docker-website)
 
@@ -15,15 +15,15 @@ For detailed steps: [BillRaymond/my-jekyll-docker-website](https://github.com/Bi
 
 ## Incremental Building
 
-Once you've built the container, and initiated the local jekyll builid process, the following steps are what you need to start a session.
+Once you've built the container, and initiated the local jekyll build process, the following steps are what you need to start a session.
 
 1. In Visual Studio Code, open the terminal window and type:
     ``` bash
     bundle exec jekyll serve --livereload
     ```
 
 ## Closing the container
-It is a good practice to close the container when you are done coding as it will free up memomry and resources on your base operating system. You can do that directly inside Visual Studio Code. 
+It is a good practice to close the container when you are done coding as it will free up memory and resources on your base operating system. You can do that directly inside Visual Studio Code. 
 1. To close and exit the container, in Visual Studio Code, close it by typing `COMMAND+SHIFT+P`, then type `Close remote connection`, and press `return`
 
 ## Opening the container