Per-Project Logo to use as og:image (for social posts) #1714

New Issue

GiteaMirror · 2025-11-02T04:10:45-06:00

GiteaMirror commented

2025-11-02 04:10:45 -06:00

Originally created by @coolaj86 on GitHub (Apr 20, 2018).

If I paste a project link into Facebook, LinkedIn, Twitter, etc it will first try to read from the og:image tag to get the photo that it should use in the image preview.

For example, https://git.coolaj86.com/coolaj86/greenlock.js shows this in the <head>:

<meta property="og:image" content="https://secure.gravatar.com/avatar/0a8b345ddcfc5401f578c850442f1e1b?d=identicon">

And shows this preview:

However, I have a specific logo for this project and I would rather show the project logo than my own headshot.

I kindly request a feature to be added which would allow a specific logo to be chosen. For example, if there is a .githeme/logo.png or .gittheme/logo.jpg in the project repository, that that be used instead of the default author logo.

branch master:

.gittheme
.gittheme/logo.png
main.go
README.md

I'd also like to have a feature so that if .gittheme/config.yml exists that it specifies whether the logo (if none is present already) be pulled from the author, organization, or site. For example:

.gittheme/config.yml:

logo: 'site'

Originally created by @coolaj86 on GitHub (Apr 20, 2018). If I paste a project link into Facebook, LinkedIn, Twitter, etc it will first try to read from the `og:image` tag to get the photo that it should use in the image preview. For example, https://git.coolaj86.com/coolaj86/greenlock.js shows this in the `<head>`: ``` <meta property="og:image" content="https://secure.gravatar.com/avatar/0a8b345ddcfc5401f578c850442f1e1b?d=identicon"> ``` And shows this preview: ![screen shot 2018-04-20 at 3 13 36 pm](https://user-images.githubusercontent.com/122831/39074146-80fb1c0e-44ad-11e8-83c1-5ceb26eebf68.png) However, I have a specific logo for this project and I would rather show the project logo than my own headshot. I kindly request a feature to be added which would allow a specific logo to be chosen. For example, if there is a `.githeme/logo.png` or `.gittheme/logo.jpg` in the project repository, that that be used instead of the default author logo. `branch master`: ``` .gittheme .gittheme/logo.png main.go README.md ``` I'd also like to have a feature so that if `.gittheme/config.yml` exists that it specifies whether the logo (if none is present already) be pulled from the author, organization, or site. For example: `.gittheme/config.yml`: ``` logo: 'site' ```

GiteaMirror added the type/proposal type/enhancement labels 2025-11-02 04:10:45 -06:00

GiteaMirror closed this issue

2025-11-02 04:10:45 -06:00

GiteaMirror commented

2025-11-02 04:10:46 -06:00

@lafriks commented on GitHub (Apr 21, 2018):

I would rather see this as setting in database not in git (also from performance point of view)

@lafriks commented on GitHub (Apr 21, 2018): I would rather see this as setting in database not in git (also from performance point of view)

GiteaMirror commented

2025-11-02 04:10:46 -06:00

@coolaj86 commented on GitHub (Apr 23, 2018):

Performance is a non-issue. All of the top-level git file structure is already cached anyway.

Putting it in a database would make it proprietary and non-portable.

As the number of git systems grows, I hope that a standard emerges so that features like default issue templates and og tags work just as well in gitea as they do on github or gitlab.

@coolaj86 commented on GitHub (Apr 23, 2018): Performance is a non-issue. All of the top-level git file structure is already cached anyway. Putting it in a database would make it proprietary and non-portable. As the number of git systems grows, I hope that a standard emerges so that features like default issue templates and og tags work just as well in gitea as they do on github or gitlab.

GiteaMirror commented

2025-11-02 04:10:46 -06:00

@saitho commented on GitHub (May 1, 2019):

Related to #694

@saitho commented on GitHub (May 1, 2019): Related to #694

GiteaMirror commented

2025-11-02 04:10:46 -06:00

@lunny commented on GitHub (May 6, 2019):

@solderjs maybe @sergey-dryabzhinsky could also solve this one in his coming PR.

@lunny commented on GitHub (May 6, 2019): @solderjs maybe @sergey-dryabzhinsky could also solve this one in his coming PR.

GiteaMirror commented

2025-11-02 04:10:46 -06:00