Custom CSS and Custom Themes

[HarvsG]

• Gitea version (or commit ref): 1.8.2
• Git version: Na
• Operating system: Ubuntu 18.04
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

How do I load a custom stylesheet into my Gitea deployment? I have tried putting a styles.css in custom/public/ and custom/public/css/ the only method I have found that works is to place it in the templates which is sub-optimal.

Perhaps the best way to do this would be to allow for a custom/themes/ folder where users could create and share themes, then make the appropriate changes in custom/conf/app.ini and change the default theme.

It looks as if a similar idea was discussed before #56.
...

Edit

A shift+refresh revealed that a new index.css in custom/public/css/ will overwrite the gitea index.css and is helpful for changing some styles. However I am still finding myself running up against the semantic UI css. Which, itself, supports theming

[sapk]

I think you will find what you need under https://docs.gitea.io/en-us/customizing-gitea/ especially Other additions to the page you can add the custom/templates/custom/header.tmpl to load your css under custom/public/css/style.css that will be available at the path /css/style.css.

[HarvsG]

Thank you, this is what I did and it has worked well. Would still be cool to be able to develop whole custom themes that could be user-selectable and shared amongst the community.

[sapk]

If you want to share you can make a PR and add your css style under the contrib folder.
Being able to extend gitea via plugin (and theme) is a long goal but it need a lot of refactor and there is a lot of issue to be fix before. You can see that gitea still change a lot and for a plugin solution to exist we need to support a stable standard. We are near it because we soon be able to host gitea on a gitea instance and that mean a more stable approach.