Skip to content
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

Merged
merged 5 commits into from
Sep 19, 2022
Merged

fix docs banner text #207

merged 5 commits into from
Sep 19, 2022

Conversation

urfreespace
Copy link
Member

@urfreespace urfreespace commented Sep 8, 2022

Unreleased version banner

image

Maintained version banner

image

Unmaintained version banner

image

Signed-off-by: Li Li <urfree@apache.org>
@urfreespace urfreespace self-assigned this Sep 8, 2022
@urfreespace urfreespace marked this pull request as ready for review September 8, 2022 07:48
@urfreespace urfreespace requested a review from momo-jun September 8, 2022 07:50
Signed-off-by: Li Li <urfree@apache.org>
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. "
Copy link
Contributor

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"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. "
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"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. "
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"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.

@Anonymitaet
Copy link
Member

Anonymitaet commented Sep 8, 2022

Thanks! @urfreespace

☘️☘️☘️ Banner wording

Can we consider using the following?

🔹🔹 🔹

For Next docs:

This is unreleased documentation for Next.
For the latest stable version, see 2.10.x.

🔹🔹 🔹

For the latest stable doc version (eg. 2.10.x):

This is the latest stable version 2.10.x.

🔹🔹 🔹

For docs in the maintenance cycle (eg. 2.9.x, 2.8.x):

This is the documentation for 2.9.x
For the latest stable version, see 2.10.x.

🔹🔹 🔹

For docs not in the maintenance cycle (eg. versions prior to 2.8.x):

This is the documentation for 2.6.2, which is no longer actively maintained.
For the latest stable version, see 2.10.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.

image

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}).",
Copy link
Member

@Anonymitaet Anonymitaet Sep 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In technical writing:

@urfreespace
Copy link
Member Author

@Anonymitaet @tisonkun Maybe we need to agree on the text and style of the banner

@tisonkun
Copy link
Member

tisonkun commented Sep 8, 2022

Hi @Anonymitaet

For the latest stable doc version (eg. 2.10.x):

This is the latest stable version 2.10.x.

I don't think we need a banner for the (expected) latest stable doc.

Agree on other wording changes.

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.

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.

@Anonymitaet
Copy link
Member

@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).

image

image

@tisonkun
Copy link
Member

tisonkun commented Sep 9, 2022

@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?

@Sepush
Copy link

Sepush commented Sep 9, 2022

@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 link border or some others will be better

@tisonkun
Copy link
Member

tisonkun commented Sep 9, 2022

don't use blue as the background just use white for light mode

This is a pivotal change. Let's stop further discussion in this direction.

@michaeljmarshall
Copy link
Member

I like the banner for the next docs, thank you for proposing this change @Anonymitaet!

@michaeljmarshall
Copy link
Member

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.

@labuladong
Copy link
Contributor

@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 think yellow is fine, we can make it darker if light yellow is too obvious on light blue.

@labuladong
Copy link
Contributor

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.

Hi @michaeljmarshall, could this Other button solve your problem? That page lists all versions:

image

@momo-jun
Copy link
Contributor

momo-jun commented Sep 9, 2022

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.

@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.”

@tisonkun
Copy link
Member

That page lists all versions:

Unfortunately, it doesn't. It still lists one 2.10.x entry for all 2.10.x series versions.

This is a separate topic, I suggest you start another thread to discuss it.

@tisonkun
Copy link
Member

@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.

@Anonymitaet
Copy link
Member

@tisonkun Thanks!
I'd still prefer to keep the banner on the latest stable version to keep the behavior consistent, so that users may not wonder why "this page does not have such info while others pages have", then they may stop for a while to think about it. What users want s "Do not make me think, I want to skim and scan info quickly".

@momo-jun
Copy link
Contributor

My personal opinion on the banner:

  1. Keep the current blue background color for the banner to minimize the effort. It's just a notification, not a striking/breaking change, and doesn't need highlights/cosmetics.
  2. No show the banner for the latest stable version of the doc, to eliminate noise for those who're already looking at the right docs. They don't even have to think, because they are possibly unaware of the banner behavior for other versions of docs.

@urfreespace
Copy link
Member Author

urfreespace commented Sep 19, 2022

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

Signed-off-by: Li Li <urfree@apache.org>
@urfreespace
Copy link
Member Author

I will merge it if there are no objections before 5:00 p.m @Anonymitaet @momo-jun

@Anonymitaet
Copy link
Member

@urfreespace Let's make a compromise and consensus on this:

☘️☘️☘️ Banner wording

Remove the banner for the latest stable version.

🔹🔹 🔹

For Next docs:

This is unreleased documentation for Next.
For the latest stable version, see 2.10.x.

🔹🔹 🔹

For the latest stable doc version (eg. 2.10.x):

This is the latest stable version 2.10.x.

🔹🔹 🔹

For docs in the maintenance cycle (eg. 2.9.x, 2.8.x):

This is the documentation for 2.9.x
For the latest stable version, see 2.10.x.

🔹🔹 🔹

For docs not in the maintenance cycle (eg. versions prior to 2.8.x):

This is the documentation for 2.6.2, which is no longer actively maintained.
For the latest stable version, see 2.10.x.

☘️☘️☘️ Banner color

Blue

@urfreespace
Copy link
Member Author

urfreespace commented Sep 19, 2022

@urfreespace Let's make a compromise and consensus on this:

☘️☘️☘️ Banner wording

Remove the banner for the latest stable version.

🔹🔹 🔹

For Next docs:

This is unreleased documentation for Next.
For the latest stable version, see 2.10.x.

🔹🔹 🔹

For the latest stable doc version (eg. 2.10.x):

This is the latest stable version 2.10.x.

🔹🔹 🔹

For docs in the maintenance cycle (eg. 2.9.x, 2.8.x):

This is the documentation for 2.9.x
For the latest stable version, see 2.10.x.

🔹🔹 🔹

For docs not in the maintenance cycle (eg. versions prior to 2.8.x):

This is the documentation for 2.6.2, which is no longer actively maintained.
For the latest stable version, see 2.10.x.

☘️☘️☘️ Banner color

Blue

Unreleased version banner

image

Maintained version banner

image

Unmaintained version banner

image

Signed-off-by: Li Li <urfree@apache.org>
@urfreespace urfreespace merged commit e8635a6 into main Sep 19, 2022
@momo-jun
Copy link
Contributor

@urfreespace @Anonymitaet can we remove the banner from this page?
image

@Anonymitaet
Copy link
Member

@urfreespace @Anonymitaet can we remove the banner from this page? image

sure

@urfreespace urfreespace deleted the update-docs-banner-texts branch September 30, 2022 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants