-
Notifications
You must be signed in to change notification settings - Fork 203
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 Review] Review website (vitess.io) content. #1222
Labels
documentation
Early in Cycle
These items are prioritised for the current release cycle
enhancement
New feature or request
Comments
This was referenced Nov 16, 2022
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@rsajwani, is this issue something we want to finish before the release of v16? |
This was referenced Nov 16, 2022
Closed
Closed
Closed
This was referenced Nov 16, 2022
Closed
rsajwani
changed the title
[Website] Review website (vitess.io) content.
[Docs Review] Review website (vitess.io) content.
Nov 16, 2022
frouioui
added
the
Early in Cycle
These items are prioritised for the current release cycle
label
Nov 17, 2022
We should plan to do it end of December. |
This was referenced Dec 9, 2022
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
This was referenced Dec 20, 2022
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Early in Cycle
These items are prioritised for the current release cycle
enhancement
New feature or request
This is the general, and tracking, issue for webiste (vitess.io) content review. The activity involves
Please note that we are not going to focus of restructuring the website content as part of this project. It is something we will do as a separate project later on.
Table of Contents
This content review is only for v15.0 and v16.0.
This issue is considered done when each of these is complete
Instructions for changes
Website github url is https://github.com/vitessio/website. Instructions to run website locally is listed under the description there.
The text was updated successfully, but these errors were encountered: