Use relative link paths for the GNO website #459
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR simply modifies the
HOME.md
file in the gno website module to utilize relative link paths, instead of hardcoded link paths.As pointed out in #458, spinning up a local version of the website will link to the testnet, and not the local running instance, on the homepage.
Additionally, a build step was added to the
all
directive in theMakefile
, so existing READMEs are valid - thegnofaucet
binary is not being built in thebuild
folder, but the README on the faucet assumes it is.Changes include
Checklist (for contributors)
Testing
Manual tests
Deployed the website using the
./build/website
command and checked that links are relative instead of absolute.