I've added an announcement using Gitea styling:
- Date of switchover (still needs to be determined)
- Commands to update Git Remote
- Link to DevTalk announcement post
- JavaScript to be able to dismiss the banner indefinitely (using Key-Value saved in browser LocalStorage)
Reviewed-on: https://projects.blender.org/infrastructure/gitea-custom/pulls/15
Slight highlight on strong and heading elements, to improve
readability.
On dark themes they display slightly lighter. On light themes there
isn't much of a difference (they're already pure black).
This pull request upgrades navigation global's markup and styles to Web Assets v2 pre-compiled _nav-global_ component, to improve visual consistency with other sites.
The Web Assets v2 _nav-global_ component brings UI fixes, spacing improvements and variable naming changes and cleanup to the navigation bar.
Co-authored-by: Pablo Vazquez <pablo@blender.org>
Co-authored-by: Thomas Dinges <thomas@blender.org>
Co-authored-by: Bastien Montagne <bastien@blender.org>
Reviewed-on: https://projects.blender.org/infrastructure/gitea-custom/pulls/9
Remove links to:
* Officially Maintained Add-ons
* Community Maintained Add-ons
Even though they may still be valid for 3.6 LTS, "Officially maintained"
add-ons are now part of core, and "Community maintained" are not really
maintained but moved to the Extensions platform.
In the latest releases, Gitea has fixed a lot of the styling issues we
had manually fixed in the past.
Additionally, the recent style adjustments they did look a lot better
so it is better to remove our custom styling as much as possible, and
follow stock Gitea. Making it easier to upgrade in the future.
* Fix broken styling
* Remove custom font
* Cleanup unused variables
* Add code comments
Move the cards "Blender, User Manual, Flamenco", to a "Products" dropdown
in the header, together with other projects. We can add more in the
future to give visibility to other projects.
Refactor the Releases, Modules and Projects cards into reusable
templates. Now they are used in the non-logged-in landing homepage
and in the logged-in dashboard.
