Eddybrando Vásquez
Eddybrando Vásquez
We currently have 3 files with definitions for links: `appLinks`, `megaMenuLinks` and `menuLinks`. These files live in the `constants/` directory in the root, which implies that they are global constants...
We've had some style regressions that are quite hard to catch in our code reviews. And as the codebase grows, the more likely are these kind of bugs to appear...
We have identified some Carbon CSS overwrites, like the one applied to the accordions in **ContentAccordion** and **StartLocally**. This overwrite (and potentially others) should be reviewed to check the need...
We're repeating some fairly generic definitions recurrently in our codebase. Some examples may include classes that hide an element based on a breakpoint, or classes that add vertical spacing between...
The typography of the menu links were not part of the typography refactor (#1569). As pointed out by @y4izus in https://github.com/Qiskit/qiskit.org/pull/1724#pullrequestreview-654200849, we should keep track of this to review these...
The goal is to work on the redesign of the Hero section for the "sm breakpoint". We need to review the Figma design and adjust it so that it leaves...
We need to adapt the individual learn pages (https://qiskit.org/learn/intro-qc-qh/) to support the new layout for the "max" breakpoint.
We need to adapt the [Metal page](https://qiskit.org/metal) to support the new layout for the "max" breakpoint.
In order to automate accessibility checks for Qiskit.org, we should integrate into our CI pipeline a tool like Cypress + [cypress-accessibility-checker](https://www.npmjs.com/package/cypress-accessibility-checker), Cypress + [cypress-axe](https://www.npmjs.com/package/cypress-axe) or [Lighthouse](https://developers.google.com/web/tools/lighthouse). Also, we might want...
For consistency and so that IDEs / text editors like VS Code's auto-lint functionality works as expected, creating a `.prettierrc` file might be helpful. We could take as an example...