Closed jcf closed 3 years ago
@Airblader @stapelberg can this documentation be added under the Developer section in i3 docs?
Sorry, I missed this when you originally reported it.
To address the issue for humans you could set the
href="/"
in question to "http://i3wm.org/" rather than just "/"
I think we should add an index page to build.i3wm.org, and also a robots.txt that removes it from search engines.
@Airblader @stapelberg can this documentation be added under the Developer section in i3 docs?
What do you mean by “this documentation”? i3-msg? No, we don’t need to mention every single tool’s manpage explicitly from our main docs page. We could add 1 single link to https://manpages.debian.org/buster/i3-wm/index.html perhaps.
We now have a robots.txt. Adding an index file is a bit inconvenient due to how the build.i3wm.org repository is set up (generated by a script), so I’ll skip that for now.
The documentation for
i3-msg
appears to have a broken link sending people to https://build.i3wm.org/, which then returns a GitHub pages 404 response.I think the problem is that you want the docs to show up at i3wm.org, but Google have found the same content on build.i3wm.org.
Here's an example Google search result in case that helps:
To address the issue for humans you could set the
href="/"
in question to "http://i3wm.org/" rather than just "/", but that's a bit of a hack (and might hurt your SEO).…cue selling my friend's SEO consultancy… :wink:
HTH!