MDX good first issues

This issue requests updates to the ORAS CLI documentation for version 1.3.5. It involves changing version numbers in the installation and binary verification guides, and updating a configuration map to ensure the command reference is built from the latest patch release.

This issue addresses incorrect Go vanity import paths for the oras-go project. The `go-source` meta tags in the v1 and v2 vanity pages were incorrectly pointing to the `main` branch, which now contains v3 code. The fix involves updating these meta tags to point to the correct `v1` and `v2` branches respectively, and removing an unused v3 page.

The installation documentation generates incorrect download URLs for ARM64 Linux users, leading them to download non-existent artifacts. This is due to `uname -m` output not being normalized to Go architecture names and some platform-specific sections hard-coding architectures instead of detecting them. The suggested fix involves updating the `sed` command to normalize architecture names and adding `-f` to `curl` for clearer error reporting.

This issue requests a blog post to announce the release of oras-go v3.0.0. The post should follow a previous announcement's pattern, highlighting new features, breaking changes, migration details, and support status, while linking to external documentation for API specifics.

This issue proposes to update the Go client library documentation page by replacing the existing content with direct links to the oras-go v2 and v3 documentation. This change aims to keep the documentation synchronized with the library's code and reduce maintenance overhead for the website.

A horizontal rule is unexpectedly appearing at the bottom of the side navigation on the p5.js website, specifically when the split side navigation is enabled. This visual artifact is present on both the main and 2.0 branches and is intended to be removed as part of an ongoing CSS audit.

This issue reports a visual bug where the left and right margins of the main content area on the p5.js website are inconsistently set to 32px instead of the intended 40px, which should match the column gutter width. This discrepancy is observed on both the main and 2.0 branches and affects various pages, including the Reference page. The fix is part of an ongoing CSS audit.

A discrepancy exists in a tutorial where a comment states 'draw two trees' but the accompanying code actually draws three. This issue requires correcting the comment to accurately reflect the functionality of the `trees()` function.

A user has submitted a contact form requesting an explanation for the "Circular Barn" problem (ID: usaco-618). The issue indicates that the current explanation is unclear and requires improvement. This is likely a request for better documentation or a more detailed walkthrough of the problem's solution.

This issue requests the creation of more practical code examples (cookbooks) for the `AssembledTransaction` feature in the JS SDK. The goal is to improve developer onboarding by providing readily usable code snippets, similar to existing JS documentation, and integrating them into the 'Working with contract specs' guide.

The user is requesting comprehensive documentation to help Solana developers transition to building Stellar contracts. They encountered dependency issues when trying to integrate Solana and Stellar, highlighting a need for clear guidance on this migration path.

This issue requires updating outdated links within the project's README file and the pull request template. Specifically, the website URL and branch references need to be changed to reflect the current official documentation and main branch.

This issue requests the removal of a specific, outdated step from the GitHub Actions `testing.yml` workflow. The step pertains to restoring a legacy Docusaurus build cache, which is no longer relevant as the project now uses Astro. The task involves deleting this cache retrieval step while preserving other existing cache configurations.

This issue requires updating a configuration file (`lunaria.config.json`) to reflect the repository's current default branch name. The current configuration incorrectly points to 'master', leading to broken GitHub links in the translation dashboard. The fix involves changing this setting and then verifying the updated links.

This issue requires updating the `.github/CODEOWNERS` file to reflect the current directory structure for Russian and Korean documentation. The old paths `/i18n/ru/` and `/i18n/kr/` need to be changed to `/src/content/docs/ru/` and `/src/content/docs/kr/` respectively, ensuring that code owners are correctly assigned for pull requests affecting these documents.

This GitHub issue serves as a backlog for documentation contributions, outlining specific tasks related to updating and improving the Rive editor documentation. It provides a key for understanding task status and priority, and encourages contributors to comment before starting work to avoid duplication and ensure proper scoping.

This issue proposes adding type checking for Astro components to the project's Continuous Integration (CI) pipeline. Currently, CI only performs build and lint checks, missing potential type errors in Astro files. The task involves integrating `astro check` into the scripts and CI, fixing any reported type errors, and adjusting configurations if necessary.

This issue proposes to improve code quality by enabling ESLint to lint `.astro` and `.mjs` files. Currently, these file types are not included in the linting process, leading to undetected rule violations. The suggested solution involves configuring `eslint-plugin-astro` and updating the lint command.

The robots.txt file incorrectly points to an old sitemap URL that now results in a 404 error. This prevents search engines from accessing the sitemap. The issue requires updating the sitemap URL in the robots.txt file to the correct, working URL to ensure proper sitemap fetching.

The documentation example for `sendDefaultPii` in Sentry's JavaScript SDK incorrectly shows `httpHeaders` as a flat object. The actual TypeScript type expects a nested object for `request` and `response` directions. This leads to a TypeScript error for users following the example.

This issue reports that the Kyverno platform-specific notes for Argo CD are incomplete and outdated. Specifically, the documentation fails to include a recommended Helm value in an example, contains outdated information about Argo CD's resource tracking mechanism, and lacks clarity on required annotations. The issue also points out a potential conflict with the Kyverno Helm chart's structure regarding a specific Helm value.

This issue reports a typo in the USACO Gold Divisibility module, specifically within the explanation of Euler's Totient function. The formula presented has an incorrect variable in the last term, which should be (pk - 1) instead of (qk - 1). This is a straightforward content correction.

This issue requests the addition of a "Wasm Runtime" section to the postrenderer plugin tutorial documentation. The new section should detail the steps for setting up a Wasm runtime for a postrenderer plugin, including repository setup, plugin configuration, Go code implementation, building the Wasm module, and testing with Helm.

This issue addresses a visual bug where removing `margin-bottom` from the `.list-unstyled` class in a previous update has negatively impacted the display of certain examples. The fix involves re-evaluating and potentially adjusting the styling of examples that rely on this class to ensure proper rendering across components, starting with Tags.

This issue reports a minor typo on the Processing reference page for `frameCount`. The word "number" is misspelled as "number o" in the description. The suggested correction is to change it to "number of frames".

A user is reporting that the p5.js mobile device movement example sketch is not functioning as expected on their iPhone. The sketch is supposed to react to device motion, but it appears to be static or unresponsive, contrary to its intended behavior.

This issue requests the documentation of several functions that are currently missing from the Helm chart template guide. The missing functions include `fromToml`, `mustToYaml`, `mustChunk`, `bcrypt`, and `tuple`, with specific instructions on where and how to document each.

The framebuffer example in p5.js version 2+ exhibits unexpected visual artifacts, displaying crescent shapes instead of rotating spheres. This issue also affects the p5.js editor, with version 2.3 showing strange behavior and a lack of syntax highlighting in versions 2.2 and above.

This issue reports a visual bug on the p5.js website where the "Jump to" links are misaligned on mobile devices. The misalignment is caused by unnecessary top margins applied to some of these links. The expected behavior is for these links to be neatly aligned.

This issue requests the addition of API documentation for the `router(req, res, [next])` function. The user cannot find this function documented and suggests it be added to the Express.js API documentation for both v4 and v5.