Web Development good first issues

This issue is titled '[Notes]' and includes a link to an asset, likely an image or document, labeled 'Notes'. The body of the issue contains only the word 'Notes' and the asset link. It appears to be a placeholder or a very early stage of documenting something, with the actual content or purpose of the 'Notes' being unclear without further context.

This issue proposes enhancing the issue filtering and sorting capabilities. Users should be able to filter issues by title and sort them by criteria such as the number of assignees, in addition to the existing filters for programming language, repository, and issue type.

This issue requests the addition of a "Keyboard editing" subsection to the README files. This section should document existing keyboard shortcuts for canvas cursor movement, painting, erasing, undo, and redo, ensuring they are discoverable and verified in the live application. No new functionality or dependencies are required.

This issue requests the implementation of a reduced-motion preference for the user interface. The goal is to disable or minimize CSS transitions and repeating animations when a user indicates a preference for reduced motion, while ensuring essential visual cues like focus indicators remain visible.

This issue requests the addition of a new example to the project's README file. The example should showcase the editor's capabilities with a non-heart bead pattern, using an original or CC0 image. The addition needs to include compact before/after images in both English and Chinese READMEs, with image file sizes kept under 500 KB, without altering any application functionality.

This issue proposes adding support for Namecheap as a DNS-01 challenge provider for ACME domain validation. It outlines the steps required to implement a new `DnsProvider` for Namecheap, including API interaction, configuration updates, and documentation. A key challenge is Namecheap's API requiring multiple credentials and a full host list replacement for record updates.

This issue proposes adding support for ClouDNS as a DNS-01 challenge provider in the Raddy ACME client. The implementation will involve creating a new `DnsProvider` for ClouDNS, integrating it into the configuration parsing, and updating documentation. A key challenge is handling ClouDNS's authentication mechanism, which uses an `auth-id` and `auth-password` pair instead of a single token, requiring a grammar extension.

This issue aims to publish reproducible conversion benchmarks as outlined in the project's roadmap. Key requirements include using pinned settings for fixtures, documenting the testing environment and commands, and including quality/structure measurements alongside runtime performance. The goal is to provide transparent and verifiable benchmark data.

This issue proposes adding a new automated test to ensure keyboard accessibility in the editor. The test should focus on a critical keyboard interaction, verify the resulting user-visible state, and be reliable across different browsers. The goal is to prevent regressions in existing keyboard navigation and functionality.

This issue requests a review of English UI elements on mobile viewports (360px and 390px) to ensure action labels are clear, not clipped, and don't wrap awkwardly. The goal is to improve usability by making primary actions understandable without relying solely on icons, while also maintaining touch-target and overflow checks.

This issue requests the addition of a single, permissively licensed image fixture to the project's test suite. The goal is to ensure conversion functionality is covered by regression tests, with clear documentation of the image's origin and licensing terms. The fixture should be placed in `tests/fixtures/` and accompanied by a relevant unit or E2E test.

This is a feature request to include 'course_level' in the API response. The data is already available in the database, and the change primarily involves updating the `server.py` file to expose this information. This will allow users to see course level details.

A bug in the scraping script `scraper.py` is causing incorrect parsing of course unit values. The script uses the wrong key ('units' instead of 'unit_value') when retrieving unit information, leading to a default value of '6' being assigned. Additionally, the script crashes if the scraped text for units contains non-digit characters.

The user is experiencing issues with Nginx Proxy Manager (NPM) not recognizing client certificates after setting up a second Certificate Authority (CA) in VaulTLS. They are currently using a single CA file (`ca-tls.cert`) for mTLS and need guidance on how to properly configure NPM to accept certificates signed by multiple CAs.

This issue proposes adding support for Google Cloud DNS as a DNS-01 challenge provider for ACME domain validation. It outlines the necessary steps, including implementing a new `DnsProvider` for Google Cloud DNS, updating configuration and documentation, and handling API credentials. The goal is to allow users to prove domain control using Google Cloud DNS by specifying it in their Raddyfile.

This issue proposes adding support for Linode as a DNS-01 challenge provider for ACME domain validation. The task involves implementing a new `DnsProvider` for Linode, integrating it into the existing system, and updating documentation. The implementation should follow the pattern of the existing Cloudflare provider, including mock API tests for network-independent testing.

This issue proposes adding support for Vultr as a DNS-01 challenge provider for ACME domain validation. The task involves implementing a new `DnsProvider` for Vultr, integrating it into the existing configuration and factory patterns, updating documentation, and ensuring comprehensive mock-API testing.

This issue proposes adding support for Hetzner DNS as a provider for the DNS-01 challenge in the Raddy ACME client. The task involves implementing a new `DnsProvider` for Hetzner, integrating it into the configuration and build system, updating documentation, and ensuring mockable tests are in place. This will allow users to obtain SSL certificates by proving domain ownership via Hetzner DNS records.

This issue proposes adding support for DigitalOcean as a DNS-01 challenge provider for ACME domain validation. The task involves implementing a new `DnsProvider` for DigitalOcean, integrating it into the existing system, and updating documentation. The implementation should follow the patterns established by the Cloudflare provider, including mock API tests for network-independent testing.

This issue proposes adding support for Amazon Route 53 as a DNS-01 challenge provider for ACME domain validation. The task involves implementing a new `DnsProvider` for Route 53, integrating it into the configuration and factory, updating documentation, and handling AWS API authentication which requires a specific grammar extension for credentials.

This issue proposes adding support for the DNSPod DNS-01 challenge provider to the Raddy ACME client. The implementation will involve creating a new `DnsProvider` for DNSPod, integrating it into the existing configuration and factory patterns, and updating documentation. A key consideration is how to handle DNSPod's `ID,Token` API authentication within the current single-token grammar.

This issue proposes adding support for AliyunDNS as a DNS-01 challenge provider in the Raddy ACME client. It involves implementing a new `DnsProvider` for AliyunDNS, handling its specific API authentication (AccessKey ID and Secret), and updating configuration parsing and documentation. The goal is to allow users to prove domain control via AliyunDNS when using the Raddyfile.

This issue proposes adding a new `download` method to the `ApiService` to handle endpoints that return binary file content, such as PDFs or ZIP archives. The goal is to provide first-class support for file downloads while leveraging the existing request pipeline, including options, interceptors, and error handling. The method would return the file data as a `Blob`, allowing consuming applications to manage the saving process.

Implement a sitemap for the LibreCode website (librecode.coop) similar to the one found in the provided GitHub pull request (https://github.com/LibreSign/site/pull/150). This involves creating the sitemap file and ensuring it's correctly integrated into the existing website's infrastructure, likely using the provided Docker Compose setup.

This issue requests the implementation of a search function for flowers, allowing users to find them by name. The current implementation has syntax and logic errors that need to be fixed.

The MultiSelect component in PrimeVue incorrectly deselects an option when the Tab key is pressed. This occurs both when the panel is open and an option is focused, and also when tabbing past a closed MultiSelect field that has `autoOptionFocus` enabled.

The toggle mask button in the PrimeVue Password component is not keyboard-operable, failing WCAG 2.1.1. Keyboard-only users and screen reader users cannot reveal or hide the password, making the feature inaccessible.

When the `template` property of a `MenuItem` is used in PrimeReact, the first item in the menu incorrectly receives a `p-focus` CSS class, indicating it has focus. This occurs even when the menu item is not actually interacted with, and the issue persists in the latest version of the library.

The calendar overlay in PrimeReact incorrectly navigates to the next/previous month when using arrow keys to move past the last/first day of a row. The expected behavior is to move to the next/previous row within the current month.