MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 142 Pull Requests Releases 90 Wiki Activity

feat: custom branding upload in site administration (nav icon, login logo, favicon) #181

New Issue
Closed
opened 2026-05-26 01:14:23 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-26 01:14:23 +00:00
Owner
Copy Link
Copy Source

Summary

Add a Branding section to Site Administration where admins can upload and manage custom images for:

  • Nav icon (top-left corner, small square icon)
  • Login logo (login page, full-sized logo)
  • Favicon (browser tab icon)

Currently Gitea uses a single logo.png for both the nav icon and login page, with no admin UI for uploading custom branding. Files must be manually placed via SSH.

Requirements

  • Separate nav icon from login logo (new logo-small.png or similar)
  • Admin UI page under Site Administration > Branding
  • Upload forms for each image type with preview
  • Files saved to custom/public/assets/img/ (persists across restarts)
  • Template changes to use separate files for nav vs login

Current behavior

  • logo.png used for both nav icon and login page (scaled down for nav)
  • favicon.png used for browser tab
  • SVG versions override PNG if present
  • No admin UI for uploading

Authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com

## Summary Add a Branding section to Site Administration where admins can upload and manage custom images for: - **Nav icon** (top-left corner, small square icon) - **Login logo** (login page, full-sized logo) - **Favicon** (browser tab icon) Currently Gitea uses a single logo.png for both the nav icon and login page, with no admin UI for uploading custom branding. Files must be manually placed via SSH. ## Requirements - [ ] Separate nav icon from login logo (new logo-small.png or similar) - [ ] Admin UI page under Site Administration > Branding - [ ] Upload forms for each image type with preview - [ ] Files saved to custom/public/assets/img/ (persists across restarts) - [ ] Template changes to use separate files for nav vs login ## Current behavior - logo.png used for both nav icon and login page (scaled down for nav) - favicon.png used for browser tab - SVG versions override PNG if present - No admin UI for uploading --- *Authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>*
jmiller commented 2026-05-26 17:46:19 +00:00
Author
Owner
Copy Link
Copy Source

Testing Proof

  • Admin branding page at /-/admin/branding: working (3-column table layout)
  • Nav icon upload: working (logo-small.png served, visible after hard refresh)
  • Login logo upload: working (login-logo.png on signin page, hidden when not set)
  • Favicon upload: working
  • Reset to default: working
  • Identity settings (App Name, Help URL, Support URL, Author): saved to app.ini
  • Deployed and verified on production v1.26.1-moko.05.03.00

Authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com

## Testing Proof - Admin branding page at /-/admin/branding: working (3-column table layout) - Nav icon upload: working (logo-small.png served, visible after hard refresh) - Login logo upload: working (login-logo.png on signin page, hidden when not set) - Favicon upload: working - Reset to default: working - Identity settings (App Name, Help URL, Support URL, Author): saved to app.ini - Deployed and verified on production v1.26.1-moko.05.03.00 *Authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>*
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 pending: testing
Feature implemented but not yet tested with documented proof
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 type: bug
Something isn't working
 type: bug
type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#181
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?