~ivilata/gwit-spec

65a892384d8ad166c90d4d5b1bdd3f3d67e58706 — Ivan Vilata-i-Balaguer 27 days ago bfd8dc0
Use less confusing example for gwit site branch name.

Which is now clearly the end of the `0xfed...ef76543210` example ID used
elsewhere, instead of the end of the other ID `0x012...effedcba98`, which
happened to end like the beginning of the first one, hence the possible
confusion.  The end of the first example ID does not clash with the beginning
nor the end of the second one.
1 files changed, 1 insertions(+), 1 deletions(-)

M README.md
M README.md => README.md +1 -1
@@ 76,7 76,7 @@ gwit defines a URI format (described further below) that allows to refer (link) 

## Site requirements

The site branch associated with a gwit site MUST be named `gwit-0x........`, where the dots represent the lower case short ID of the PGP site key, i.e. the last 8 hexadecimal digits of the site identifier in lower case. Example: `gwit-0xfedcba98`.
The site branch associated with a gwit site MUST be named `gwit-0x........`, where the dots represent the lower case short ID of the PGP site key, i.e. the last 8 hexadecimal digits of the site identifier in lower case. Example: `gwit-0x76543210`.

This means that the same Git repository may hold different but related gwit sites, each one with its own branch and key. For instance, while the `master` or `main` branch may contain common sources for a static site generator, generated Gemini and Web files may go to separate gwit site branches.