Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement Lighthouse CI (original #1130) #646

Closed
1 task
obulat opened this issue Apr 21, 2021 · 1 comment · Fixed by #4994
Closed
1 task

Implement Lighthouse CI (original #1130) #646

obulat opened this issue Apr 21, 2021 · 1 comment · Fixed by #4994
Assignees
@sarayourfriend
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend

Comments

@obulat
Copy link
Contributor

obulat commented Apr 21, 2021 •
edited
Loading

This issue has been migrated from the CC Search Frontend repository

Author: zackkrida
Date: Mon Aug 10 2020
Labels: ✨ goal: improvement,🏷 status: label work required,💻 aspect: code,🔒 staff only,🙅 status: discontinued,🤖 aspect: dx

We will implement Lighthouse CI to get some CI on front-end performance and a11y.

Implementation

  • I would be interested in implementing this feature.

Original Comments:

Issue author neeraj-2 commented on Thu Sep 03 2020:

Can ,i work on this?But ,please guide me what exactly we need to do?

source

zackkrida commented on Tue Sep 08 2020:

Hi @neeraj-2, this actually needs to be done by CC staff, since there's some edits to the repo configuration needed.
source
@obulat obulat mentioned this issue Feb 18, 2023
Closed
2 tasks
@obulat obulat transferred this issue from WordPress/openverse-frontend Feb 22, 2023
@obulat obulat added the 🧱 stack: frontend Related to the Nuxt frontend label Feb 22, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Feb 23, 2023
@obulat obulat added 🟩 priority: low Low priority and doesn't need to be rushed ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository labels Mar 8, 2023
@sarayourfriend sarayourfriend self-assigned this Sep 26, 2024
@sarayourfriend sarayourfriend moved this from 📋 Backlog to 🏗 In Progress in Openverse Backlog Sep 26, 2024
@sarayourfriend
Copy link
Collaborator

Given the WP Accessibility week coming up, I'm going to put this one in the background for my infrastructure work, as it will provide a11y advice for each change to the frontend. I think getting the baseline set up with reporting on individual PRs will be pretty simple, and we can work on refining our "assertions" and such later.

@sarayourfriend sarayourfriend mentioned this issue Sep 26, 2024
Merged
5 tasks
@openverse-bot openverse-bot moved this from 🏗 In Progress to ✅ Done in Openverse Backlog Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sarayourfriend sarayourfriend

Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend
Projects
Openverse Backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Collect lighthouse CI on each frontend change WordPress/openverse
2 participants
@obulat @sarayourfriend