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

Update website top navigation bar #3670

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

aneta-petrova
Copy link
Member

What changes are you introducing?

  • Removing a few links from the main landing page and adding them to the top menu bar instead
  • Replacing the current helmet logo with helmet + website label

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

Split from and depends on #3657

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

N/A

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 labels Feb 13, 2025
@@ -12,7 +12,7 @@ function buildNavigation() {

return `<nav>
<a href="/">
<img class="logo" src="/img/helmet.svg" alt="Home">
<img class="logo" src="/img/helmet.png" alt="Home">
Copy link
Member Author

Choose a reason for hiding this comment

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

A note for future me/future someone: We want svg here.

Copy link
Member

Choose a reason for hiding this comment

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

Wouldn't it be easier to add the text as real text in here instead of adding it to the image? That way search engines can also read it. Or is it about using a specific font?

Copy link
Member Author

Choose a reason for hiding this comment

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

To answer your questions:

I hope that explains my intentions but truth be told, this is one of the things that I'm hoping to get @kmalyjur's input on once she and I are able to meet again.

I appreciate your feedback, please keep it coming, this is a good place to record any concerns that we should address.

Copy link
Member

Choose a reason for hiding this comment

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

I intended the helmet + text as a single clickable unit. This is supposed to be a link to the home page and I want to avoid a situation where only the image part is clickable and not the text.

You can do that with HTML too:

  <a href="/">
    <img class="logo" src="/img/helmet.svg" alt="Home">
    Foreman Documentation
</a>

Also, yes, it's about using a specific font.

You can load fonts into CSS and use a specific font too.

Copy link

The PR preview for 921034e is available at theforeman-foreman-documentation-preview-pr-3670.surge.sh

The following output files are affected by this PR:

show diff

show diff as HTML

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 Needs tech review Requires a review from the technical perspective
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants