-
Notifications
You must be signed in to change notification settings - Fork 180
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
fix docs banner text #207
fix docs banner text #207
Conversation
Signed-off-by: Li Li <urfree@apache.org>
@@ -25,7 +25,7 @@ function UnreleasedVersionLabel({ siteTitle, versionMetadata }) { | |||
}} | |||
> | |||
{ | |||
"This is unreleased documentation for {siteTitle} {versionLabel} version." | |||
"This documentation is for an unreleased {siteTitle} {versionLabel} version of Apache Pulsar. " |
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.
Seems {siteTitle} is duplicate with Apache Pulsar
, and maybe {versionLabel} can also be removed.
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 documentation is for an unreleased {siteTitle} {versionLabel} version of Apache Pulsar. " | |
"This documentation is for an unreleased version of Apache Pulsar. " |
Agree. Simply writing "an unreleased version" works fine for me.
@@ -25,7 +25,7 @@ function UnreleasedVersionLabel({ siteTitle, versionMetadata }) { | |||
}} | |||
> | |||
{ | |||
"This is unreleased documentation for {siteTitle} {versionLabel} version." | |||
"This documentation is for an unreleased {siteTitle} {versionLabel} version of Apache Pulsar. " |
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 documentation is for an unreleased {siteTitle} {versionLabel} version of Apache Pulsar. " | |
"This documentation is for an unreleased version of Apache Pulsar. " |
Agree. Simply writing "an unreleased version" works fine for me.
@@ -41,7 +41,7 @@ function UnmaintainedVersionLabel({ siteTitle, versionMetadata }) { | |||
}} | |||
> | |||
{ | |||
"This is documentation for {siteTitle} {versionLabel}, which is no longer actively maintained." | |||
"This documentation is for an out-of-date {siteTitle} {versionLabel} version of Apache Pulsar. " |
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 documentation is for an out-of-date {siteTitle} {versionLabel} version of Apache Pulsar. " | |
"This documentation is for an out-of-date version of Apache Pulsar. " |
Ditto. The sidebar and URL should already identify which version it is.
Thanks! @urfreespace ☘️☘️☘️ Banner wording Can we consider using the following? 🔹🔹 🔹 For
🔹🔹 🔹 For the latest stable doc version (eg. 2.10.x):
🔹🔹 🔹 For docs in the maintenance cycle (eg. 2.9.x, 2.8.x):
🔹🔹 🔹 For docs not in the maintenance cycle (eg. versions prior to 2.8.x):
☘️☘️☘️ Banner color Blue is more appropriate than yellow/red here. Yellow / red can be used to indicate important hints, tips, guidance, restrictions, advice that might be overlooked, or the possibility of damage to software. If yellow / red is overused, they lose their significance. Thoughts? @tisonkun @momo-jun @DaveDuggins @D-2-Ed |
"description": "The label used to tell the user that he's browsing an unmaintained doc version" | ||
}, | ||
"theme.docs.versions.latestVersionSuggestionLabel": { | ||
"message": "We recommend you use the {latestVersionLink} ({versionLabel}).", |
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.
In technical writing:
- Avoid first-person pronouns. Details see Pulsar Documentation Writing Style Guide.
- Avoid using "recommend" if possible. A phrase such as “We recommend that you take the following action” could create a potential marketing or legal problem. For how to write this tip, see fix docs banner text #207 (comment).
@Anonymitaet @tisonkun Maybe we need to agree on the text and style of the banner |
Hi @Anonymitaet
I don't think we need a banner for the (expected) latest stable doc. Agree on other wording changes.
Here we'd like to hint the users to use the latest stable doc. So it's not overuse from my perspective. You can get the image why it's a hint from: You can find several projects that don't follow this way. But think of the Pulsar situation - we don't maintain quite a few old versions, and it's still under rapid development. We don't want users to use an old version and ask for bug fixes cherry-pick, but just try out the latest stable. For users already use an old version, the color is not a big deal. |
@tisonkun thanks! Since the Pulsar website background is light blue, yellow / red is too obvious on light blue than it is on the white background (eg. Docusaurus). |
@Anonymitaet I agree that color is hard 🤣 The comment here is to make it relatively obvious, but choosing a nice color can be improved later. @labuladong @Sepush do you have some input on which color is suitable for this purpose? |
I recommend don't use blue as the background just use white for light mode, If you want blue theme,only apply for the |
This is a pivotal change. Let's stop further discussion in this direction. |
I like the banner for the |
I'm not sure where to provide this feedback (so feel free to redirect me to a different channel), but I find the recent change to version numbers being 2.10.x to be confusing. I like to know that I am looking at the exact documentation for a version, since there are minor changes between patch versions that might affect documentation. Without explicit versioning, we lose important nuance. |
I think yellow is fine, we can make it darker if light yellow is too obvious on light blue. |
Hi @michaeljmarshall, could this |
@michaeljmarshall you can refer to PIP-190 for more details. In short, the changes between patch versions are annotated with a version-specific note like “This configuration is only available in 2.10.1 and later versions.” |
Unfortunately, it doesn't. It still lists one This is a separate topic, I suggest you start another thread to discuss it. |
@Anonymitaet @urfreespace improving color can be a continuous effort. If we now agree on the wording part. We can push forward the changes in wording. I have one comment here: Don't show a banner for the latest stable version. Users are already on the version we'd recommend and nothing should be noticed. |
@tisonkun Thanks! |
My personal opinion on the banner:
|
As the new text is more explicit and precise so update the text from this Pr and keep the background color blue, are you all agree? @Anonymitaet @tisonkun @momo-jun /cc @tuteng |
I will merge it if there are no objections before 5:00 p.m @Anonymitaet @momo-jun |
@urfreespace Let's make a compromise and consensus on this: ☘️☘️☘️ Banner wording Remove the banner for the 🔹🔹 🔹 For
🔹🔹 🔹
🔹🔹 🔹 For docs in the maintenance cycle (eg. 2.9.x, 2.8.x):
🔹🔹 🔹 For docs not in the maintenance cycle (eg. versions prior to 2.8.x):
☘️☘️☘️ Banner color Blue |
Unreleased version bannerMaintained version bannerUnmaintained version banner |
@urfreespace @Anonymitaet can we remove the banner from this page? |
sure |
Unreleased version banner
Maintained version banner
Unmaintained version banner