UI: Conference website web-assets v2 upgrade #103970
No reviewers
Labels
No Label
legacy project
Infrastructure: Websites
Priority
High
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Resolved
Type
Bug
Type
Design
Type
Report
Type
To Do
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/conference-website#103970
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ui/web-assets-v2-update"
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 Git submodule Web Assets to v2, 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.
Important:
Some account screens / states are difficult to trigger locally for visual testing. As such, a more in-depth review is needed especially for these pages with dummy content e.g. on staging, to make sure all components look as expected before the PR can be merged and deployed.
WIP: Conference website web-assets v2 upgradeto UI: Conference website web-assets v2 upgradeI get a crash on loading the landing page locally, it's assuming
edition.header
.<div style="background-image: url({{ edition.header.url }}); background-position-y: 50%" class="hero-bg"></div>
Needs a check if
edition.header
exists.We already do that check everywhere btw. Perhaps the hero background could become a reusable component.
Thanks, it has been fixed locally.
In the meanwhile I'm checking if we can turn it into a reusable component.
Tickets boxes do not have a background (
products_table.html
)http://conference.local:8009/tickets/overview/
Top-bar accent button styling is lost:
Thanks, this has been fixed.
Web Assets' bundled navbar component has a default CTA button, with the above (more modest) styling – the new styling comes from here. If we want to make the button more prominent in the navbar, should we maybe change it in BWA to match the styling we currently have on the Conference website (so that to make the contrasty CTA button the Web Assets default)?
I think the root of the issue is that the Buy Tickets looks like
btn-primary
when it should bebtn-accent
. We don't always want all buttons to be this prominent. Bothprimary
andaccent
are valid.Styling differences in the user profile page.
.lead
class here, it just looks out of place now)The lack of "dim" text is also visible in the footer links:
Crash on presentation review pages.
http://conference.local:8009/2023/presentations/1911/review/
Broken active day button styling in schedule.
https://conference.blender.org/2022/schedule/?display=horizontal
The jump-to-top button has a huge shadow compared to production.
1aed7d9a11
to27f4f928ff
This makes a lot of sense, but was a bit tricky, as the
navbar
component has its own button styles to enable Web-Assets-style buttons in projects that don't use BWA as their framework, which somewhat clashed. I resolved this in https://projects.blender.org/infrastructure/web-assets/releases/tag/v2.0.0-alpha.35, that enables default BWA buttons to be used in navbar (and changed tobtn-accent
here accordingly).Festival: voting is broken and stars are always styled yellow, don't react on hover.
http://conference.local:8009/2023/festival/entries/556/
Review issues:
<h3>
not closed, making the entire description a title.Example: http://conference.local:8009/2021/presentations/1301/review/
First pass of review
@pablovazquez thank you for your very thorough feedback! 🙏
All of the above items should be improved or fixed now. I'm reopening the review request.
This issue is still present.
Also visible in elements with
shadow-lg
like the box in Festival Finals voting page.Thank you. It seems this was a v2 issue on the Web Assets level. All shadow styles have been systematically revised and fixed in v2.0.0-alpha.37 – shadows should now look correct on all pages.
A small one, dropdown's z-index seem to conflict with items with fixed positions like the festival vote footer using
.fixed-bottom
among others:row fixed-bottom position-sticky bg-light shadow-lg festival-vote-footer
Example (if you add enable the festival and add some movies yourself) http://conference.local:8009/2024/festival/finals/
It's not a big deal though because it just happens on long menus which most of the time only admins get anyway. But it'd be good to tackle that in web-assets. Basically have dropdowns z-index be the highest up, over fixed items z-index even.
Also noticed the z-index is not a CSS variable but a fixed number (probably a Sass variable), it might be easier to customize as CSS variable.
@pablovazquez thank you for reporting this. I resolved the issues in Web Assets the following way:
navbar
's z-index properties. As a parent element, it was overlapped by subsequent markup items with same or higher z-indexes. Because of this, its children elements (like dropdowns) couldn't take precedence, even if their local z-indexes were higher. Now it should work as expected.With the above changes I think the PR is ready to be merged, and I'm going ahead as discussed IRL.
Thanks for tackling all the issues!