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

Add a banner for unsupported and pre-release #3653

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

aneta-petrova
Copy link
Member

What changes are you introducing?

This should show a banner/ribbon for all guides in nightly and unsupported releases, with a link leading to the main docs.theforeman.org page where users can read more information on supported releases.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Solution suggested in #695 (comment)

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Credit: https://simonwhitaker.github.io/github-fork-ribbon-css/

Checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • Foreman 3.8/Katello 4.10
  • Foreman 3.7/Katello 4.9 (Satellite 6.14)
  • We do not accept PRs for Foreman older than 3.7.

@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Feb 11, 2025
@@ -6,10 +6,22 @@
:toclevels: 3
ifndef::satellite[]
:docinfodir: common
++++
Copy link
Member Author

Choose a reason for hiding this comment

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

Using passthrough blocks like this is ugly but I couldn't find a better way.

@aneta-petrova aneta-petrova removed Needs testing Requires functional testing Needs tech review Requires a review from the technical perspective labels Feb 11, 2025
Copy link

github-actions bot commented Feb 11, 2025

The PR preview for b5bc07a is available at theforeman-foreman-documentation-preview-pr-3653.surge.sh

The following output files are affected by this PR:

show diff

show diff as HTML

@aneta-petrova aneta-petrova marked this pull request as draft February 11, 2025 20:17
@aneta-petrova
Copy link
Member Author

aneta-petrova commented Feb 11, 2025

This seems to break some guides and while I don't know why yet, this is what the banners look like locally:

  • nightly:
    image

  • unsupported:
    Screenshot From 2025-02-11 21-26-06

@aneta-petrova aneta-petrova force-pushed the ribbon branch 2 times, most recently from 93187ed to 80916b6 Compare February 11, 2025 21:21
@aneta-petrova
Copy link
Member Author

Something about adding the ribbon made GHA suddenly remember that there are a few issues with incorrect heading levels. So I'm now including a few lines to fix these headings.

I also moved the ribbon to the bottom right corner where it's arguably easier to overlook but at least it doesn't overlap with anything important like the version dropdown.

@aneta-petrova aneta-petrova marked this pull request as ready for review February 11, 2025 21:42
Copy link
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

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

Great work! I like the ribbons a lot. I also don't mind that they cover some text on unsupported versions; I assume this goes away when scrolling?

Alternative wording: "Supported RC version" in favor of "pre-release version".

@aneta-petrova
Copy link
Member Author

Great work! I like the ribbons a lot. I also don't mind that they cover some text on unsupported versions; I assume this goes away when scrolling?

I think the banners should be fixed so that they don't go away with scrolling. Users should see them at all times, not just when they open a guide for the first time.

I reverted to the top-right position. You can take a look at any non-satellite guide preview to check it out:

Screenshot From 2025-02-12 09-37-37

This is not great but I can only assume that I could tweak the position of the ribbon to make it start below the blue top menu bar so that there is no overlap? I haven't really tried yet, though.

Alternative wording: "Supported RC version" in favor of "pre-release version".

I'd rather keep the wording as clear as possible and I don't think the "RC" acronym is quite that. I chose "pre-release" based on #695 (comment) and was hoping that because the ribbon links to the docs.theforeman.org main landing page, all the supported/unsupported/supported RC context will be clarified there.

@aneta-petrova aneta-petrova linked an issue Feb 12, 2025 that may be closed by this pull request
@aneta-petrova aneta-petrova force-pushed the ribbon branch 2 times, most recently from fa54312 to 54767c1 Compare February 13, 2025 11:01
@aneta-petrova
Copy link
Member Author

Notes from today's triage: Generally, ack. The only real blocker is the overlap described in #3653 (comment). @kmalyjur can help with that.

We also discussed possibly using a different color that's more aligned with the Foreman color palette. That decision doesn't have to be made as part of this PR, it can be a follow up.

Co-authored-by: Ewoud Kohl van Wijngaarden <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Release Candidate Banner
3 participants