The Hub turns any link wrapping an image into a fit-content block; :only-child
ignores text nodes, so the username links matched it too and stayed left-aligned
inside their centred cells.
fix: restore the team table cell alignment on the Hugging Face Hub
The Hub strips width, align and valign off table cells and its prose styles
set text-align:start, so every cell collapsed to left-aligned narrow columns.
Inline styles survive sanitization and outrank the :where() prose rule.
fix: keep card images inline on the Hugging Face Hub
The Hub renders cards through Tailwind preflight, which makes every image
display:block and adds 2em of vertical margin, breaking each logo and badge
onto its own line. Inline styles override both; three.js also needs a light
backdrop to stay legible against the dark theme.
chore: track binaries with LFS and add the Hugging Face card metadata
The profile README only renders on the organization page. Anyone who
opens this repository directly lands on an empty listing with no way to
tell what the two projects are or where they live.
Mirrors the site. "PhishGuard" read as a product name, and the thing is not a
product -- it is coursework whose own disclaimer says not to trust it with a
link. A descriptive heading sets that expectation before the disclaimer has to.
The tagline no longer restates the name, so it carries the distinctive part
instead: two algorithms each built twice, and the constant-predictor baseline
that stops a 98% accuracy reading as success on a corpus that is 92.5%
legitimate. The thumbnail's alt text now describes the recording rather than
naming the product.
Mirrors the site at fetiai.github.io in the content and order GitHub can render,
so moving between the two surfaces is never disorienting.
It lives at profile/README.md rather than the repository root, because only that
path is surfaced on the organization page -- a root README describes the
repository instead, which looks correct in the repo and blank where it matters.
Each thumbnail is an animated WebP wrapped in a link to that project's live demo,
so the most eye-catching element on the page is also its primary call to action.
WebP carries more quality per byte than GIF here: both are 720px wide against the
480px the GIFs managed, and both came out smaller.
Image sources are absolute raw URLs. Relative paths resolve against the file when
the README is viewed in the repository but against the repository root when it is
rendered on the organization page, so one of the two views would break; absolute
URLs work in both.
Every accuracy in the results table is read against the 0.9248 …
