forgejo-docs/docs/user/profile.md

---
title: 'Profile customization'
license: 'Apache-2.0'
origin_url: 'https://github.com/go-gitea/gitea/blob/8d9e2d07f3f84a86265fdbe0ab7fcf63cc34ddbd/docs/content/usage/profile-readme.en-us.md'
---

By default the profile page of a user is the list of repositories they
own. It is possible to customize it with a short description that
shows to the left, under their avatar. It can now be fully
personalized with a markdown file that is displayed instead of the
list of repositories.

![Profile page](../_images/user/profile/profile-step1.png)

It uses the `README.md` file from the `.profile` repository of the
user, if it exists.

![Profile README.md](../_images/user/profile/profile-step2.png)

> **NOTE:** if a the `.profile` repository is private the `README.md` they contain will be displayed publicly. It is **strongly recommended** to verify no such repository exist in a given instance before upgrading.
docs: user: profile: document user custom profiles # Conflicts: # user/profile.md 2023-07-24 11:21:31 -04:00			`---`
			`title: 'Profile customization'`
			`license: 'Apache-2.0'`
sync with the latest changes from Gitea git log --patch faa28b5a44912f1c63afddab9396bae9e6fe061c..8d9e2d07f3f84a86265fdbe0ab7fcf63cc34ddbd . ':(glob)docs/*/.en-us.md' (cherry picked from commit b77359bfb1991c190d6caacea4a939f2c872fe39) 2023-09-22 13:20:11 -04:00			`origin_url: 'https://github.com/go-gitea/gitea/blob/8d9e2d07f3f84a86265fdbe0ab7fcf63cc34ddbd/docs/content/usage/profile-readme.en-us.md'`
docs: user: profile: document user custom profiles # Conflicts: # user/profile.md 2023-07-24 11:21:31 -04:00			`---`

			`By default the profile page of a user is the list of repositories they`
			`own. It is possible to customize it with a short description that`
			`shows to the left, under their avatar. It can now be fully`
			`personalized with a markdown file that is displayed instead of the`
			`list of repositories.`

move images to content dir and use relative paths This is necessary for the website upgrade to Astro v3, which has a new built-in image API. 2023-08-30 20:08:10 -04:00			`![Profile page](../_images/user/profile/profile-step1.png)`
docs: user: profile: document user custom profiles # Conflicts: # user/profile.md 2023-07-24 11:21:31 -04:00
			It uses the `README.md` file from the `.profile` repository of the
			`user, if it exists.`

move images to content dir and use relative paths This is necessary for the website upgrade to Astro v3, which has a new built-in image API. 2023-08-30 20:08:10 -04:00			`![Profile README.md](../_images/user/profile/profile-step2.png)`
docs: user: profile: document user custom profiles # Conflicts: # user/profile.md 2023-07-24 11:21:31 -04:00
			> NOTE: if a the `.profile` repository is private the `README.md` they contain will be displayed publicly. It is strongly recommended to verify no such repository exist in a given instance before upgrading.