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.
The error was caused by using hsl colors for variables.
Solved by converting the used variables to hex values.
It seems that the editor used by gitea does not support other colors
than hex (transparent, hsl, rgb, etc).
Issue: https: //github.com/microsoft/monaco-editor/issues/1815
* Restore divide line below secondary nav bar, so that e.g. Issues is not in
the same space as the per repository Issues.
* Make secondary nav bar slightly more compact.
* Restore colored owner/repository name since this is information worth
highlighting to understand the context of what you're looking at.
* Slightly reduce contrast on divider lines.
* Fix inconsistent number pills styling on pull request page.
Use the same colors that `arc-green` imports from:
* Chroma from /web_src/less/themes/chroma/dark.less
* CodeMirror from /web_src/less/codemirror/dark.less
In line with the code blog and other dev sites (Wiki, DevTalk)
Everything is pretty much copied from the one in blender.org (_navbar_developer.php),
with some additions to make it work in Gitea.
The styling additions are in the <style> block with the comment "/* Custom styling for Gitea */"
The link to "Projects" is projects.blender.org (since it makes sense here but
not yet in the Code blog).
On the Gitea side, two custom templates have changed:
* head_navbar.tpml was changed to add the mobile navbar expand toggle.
* body_inner_pre.tpml contains the actual navbar, copied from the blender.org repo
with the following changes:
* Added <style> block custom for Gitea.
* Added custom notifications code from head_navbar.tpml
* Added user buttons (notif, create, register, sign in, etc),
See the area around "{{/* Here starts the custom styling for gitea. */}}"
* In order to style the buttons as such, the class `navbardev-btn` was added
to the Register, Sign In, Notifications, Create, and User dropdown buttons.
