Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better use of the config #348

Open
egekorkan opened this issue Sep 27, 2022 · 3 comments
Open

Better use of the config #348

egekorkan opened this issue Sep 27, 2022 · 3 comments
Assignees

Comments

@egekorkan
Copy link
Contributor

Coming from #336 (comment)

Another note: Adding "WoT" prefix to each subpage would not be a good idea if this prefix changes once... we deal with it in _config.yml

@egekorkan
Copy link
Contributor Author

This might fix the netlify problem or we need to adjust this in netlify to take /WoT into account

@egekorkan
Copy link
Contributor Author

Call of 31.01:
We have this current config due to website being available at W3.org and at github.io. Now we have Netlify as well. In the case of Netlify, a postprocessing script can actually replace all w3.org URLs with the preview URLs.

@egekorkan
Copy link
Contributor Author

Call of 21:03: Actually, even if the website is opened locally via jekyll, the links in the navbar change the 127.0.0.1 to localhost so there is a different behavior with respect to links in the config via jekyll vs links we add via href inside the code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants