Typst good first issues

The user is requesting support for Asciidoctor-style callout syntax within code blocks. This would involve embedding callout numbers directly in the code and then providing explanations for each callout below the block, similar to how Asciidoctor handles it.

The author is considering migrating their projects away from GitHub and is seeking community input on two primary alternatives: Codeberg and Tangled. They detail the pros and cons of each, with a personal leaning towards Tangled due to its federation and stacked PR support, despite its venture capital backing.

This feature request aims to modify Typst's default bibliography behavior. Currently, the `#bibliography` function inserts references at the call site, which conflicts with the template's sidebar layout. The desired outcome is for bibliographies to be automatically placed within the sidebar, and the project is open to community contributions via Pull Requests.

The user, a teacher, needs line numbers in their code examples to be more visually distinct from the code itself, especially when printed in black and white. They propose adding a configurable background color to the line numbers to improve readability and distinguish them from the actual code.

This issue is a placeholder to track and address outdated documentation. Contributors are encouraged to identify and fix any inaccuracies or missing information within the project's documentation.

The user encountered an issue where a default gray color (#F3F2F0) was indistinguishable from white on their screen, leading to unexpected rendering. They suggest changing the default to a named, safe color like `color.silver` for better cross-machine consistency and visibility.

This issue requests the addition of a new language to the project's message catalog. The task involves translating existing message keys into a new language, registering it as a supported language, and adding corresponding tests and documentation updates. This is considered a straightforward task suitable for a first-time contributor.

A Typst user is encountering a panic error when compiling a report with Hydra in version 0.15.0, which did not occur in version 0.14.2. The error stems from the `get-top-margin()` function in Hydra, which fails when only horizontal margins are specified, as it expects either a `top` or `y` key in the margin dictionary.

This issue proposes adding a "speaker notes" feature to typslides, similar to Google Slides. This would allow presenters to view notes in a separate window during a presentation, which are not visible to the audience. The proposed solution suggests adopting an API similar to Touying's `speaker-note` and leveraging tools like `pympress` for display.

The task is to expand the Elembic library for Typst by adding more example implementations of custom elements. This includes creating examples for common elements like subtitles and bold text, and potentially packaging these examples into a readily importable library for easier user adoption. The goal is to lower the barrier to entry for new users by providing more concrete, simple examples.

Update the fletcher package's manual to include a section explaining how the package interacts with equations and their alignment points, using the provided example as a starting point. The documentation should clarify how to use fletcher's features within mathematical expressions and leverage alignment points for precise diagram placement.

Enhance the Typst glossarium package to allow users to specify custom capitalized versions of glossary terms, particularly for terms with content (e.g., mathematical expressions) as short forms. This involves adding functionality to handle custom capitalization alongside existing pluralization options, potentially allowing for three manual overrides per field (plural, capitalized, capitalized and plural). The implementation should gracefully handle cases where custom capitalization is not provided, falling back to existing logic.