In the current CI workflow that deploys the site, the behaviour of relative paths is different from that seen locally. When I specify a relative path to a file in the current directory, the convention is to put in ./file and then clicking on the link in the site should navigate to the local directory's file. Similarly, we would point to a file in the parent directory by specifying ../file.
When I test the relative paths as shown above locally (by deploying the site on my machine), the links work great
The same URLs do no work on the deployed site
Haven't been able to figure out why the relative paths behave differently locally vs. after being deployed.
In the current CI workflow that deploys the site, the behaviour of relative paths is different from that seen locally. When I specify a relative path to a file in the current directory, the convention is to put in
./fileand then clicking on the link in the site should navigate to the local directory's file. Similarly, we would point to a file in the parent directory by specifying../file.Haven't been able to figure out why the relative paths behave differently locally vs. after being deployed.