MDX good first issues

This issue proposes adding a dedicated chapter on OpenAPI specifications to the "Backend from First Principles" repository. The author argues that OpenAPI is a crucial standard in modern API development and its absence leaves a gap in the repository's foundational coverage. The proposed chapter would cover its definition, structure, usage, and related tooling.

The README file for this project contains broken image badges, as indicated by a provided screenshot. The issue is labeled as 'documentation' and 'good first issue', suggesting a straightforward fix is needed to restore the functionality and appearance of these badges.

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".

This issue proposes to improve the documentation by including Hubble and Galexie within the existing table of data products. Currently, these are mentioned separately, making direct comparison difficult. The suggestion is to reframe the table to encompass various data products, clearly indicating their type (API or other).

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.

A user reported that an image is not displaying correctly on the solution page for the JOI - 2020 - Stray Cat problem. This issue is labeled as a bug and a good first issue, indicating it's likely a straightforward content or rendering problem.

A broken link in the 'Advanced - Persistent Data Structures' module on usaco.guide redirects to a gambling website. The issue requests the removal or update of this link to protect users. This is a straightforward content correction task.

This issue requests the addition of example schemas for the /payments endpoint. Currently, the response schema changes based on payment types, and there are no documented examples of these variations, making it difficult for developers to understand and integrate with the API.

The documentation for verifying ORAS CLI binaries is outdated and no longer aligns with the current release signing process and the KEYS file. This leads to users being unable to fully verify releases or only verifying partial information. The issue requires updating the guide across multiple versioned documentation branches.

This issue is a request to update the Stellar documentation's guide on choosing the right storage solution. The goal is to ensure the guide accurately reflects current best practices and provides clear guidance for developers based on their specific use cases.

The user is requesting a guide on how to implement SAC (Stellar Asset Contract) clawback functionality. This guide should be added to the existing token building section of the Stellar developer documentation.

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.

This issue requests the creation of a comprehensive end-to-end guide for fetching data from the Goldsky indexer and integrating it into a frontend interface. The guide should cover the fundamentals of indexers, the process of setting up data retrieval, and best practices for frontend integration and data display.

This issue proposes improving string concatenation capabilities, specifically for providing URIs for NFTs. The current alternative is using `Vec`, and the user is looking for a more direct string concatenation method.

The user is requesting the creation of an 'Asset Directory' to help developers easily find information about Tier 1 assets, such as their public keys for establishing trustlines. This directory would centralize crucial developer-facing information that is currently difficult to discover, as exemplified by the user's experience finding USDC on Testnet.

A user has reported that a problem explanation is missing from the "Ad Hoc Problems" section of the USACO Bronze module. This appears to be a content issue where a specific problem's explanation is absent, requiring a content update.

This issue requests documentation for how to create non-upgradeable (immutable) smart contracts on Soroban. Currently, all contracts are upgradeable by default, which conflicts with the desire for permissionless, 'code is law' contracts where the developer has no special privileges after deployment. The user believes there's a way to disable upgradeability but lacks documentation.

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 discusses a common pitfall in Soroban smart contracts where using built-in `Vec` and `Map` types to store unbounded collections within a single contract data entry leads to scalability problems and potential contract lock-ups. The proposed solution is to store each collection item as a separate contract data entry to avoid ledger entry size limits and transaction serialization bottlenecks.

This issue proposes to enhance documentation by referencing existing CDP-based hackathon projects as case studies for the ingest library. The goal is to showcase the library's capabilities through these real-world examples, potentially linking to their repositories with minimal framing or more in-depth write-ups if feasible.

This issue requests documentation clarifying how operations within a transaction can use a different source account than the parent transaction envelope. It aims to explain default source account overrides and provide code examples, particularly for new users to prevent confusion with `set ops` functions and understand key custody implications.

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 proposes replacing plain text descriptions of account balances in the Stellar documentation with visual representations. The goal is to make the examples easier to understand by drawing code blocks that visually depict each account's holdings.

This issue points out a missing piece of information in the Stellar developer documentation regarding automatic quorum set generation. Specifically, the `QUALITY="CRITICAL"` setting is not mentioned on the provided configuration page, which could lead to confusion for administrators.

This issue proposes adding a Frequently Asked Questions (FAQ) document for Horizon node operators to the official documentation. The goal is to empower operators to self-serve and resolve common node issues without needing direct support.

This issue requests a refresh of several "classic" How-To Guides and the Channel Accounts section on the Stellar developers documentation. The primary goal is to ensure that the examples provided within these encyclopedia entries are up-to-date and functional, addressing potential outdated code or concepts.

This issue reports inaccuracies in the solution explanation for the "CF - Max Median" problem. Specifically, the explanation is not quite accurate, as indicated by a forum discussion, and contains an out-of-bounds error on line 33. There's also a minor inconsistency in the use of comparison operators.

This issue proposes adding a dedicated documentation page for the ORAS .NET SDK to the client libraries section of the ORAS website. Currently, .NET is only partially represented with an off-site link and a feature checklist, but lacks its own dedicated page like Go, Python, Rust, and Java. The fix involves creating a new `.mdx` file for .NET, mirroring the structure of the existing Java documentation page.

A user is requesting a solution for the 'Robot Path' problem, which they believe is missing from the Platinum - Range Queries with Sweep Line module on usaco.guide. They have provided a link to the module and explicitly stated their need for a solution.

This issue requires updating a single stale screenshot on the Sentry product onboarding documentation page. The task involves comparing the existing screenshot with the current Sentry UI, recapturing it if necessary, and replacing the old image file while ensuring the alt text remains accurate. This is a straightforward content update task.