-
Notifications
You must be signed in to change notification settings - Fork 276
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
Doc/ Adding a Sitemap #313
Conversation
Signed-off-by: Sara <lira.lemur@gmail.com>
Signed-off-by: Sara <lira.lemur@gmail.com> Co-Authored-By: Andrei Lebedev <lebdron@gmail.com>
Signed-off-by: Sara <lira.lemur@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sitemap would be updated after #310 , maybe merge it first?
Signed-off-by: Sara <lira.lemur@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might need to look into custom build steps in readthedocs, so that this file is always up-to-date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that we should have a separate storage for generated documentation files.
Please reopen this pull request when there will be an agreement on the solution. Did not save the branch because this should be generated. Created task https://jira.hyperledger.org/browse/IR-755 |
Description of the Change
Sitemap is being submitted, so google's crawlers could reindex pages.
Benefits
Better SEO
Possible Drawbacks
Will need to be updated when we update the docs. Maybe it would be better to have some sort of an automatic generator in the long run.