Tips/Tricks/How-Tos

Do NOT Modify spec.json this way...

The spec.json file has a key reference that should ALWAYS remain set to the main repository.

Be sure that the "source" parameter is left as pointing at the main repository. As a CONSEQUENCE this will mean that your forked repository will not likely render properly to your personal github.io space.

i.e. leave the account value as trustoverip not yours.

You can preview your changes (see below) with SpecUp.

"source": {
  "host": "github",
  "account": "trustoverip",
  "repo": "tswg-trust-registry-protocol"
},

Adding images

Put the images into the ./spec folder where your main content (or in a sub-folder like ./spec/images )

Reference these using regular image markdown:

![alternate text/title](./images/highlevel.png)

NOTE: if you don't use this approach your local preview may show images that DO NOT show when fully deployed in the main repository.

Previewing/Rendering Locally

Run the following in your terminal (you will need to npm install before this will work):

One-time Render: npm run render
Constant Render: npm run edit

Linking GitHub Issues

When you configure the specs.json file, be sure to link the proper GitHub repository as the Issued list (top right corner) will come from that repo:

e.g for TRP

"source": {
  "host": "github",
  "account": "trustoverip",
  "repo": "tswg-trust-registry-protocol"
},

Calling Out a Single GitHub Issue

::: issue 
https://github.com/trustoverip/tswg-trust-registry-protocol/issues/5 
- Should align with Service Profiles/[Service Discovery] efforts
:::

will render out as (h/t: Eric Scouten )

OTHER???

SpecUp Resources