ok it maybe a minor trifle … but
on every hugging repository it give:
“Files and versions”
ok if the list is long only a very small what ever (It’s not even a real noticeable button)
you must press to show the full list
example
is it possible to show that more explicite colored or what ever is possible ?
it is very hard to see that to expand the full list …
who can help? where i should send a feature request ?
where i should send a feature request ?
via email or on GitHub issue.
You cannot make that “Load more files” control more visible globally (for everyone) from your account settings. That UI is part of Hugging Face’s website. You have two real options:
Your example repo page clearly contains the subtle “Load more files” row at the bottom of “Files and versions.” (Hugging Face)
The “Files and versions” tab is a web view over a versioned repository (Git-like). The Hub is built to host very large repos and long file trees. (Hugging Face)
Showing thousands of rows at once is expensive for the browser and the server, so the UI uses pagination and “load more” patterns.
You can see the same tradeoff in the official API docs: when “expanded” metadata is requested, it is “more expensive for the server,” so fewer results are returned per page (50 vs 1000), and the library paginates behind the scenes. (Hugging Face)
That is strong evidence that Hugging Face intentionally avoids “render everything immediately.”
Small, low-contrast click targets are easy to miss and hard to activate. WCAG 2.2 explicitly explains that minimum target sizes help users activate controls reliably and avoid mis-clicks. (W3C)
WCAG also recommends larger targets reduce accidental actions. (W3C)
So your request is not cosmetic. It is discoverability + accessibility.
Do these in order. You get an immediate fix today, plus a clean request for a permanent fix.
These do not change the UI, but they make the hidden control easier to find.
These are crude, but they work immediately.
If your goal is “I want this to stand out on every HF repo I browse,” a user-style is the right tool.
Stylus is a browser extension that lets you apply custom CSS to websites (local-only). It does not affect other users.
Stylus has official docs on writing styles and using the browser inspector. (GitHub)
Install Stylus (extension). (Crime Web Store)
Open your repo page. (Hugging Face)
Use the DOM inspector:
In Stylus, create a new style for domain huggingface.co.
Target the element you found in the inspector and apply “make it look like a button.”
You want these properties:
padding, display:blockborder, background, font-weightcursor:pointer, :hoverExample CSS shape (you must adapt the selector you grab from Inspect):
/* Replace SELECTOR with the element you inspect for the "Load more files" row */
SELECTOR {
display: block !important;
padding: 10px 12px !important;
border: 2px solid currentColor !important;
border-radius: 8px !important;
font-weight: 700 !important;
cursor: pointer !important;
}
SELECTOR:hover {
filter: brightness(1.1) !important;
}
Why “adapt the selector”: Hugging Face can change class names. The inspect-and-select method stays correct even if the site markup changes.
If you want, tell me your browser (Chrome/Firefox) and paste the HTML snippet you see in Inspect for that row, and I will write an exact selector.
You want Hugging Face to change the Hub UI so everyone sees an obvious button.
Hugging Face explicitly says the “Site Feedback” category is for feedback about the website in general. (Hugging Face Forums)
And there are real examples of people filing minor front-end UI bug reports there. (Hugging Face Forums)
A Hugging Face forum answer points to [email protected] for website-related problems and feedback. (Hugging Face Forums)
The forum itself notes it is partly preference whether you use GitHub issues or the forum. (Hugging Face Forums)
If you file on GitHub, be aware:
huggingface/hub-docs is the Hub documentation repo. It might not be the right tracker for a frontend UI change, but it exists and is used for Hub-related issues sometimes. (GitHub)For your specific request (UI discoverability), the forum “Site Feedback” is the cleanest.
When teams get a vague “make it better,” it stalls. Ask for concrete UI changes:
This aligns with WCAG’s “targets should be easily activated,” and larger targets reduce accidental actions. (W3C)
Example:
Gives power users speed without forcing infinite scroll.
Title: Make “Load more files” in “Files and versions” more visible
Body:
Page example: (your link) (Hugging Face)
Problem: On repos with long file lists, the “Load more files” control is subtle and easy to miss. Users think the file list ended. Screenshot attached.
Request:
Why: This is a recurring usability problem on large repos.
If you mainly want to see or download everything, the official tooling is more reliable than the web list.
huggingface_hub download guide (single file or full repo). (Hugging Face)snapshot_download() supports allow_patterns / ignore_patterns so you do not pull huge files you do not need. (Hugging Face)This avoids “Load more files” entirely.