UI: Developer-website web-assets v2 upgrade #1
No reviewers
Labels
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/developer-website#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ui/web-assets-v2-upgrade"
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?
This pull request upgrades Web Assets to v2 by adding pre-compiled BWA styles (as of v2.0.0-alpha.32), resolves post-upgrade issues, and makes the necessary project-specific changes.
Web Assets v2 brings UI fixes, improvements, and new development features to the platform as detailed on the Web Assets v2 guidelines and notes wiki page.
Visual changes are kept to a minimum. Some project-level cleanup has been done when converting components to use Web Assets v2 markup and styles.
Screenshot:
Some project-level style overrides were added mainly to implement Web Assets modular vertical sizing, introduced in v2.
WIP: Developer-website web-assets v2 upgradeto UI: Developer-website web-assets v2 upgrade@ -19,3 +19,3 @@
<meta name="twitter:title" content="Blender Developer - developer.blender.org" />
<meta name="twitter:image" content="https://www.blender.org/wp-content/themes/bthree/assets_shared/images/blender_the_freedom_to_create_02.jpg" />
<link rel="stylesheet" href="https://code.blender.org/wp-content/themes/bthree-code/style.css?16052023" type="text/css" media="screen" />
<link rel="stylesheet" href="assets/css/style.css" type="text/css" media="screen" />
Missing the version argument so it gets cached by the browser.
@ -67,3 +57,3 @@
<div class="nav-global-container">
<nav>
<a href="https://developer.blender.org/" class="nav-global-logo is-active">
<a href="https://developer.blender.org/" class="nav-global-logo">
Why removing the is-active? This is the landing page of developer.blender.org, that's why it was set to be the "active" link.
I wasn't sure if highlighting the logo was intentional, as it isn't currently highlighted on all projects' landing pages (missing e.g. in Web Assets). I fixed it and will make sure that the logo highlighting prevails on other projects as well, that we use to indicate we're on the home page of a project.
Thanks!