Feature Description
Background
Currently in Gitea:
- Organization
- Only supports a single identifier (typically an English slug/name);
- Lacks multi-language display capability;
- Cannot be searched using localized (non-English) names.
- Repository
- Supports Description display and search;
- However, the Description is not prominently displayed on the repository homepage;
- Search on listing/home pages does not effectively leverage the Description field.
Proposed Enhancements
1. Multi-language Support for Organization
It is recommended to enhance Organization with multi-language capabilities:
- Allow defining localized names (e.g., Chinese, English, etc.);
- Automatically display based on user language preference;
- Enable search using localized names;
- Keep the existing slug/name as the unique internal identifier.
2. Improve Repository Description Display
Inspired by platforms like GitHub and GitLab:
- Display the repository Description more prominently on the repository homepage;
- Improve readability and quick understanding of repository purpose;
- Enhance repository listing and search:
- Support filtering/searching based on Description;
- Improve relevance of search results.
3. Introduce a “Title” Field (Recommended Approach)
Introduce a new field for both Organization and Repository:
New Field: Title (Multi-language)
This field is distinct from Description:
| Field |
Purpose |
| Name |
Unique system identifier (stable, technical) |
| Title |
Short, user-friendly, multi-language display name |
| Description |
Longer text for detailed explanation |
Suggested behavior:
- Title supports multiple languages;
- Display alongside Name (e.g.,
repo-name (Localized Title));
- Used for:
- UI display
- Search matching (higher priority than Description);
- Short and concise, suitable for list views.
Search Enhancements
Unify and enhance search behavior across:
Organization search fields:
- Name
- Title (multi-language)
- Description
Repository search fields:
- Name
- Title (multi-language)
- Description
Additional capabilities:
- Fuzzy matching;
- Multi-language-aware matching (prioritize user locale).
Value
This improvement would:
- Enhance internationalization (i18n)
- Better support for multilingual and global teams;
- Improve usability
- Reduce reliance on English-only identifiers;
- Improve search experience
- Allow users to find resources using natural/local language;
- Align with mainstream platforms
- Closer to user experience of GitHub / GitLab;
- Lower migration and learning costs.
Summary
It is recommended that Gitea:
- Introduce a multi-language Title field for Organization and Repository;
- Improve visibility of Description;
- Enhance search to cover Name / Title / Description;
- Retain existing Name as the unique identifier.
Screenshots
No response
Feature Description
Background
Currently in Gitea:
Proposed Enhancements
1. Multi-language Support for Organization
It is recommended to enhance Organization with multi-language capabilities:
2. Improve Repository Description Display
Inspired by platforms like GitHub and GitLab:
3. Introduce a “Title” Field (Recommended Approach)
Introduce a new field for both Organization and Repository:
New Field: Title (Multi-language)
This field is distinct from Description:
Suggested behavior:
repo-name (Localized Title));Search Enhancements
Unify and enhance search behavior across:
Organization search fields:
Repository search fields:
Additional capabilities:
Value
This improvement would:
Summary
It is recommended that Gitea:
Screenshots
No response