CatAClock/forgejo

22845 commits 14 branches 246 tags 652 MiB

Author SHA1 Message Date

Author	SHA1	Message	Date
0ko	a0c9e81611	feat(ui): redesign migration selection screen (#6795 ) Ref https://codeberg.org/forgejo/design/issues/9. Changes: * Updated SVGs which had inconsistent paddings making them look off * Better usability on mobile * Better space efficiency on desktop, up to 4 columns * Nice responsive design * Less bland look on desktop. The borders were already here but invisible in Forgejo dark theme Preview: * https://codeberg.org/attachments/3c9e10ae-3315-46e5-b8bb-8021f6fd8936 * https://codeberg.org/attachments/8196ad89-5ab6-443a-98ce-a70dcc75bca9 * https://codeberg.org/attachments/24f52a14-2ac4-4949-8108-55c34bd3c650 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/6795 Reviewed-by: Beowulf <beowulf@beocode.eu> Reviewed-by: Otto <otto@codeberg.org>	2025-04-19 13:51:35 +00:00
silverwind	a062725758	Update JS and PY dependencies, build for `es2020` browsers (#28977 ) - Update all JS dependencies minus @mcaptcha/vanilla-glue - Fix new lint errors - Regenerate SVGs - Switch to maintained stylelint stylistic plugin - Tested Mermaid, Citation, Swagger, sorting - Raise ESBuild target to `es2020` as dictated by `pretty-ms` dependency.	2024-02-02 09:36:32 +00:00
wxiaoguang	faa28b5a44	Move public asset files to the proper directory (#25907 ) Move `public/` to `public/assets/` Some old PRs (like #15219) introduced inconsistent directory system. For example: why the local directory "public" is accessed by `http://site/assets`? How to serve the ".well-known" files properly in the public directory? For convention rules, the "public" directory is widely used for the website's root directory. It shouldn't be an exception for Gitea. So, this PR makes the things consistent: * `http://site/assets/foo` means `{CustomPath}/public/assets/foo`. * `{CustomPath}/public/.well-known` and `{CustomPath}/public/robots.txt` can be used in the future. This PR is also a prerequisite for a clear solution for: * #21942 * #25892 * discourse.gitea.io: [.well-known path serving custom files behind proxy?](https://discourse.gitea.io/t/well-known-path-serving-custom-files-behind-proxy/5445/1) This PR is breaking for users who have custom "public" files (CSS/JS). After getting approvals, I will update the documents. ---- ## ⚠️ BREAKING ⚠️ If you have files in your "custom/public/" folder, please move them to "custom/public/assets/". --------- Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Giteabot <teabot@gitea.io>	2023-07-18 18:06:43 +02:00

0ko

a0c9e81611

feat(ui): redesign migration selection screen (#6795 )

Ref https://codeberg.org/forgejo/design/issues/9.

Changes:
* Updated SVGs which had inconsistent paddings making them look off
* Better usability on mobile
* Better space efficiency on desktop, up to 4 columns
* Nice responsive design
* Less bland look on desktop. The borders were already here but invisible in Forgejo dark theme

Preview:
* https://codeberg.org/attachments/3c9e10ae-3315-46e5-b8bb-8021f6fd8936
* https://codeberg.org/attachments/8196ad89-5ab6-443a-98ce-a70dcc75bca9
* https://codeberg.org/attachments/24f52a14-2ac4-4949-8108-55c34bd3c650

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/6795
Reviewed-by: Beowulf <beowulf@beocode.eu>
Reviewed-by: Otto <otto@codeberg.org>

2025-04-19 13:51:35 +00:00

silverwind

a062725758

Update JS and PY dependencies, build for es2020 browsers (#28977 )

- Update all JS dependencies minus @mcaptcha/vanilla-glue
- Fix new lint errors
- Regenerate SVGs
- Switch to maintained stylelint stylistic plugin
- Tested Mermaid, Citation, Swagger, sorting
- Raise ESBuild target to `es2020` as dictated by `pretty-ms`
dependency.

2024-02-02 09:36:32 +00:00

wxiaoguang

faa28b5a44

Move public asset files to the proper directory (#25907 )

Move `public/*` to `public/assets/*`

Some old PRs (like #15219) introduced inconsistent directory system.

For example: why the local directory "public" is accessed by
`http://site/assets`? How to serve the ".well-known" files properly in
the public directory?

For convention rules, the "public" directory is widely used for the
website's root directory. It shouldn't be an exception for Gitea.

So, this PR makes the things consistent:

* `http://site/assets/foo` means `{CustomPath}/public/assets/foo`.
* `{CustomPath}/public/.well-known` and `{CustomPath}/public/robots.txt`
can be used in the future.

This PR is also a prerequisite for a clear solution for:
* #21942
* #25892 
* discourse.gitea.io: [.well-known path serving custom files behind
proxy?](https://discourse.gitea.io/t/well-known-path-serving-custom-files-behind-proxy/5445/1)

This PR is breaking for users who have custom "public" files (CSS/JS).
After getting approvals, I will update the documents.

----

## ⚠️ BREAKING ⚠️

If you have files in your "custom/public/" folder, please move them to
"custom/public/assets/".

---------

Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Giteabot <teabot@gitea.io>

2023-07-18 18:06:43 +02:00

Renamed from public/img/svg/gitea-gogs.svg (Browse further)

3 commits