Skip to content

TUL/Reduce the footer vendor credit to the company name - #1466

Merged
milanmajchrak merged 1 commit into
customer/TULfrom
tul/fe-footer-dataquest-only
Aug 19, 2026
Merged

TUL/Reduce the footer vendor credit to the company name#1466
milanmajchrak merged 1 commit into
customer/TULfrom
tul/fe-footer-dataquest-only

Conversation

@MatusBeke

Copy link
Copy Markdown
Collaborator

Drops the Theme by wording from the footer's vendor credit and leaves the company name on its own.

Part of dataquest-dev/dspace-customers#592. Same change as #1464 (MENDELU), which the team agreed on after voting between several wordings. Rolling out to the remaining customers one branch at a time.

Before / after

before Theme by on its own line, + dataquest underneath
after + dataquest alone

Screenshot below.

What changed

Five deleted lines, nothing added.

footer.component.html — the <p class="theme-by">Theme by</p> above the link is gone. The anchor itself is untouched, so its [href], [title] and hard-coded + dataquest text all behave exactly as before.

footer.component.scss — the .theme-by rule (padding-top: 4px; font-size: 12px !important) is deleted along with the element it styled; it had no other use.

Note that on this branch the wording was hard-coded in the template rather than translated, so unlike MENDELU there is no i18n key to remove.

Verification

Built the production image from this branch and ran it against a local DSpace 7.5 backend with themed.by.* exposed:

rendered text + dataquest
.theme-by element not present in the DOM
href https://www.dataquest.sk/dspace
title + dataquest (from themed.by.company.name)
footer height 78px

Notes for the reviewer

  • The DSpace software copyright © 2002-2026 LYRASIS line above is untouched, so the software copyright and the vendor credit stay clearly separate.
  • The credit keeps the footer's existing link styling — no new CSS. Making it look more like a signature would be a visual change beyond what this issue asks for, so it is deliberately left alone.
  • The leading + in + dataquest is part of the text on this branch; on other customers it comes from the backend property.

🤖 Generated with Claude Code

The footer credit read "Theme by" stacked above "+ dataquest". Drop the
wording and leave the company name on its own.

The wording was hard-coded in the template here, not translated, so there
is no i18n key to remove. The .theme-by SCSS rule is deleted along with the
element it styled.

Refs dataquest-dev/dspace-customers#592

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
MatusBeke added a commit that referenced this pull request Aug 18, 2026
@MatusBeke

Copy link
Copy Markdown
Collaborator Author

Footer as it renders with this branch — TUL theme, production build against a local DSpace 7.5 backend:

TUL footer with the plain company name

The credit is now just + dataquest. The DSpace software copyright © 2002-2026 LYRASIS line above it is unchanged.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR simplifies the footer’s vendor credit by removing the “Theme by” line, leaving only the company name/link (as agreed in the referenced rollout for other customers).

Changes:

  • Removed the Theme by <p> element from footer.component.html while leaving the existing vendor link intact.
  • Removed the now-unused .theme-by styling from footer.component.scss.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/app/footer/footer.component.html Deletes the “Theme by” line so only the vendor link text remains.
src/app/footer/footer.component.scss Removes the .theme-by rule since the element no longer exists.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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.

3 participants