-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update sidebar navigation for version 3.9 of English and Japanese docs #597
base: main
Are you sure you want to change the base?
Conversation
This navigation is necessary since we will be hard-coding titles (`labels`) in the sidebar navigation in the near future. Without this, the sidebar navigation for Japanese docs would show in English.
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.
Thank you! Almost LGTM. I left a few comments. PTAL!
✅ Deploy Preview for staging-scalardl-docs-site ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
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.
Thank you for revising it! I left a very minor improvement, but basically LGTM.
sidebars.js
Outdated
{ | ||
type: 'doc', | ||
id: 'use-generic-contracts', | ||
label: '汎用コントラクトおよびファンクションの使用', |
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.
Probably, this is consistent with others, and a short one might be better.
label: '汎用コントラクトおよびファンクションの使用', | |
label: '汎用コントラクトを使用する', |
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.
Ah, thank you for mentioning this!
In a PR for the ScalarDB sidebar, @/feeblefakie mentioned noun form and verb form. In that PR, I changed them to noun form, so I've done the same in the sidebars in this PR as well in 7e4b2e0.
Make Japanese titles consistently use noun form, as mentioned in the PR for the ScalarDB sidebar navigation (https://github.com/scalar-labs/docs-scalardb/pull/762/files/1c1b5404f5b23485105ae6a17a42977ecdc5aac3#r1869009005).
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.
{ | ||
type: 'doc', | ||
id: 'use-generic-contracts', | ||
label: 'Use Generic Contracts and Functions', |
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.
@jnmt As mentioned in your comment for the Japanese phrasing, should we shorten the English wording as well?
label: 'Use Generic Contracts and Functions', | |
label: 'Use Generic Contracts', |
sidebars.js
Outdated
{ | ||
type: 'doc', | ||
id: 'use-generic-contracts', | ||
label: '汎用コントラクトおよびファンクションの使用', |
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.
Ah, thank you for mentioning this!
In a PR for the ScalarDB sidebar, @/feeblefakie mentioned noun form and verb form. In that PR, I changed them to noun form, so I've done the same in the sidebars in this PR as well in 7e4b2e0.
type: 'doc', | ||
id: 'scalar-kubernetes/CreateBastionServer', | ||
label: 'Create a Bastion Server', | ||
}, | ||
], | ||
}, | ||
{ | ||
type: 'category', | ||
label: 'Cluster Guides', |
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 don't think Cluster Guides
and Container Image Guides
are needed in the sidebar because they are part of deployment and covered by the Deployment guides.
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.
Although I'm OK with not showing these docs in the sidebar in the future, as long as the content is available in the other docs, I do have one concern.
Many other docs link to these docs listed in this sub-category. If we remove these docs from the sidebar, when a visitor clicks a link to go to these pages, then the sidebar navigation will not be displayed on those pages. I think not showing the sidebar navigation would be confusing for users because they would need to go back to the previous page or go to the home page to see the sidebar navigation again.
With that in mind, how about we address this in a different PR?
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.
Thank you for the updates! (And sorry for my late review...)
I left several comments and suggestions.
Please take a look when you have time! 🙇♂️
{ | ||
type: 'doc', | ||
id: 'getting-started-auditor', | ||
label: 'Run a Contract Through ScalarDL Ledger and ScalarDL Auditor', |
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.
label: 'Run a Contract Through ScalarDL Ledger and ScalarDL Auditor', | |
label: 'Run a Contract Through ScalarDL Auditor mode', |
I think we can make the label length short if we can use the term Auditor mode
.
However, I don't know whether we can use the term Auditor mode
as an official term.
If we should not use Auditor mode
, I think we can keep the current label name as is.
@feeblefakie @jnmt
What do you think?
{ | ||
type: 'doc', | ||
id: 'installation-with-docker', | ||
label: 'Install ScalarDL in Your Local Environment', |
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.
label: 'Install ScalarDL in Your Local Environment', | |
label: 'Install ScalarDL in Your Local Environment with Docker', |
Now, we are creating another document Deploy ScalarDL Ledger Locally
that uses Minikube to deploy ScalarDL locally in another PR.
https://github.com/scalar-labs/docs-internal-orchestration/pull/83
So, I think it would be better to mention with Docker
explicitly here to avoid unnecessary confusion.
What do you think?
(If with Docker
is too long, let me consider other ideas.)
{ | ||
type: 'doc', | ||
id: 'generic-contracts-reference', | ||
label: '汎用コントラクトおよびファンクション', |
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.
label: '汎用コントラクトおよびファンクション', | |
label: 'Generic Contracts Reference', |
It seems that we should use English here.
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 think we don't treat Generic contracts
as a proper noun. So, I think it's fine as is.
Maybe, it's better to be just 汎用コントラクト
.
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.
@feeblefakie
Ah, sorry. My comment was a bit ambiguous.
Here is the docsEnglish
section. Not the docsJapanese
section.
So, simply we should use English here. I think it was translated by accident.
According to your suggestion, it might be better to use Generic Contracts
(without Reference
) here though.
{ | ||
type: 'doc', | ||
id: 'scalardl-java-client-sdk/README', | ||
label: 'ScalarDL Java クライアント SDK', |
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.
label: 'ScalarDL Java クライアント SDK', | |
label: 'ScalarDL Java Client SDK', |
I think ScalarDL Java Client SDK
is a component name. So, I think we should not translate Client
here.
{ | ||
type: 'doc', | ||
id: 'authentication', | ||
label: '認証を使用', |
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.
label: '認証を使用', | |
label: '認証', |
I think 認証
is simple and better because the origin English word is Authentication
.
{ | ||
"type": "doc", | ||
"id": "scalar-kubernetes/BackupRDB", | ||
"label": "Kubernetes で RDB をバックアップ" |
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.
"label": "Kubernetes で RDB をバックアップ" | |
"label": "Kubernetes 環境で RDB をバックアップ" |
Same as sidebars.js
.
{ | ||
"type": "doc", | ||
"id": "scalar-kubernetes/BackupNoSQL", | ||
"label": "Kubernetes で NoSQL データベースをバックアップ" |
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.
"label": "Kubernetes で NoSQL データベースをバックアップ" | |
"label": "Kubernetes 環境で NoSQL データベースをバックアップ" |
Same as sidebars.js
.
{ | ||
"type": "doc", | ||
"id": "scalar-kubernetes/RestoreDatabase", | ||
"label": "Kubernetes でデータベースを復元" |
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.
"label": "Kubernetes でデータベースを復元" | |
"label": "Kubernetes 環境でデータベースを復元" |
Same as sidebars.js
.
{ | ||
type: 'doc', | ||
id: 'getting-started-auditor', | ||
label: 'ScalarDL Ledger と ScalarDL Auditor を通じてコントラクトを実行', |
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.
label: 'ScalarDL Ledger と ScalarDL Auditor を通じてコントラクトを実行', | |
label: 'ScalarDL Auditor モードを通じてコントラクトを実行', |
If we can use Auditor mode
as an official word, we can make this label shorter.
{ | ||
"type": "doc", | ||
"id": "getting-started-auditor", | ||
"label": "ScalarDL Ledger と ScalarDL Auditor を通じてコントラクトを実行" |
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.
"label": "ScalarDL Ledger と ScalarDL Auditor を通じてコントラクトを実行" | |
"label": "ScalarDL Auditor モードを通じてコントラクトを実行" |
Same as sidebars.js
.
Caution
This PR should not be merged until after we're ready to add the
displayed_sidebar: docsEnglish
configuration to the front-matter properties of English docs anddisplayed_sidebar: docsJapanese
configuration to the front-matter properties of Japanese docs. By adding this configuration, we can specify the appropriate sidebar language that should be displayed for the respective language when the visitor is on a page.This method follows Docusaurus's method for sidebars, as described in Understanding sidebar association.
Description
This PR updates the sidebar navigation for ScalarDL 3.9 (and will apply to later versions as well). Since we'll be hard-coding titles (
labels
) in the sidebar navigation in the near future, we should address this now before it becomes an issue.If we don't specify which sidebar navigation to show for each language, the sidebar navigation for Japanese docs would show in English.
Note
We hard-code the titles (
labels
) in the sidebar navigation so that we can make the titles shorted in the sidebar navigation while keeping longer titles at the top of each doc. Keeping titles within the actual doc provides readers with better context and is better for SEO.See an example of the sidebar navigation at:
Related issues and/or PRs
Note
Similar changes are being done in the ScalarDB docs:
Changes made
docs
todocsEnglish
.docsJapanese
) that matches the English docs.labels
) in thedocsJapanese
sidebar into Japanese.Checklist
N/A
Additional notes (optional)
N/A