Repository navigation
Site: bring the landing page, docs index, compare page and README up to v1.8.0 - #308
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The public site described the product as of early November. This brings the landing page, the docs index, the compare page and the README up to what v1.8.0 ships, and removes claims that stopped being true. It has to merge before the v1.8.0 tag, because bloodraven.dev is built from the release tag.
Why
The site deploys when a release is published. Features that shipped since (paced rollouts, the v1beta1 API, storage growth, the workload dashboard, standby clusters, the kubectl plugin) were in the reference docs but not on the pages a new visitor reads.
Changes
Landing page
MysqlStandbyCluster.migrate-storage, and the operator's check at start.Docs
DisasterRecoverysite is not a planned-failover target; the text said manual promotion "would use the forthcoming planned-failover API".Compare page (figures recounted from the code, as its header asks)
README: the same six standout features and the scenario count.
Screenshots
None attached: the only image host available here is a public bucket, and the pages are public within the hour anyway. I rendered the landing page locally at 1280 px and inspected the new cards, the stats row and the control-plane points; the grids fill evenly (six cards in the three-column section, six in the two-column section).
Test Plan
npm testinsite/: 38 passed.nuxt dev:/,/compare,/docs,/docs/get-started/known-limitationsand/docs/architecture/multi-cluster-drreturn 200 with the new text.llms-full.txtcheck. CI's Docs / Build job runs both.Not done