Skip to content

update frontend docs - #515

Merged
martin-mfg merged 15 commits into
masterfrom
update-frontend-docs
Aug 26, 2026
Merged

update frontend docs#515
martin-mfg merged 15 commits into
masterfrom
update-frontend-docs

Conversation

@martin-mfg

Copy link
Copy Markdown
Member

@vercel

vercel Bot commented Aug 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
github-stats-extended-backend Ready Ready Preview Aug 26, 2026 12:44pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
github-stats-extended-frontend Ignored Ignored Aug 26, 2026 12:44pm

Request Review

@martin-mfg
martin-mfg requested a review from marcalexiei August 25, 2026 12:15

@marcalexiei marcalexiei 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.

I also made few improvements via #516

Comment on lines +166 to +169
<a href="/api/top-langs?username=anuraghazra&layout=donut">
<img class="card-preview-light" src="/api/top-langs?username=anuraghazra&layout=donut&theme=light_github" alt="Top Langs" />
<img class="card-preview-dark" src="/api/top-langs?username=anuraghazra&layout=donut&theme=dark_github" alt="Top Langs" />
</a>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The demo images above don’t have a link, while this one and the ones that follow do.
Should the link point to the specific card alongside the theme?
Also I'm wondering if the link to the image is useful in this context.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I think linking the images is somewhat helpful: It allows users to open the images and then inspect in the browser's address bar how it is configured. Without this, users have to: a) assume that we embed live images instead of fixed prerendered images and b) know how to view the url of an embedded image in their browser. And yes, I guess it makes sense to include the card's theme in the linked url.
In some cases the docs demonstrate that e.g. repo cards are intended to be linked to the repo they represent. Then linking to the image itself is not possible anymore, but imo linking to the repo is more important in these cases.

I see your new PR aims to make the linking consistent. So I won't make any changes to the linking here. And we can continue the discussion in #522.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

#507 brought back docs/*.
Will the old documentation be removed in this PR, or will that be done in a separate one?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Removing the old documentation is intended to happen via #488.

Comment thread apps/frontend/src/content/docs/docs/customization/theming.md Outdated
@martin-mfg
martin-mfg merged commit 3bf8e6d into master Aug 26, 2026
12 checks passed
@martin-mfg
martin-mfg deleted the update-frontend-docs branch August 26, 2026 13:25
martin-mfg added a commit that referenced this pull request Aug 27, 2026
…hem (#522)

> [!NOTE]
> Just a POC, marking as draft until #515 and #516 are merged.

- Adds `apps/frontend/src/plugins/rehypeCardImages.ts`:
a `/api` image that names no theme is emitted twice, once per site theme
— `light_github` / `dark_github` or the `*_repocard` pair.
  One that names a theme is left untouched.
- Every `/api` image also gets `loading="lazy" decoding="async"`,
  so the theme is not using costs no request.
- Drops the inline `<img>`/`<a>` HTML from `docs/index.md` and
`customization/theming.md`;
previews on the other docs pages became theme-aware without being
edited.
Once the other docs PRs are merged I'll rebase and apply the same change
everywhere.

---------

Co-authored-by: martin-mfg <2026226+martin-mfg@users.noreply.github.com>
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