Skip to content

Unify footer links and layout#176

Draft
NiHaiden wants to merge 1 commit intomainfrom
fix/footer-links-unify
Draft

Unify footer links and layout#176
NiHaiden wants to merge 1 commit intomainfrom
fix/footer-links-unify

Conversation

@NiHaiden
Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings April 22, 2026 18:32
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the footer component to use a unified layout and consistent external-link cards while improving visuals and adding community/docs links.

Changes:

  • Refactors Footer to a new structured layout with grid-based link cards and updated styling.
  • Adds shared external link props and expands external destinations (docs, forums, Discord, repo, site, Ko-fi).
  • Replaces <img> usage with next/image for footer assets.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


const externalLinkProps = {
target: "_blank",
rel: "noreferrer",
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

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

target="_blank" should include rel="noopener noreferrer" (not just noreferrer) to prevent reverse-tabnabbing and ensure consistent protection across browsers. Update externalLinkProps.rel accordingly.

Suggested change
rel: "noreferrer",
rel: "noopener noreferrer",

Copilot uses AI. Check for mistakes.

export default function Footer({ introRef }: { introRef?: RefObject<any> }) {
type FooterProps = {
introRef?: RefObject<HTMLDivElement | null>;
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

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

RefObject<T> already models current as T | null, so using RefObject<HTMLDivElement | null> adds redundant nullability (effectively HTMLDivElement | null | null). Prefer RefObject<HTMLDivElement> to keep the prop type precise and avoid propagating unnecessary null unions.

Suggested change
introRef?: RefObject<HTMLDivElement | null>;
introRef?: RefObject<HTMLDivElement>;

Copilot uses AI. Check for mistakes.
@codacy-production
Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes. Give us feedback

@NiHaiden NiHaiden marked this pull request as draft April 22, 2026 18:34
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.

2 participants