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

Enhance Header and Footer Styles to Match Omeka Classic Theme #34

Open
designcomputer opened this issue Dec 12, 2024 · 0 comments
Open

Comments

@designcomputer
Copy link

The current implementation of the freedom theme has minor styling inconsistencies compared to the Omeka Classic version of the theme. The following changes align the design more closely with the Classic theme:

Header - Site Title Styling:
The site title in the header (.main-header__site-title a) should use the "Noto Serif" font-family and larger font size for a more prominent and classic appearance.

Footer - Navigation Link Wrapping:
Links in the footer navigation menu (.main-footer__col2 .navigation a) should not break in the middle of words, ensuring better readability and visual consistency.

Suggested Changes
Header: Update Site Title Styling
Modify the styles for .main-header__site-title a:

.main-header__site-title a {
    display: block;
    font-family: "Noto Serif", serif;
    font-size: 2rem;
    font-weight: 500;
    line-height: 1.2;
    text-decoration: none;
}

Footer: Prevent Text Wrapping in Links
Modify the styles for .main-footer__col2 .navigation a:

.main-footer__col2 .navigation a {
    white-space: nowrap; // Prevents the text in links from wrapping
}

Benefits of These Changes

The site title will better match the classic theme's aesthetic, improving user experience for those transitioning between versions.
Enhanced Readability:

Preventing navigation links from breaking in the middle of words ensures a more polished and professional appearance.

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

No branches or pull requests

1 participant