Skip to content

feat: removed scroll to top button#2089

Merged
dscho merged 2 commits intogit:gh-pagesfrom
Paulie-Aditya:feat/rmScrollBtn
Sep 30, 2025
Merged

feat: removed scroll to top button#2089
dscho merged 2 commits intogit:gh-pagesfrom
Paulie-Aditya:feat/rmScrollBtn

Conversation

@Paulie-Aditya
Copy link
Copy Markdown
Contributor

Feature: removed scroll to top button

As we are currently refreshing the website, per the discussion in issue #2067 , the consensus is to try a "Just Do It, and Revert It If Necessary" approach. Therefore, this PR removes the scroll-to-top button. If this change triggers a negative response from users, it will be reverted and we will pretend it never happened.

Removed the Scroll to top button in its entirety
This includes its css, the element itself and all references to it.

cc: @To1ne @dscho

</div>
</footer>
<a href="#top" class="no-js scrollToTop" id="scrollToTop" data-label="Scroll to top">
<img src="{{ relURL "images/icons/chevron-up@2x.png" }}" width="20" height="20" alt="scroll-to-top"/>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Shouldn't the chevron-up PNGs be deleted at the same time?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

sure, but that's in my .gitignore i guess how can I push it?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

oh there's the same in public/ as well

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I guess if I remove the pngs from static, then they would not be generated in the public/ folder
so the correct course would be to infact remove the pngs from static/

if the above is correct do give me the go ahead, I'll push these changes

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yes, public/ contains the output of Hugo. Parts of that tree are verbatim copies from files that live in static/.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

(And to make sure that this is clear: removing the files from static/ and then re-running Hugo will not remove the files from public/; You'd have to remove the public/ folder completely and then run Hugo again for that to happen.)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

great, thanks for confirming

Copy link
Copy Markdown
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

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

Okay, let's Just Do It!

@dscho dscho merged commit 0e8ab31 into git:gh-pages Sep 30, 2025
1 check passed
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