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

[docs] https://docs.lilypad.tech/ redirects to https://docs.lilypad.tech/lilypad #37

Open
AquiGorka opened this issue May 6, 2024 · 7 comments
Assignees

Comments

@AquiGorka
Copy link

This is not the best for SEO. Definitely a minor concern but ideally we keep the current version docs at /

@developersteve
Copy link
Contributor

Ahh after checking the DNS it looks like this is because the docs are structured within a lilypad folder within the repo and being carried over from gitbooks.

@developersteve
Copy link
Contributor

@developersteve
Copy link
Contributor

Adding in @PBillingsby here too for the gitbook side of things

@developersteve
Copy link
Contributor

@PBillingsby I think this might be able to fix it if we changed the .gitbook.yml root folder location to ./lilypad as per https://docs.gitbook.com/integrations/git-sync/content-configuration#root

@AquiGorka
Copy link
Author

Thank you for looking into this. Definitely low priority.

@PBillingsby PBillingsby self-assigned this Aug 28, 2024
@PBillingsby
Copy link
Collaborator

@developersteve Can we set up a redirect once the appended /lilypad is removed? So redirect from /lilypad to /.

We have a lot of references to https://docs.lilypad.tech/lilypad and I believe once we change the root path all of those links will be broken.

@developersteve
Copy link
Contributor

@developersteve Can we set up a redirect once the appended /lilypad is removed? So redirect from /lilypad to /.

We have a lot of references to https://docs.lilypad.tech/lilypad and I believe once we change the root path all of those links will be broken.

Yup that was the plan, the .gitbook.yml was added per the spec doc but it didn't change so is still in the same state. From memory this was going to need a complete refactor to work :(

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