Astro good first issues

This feature request aims to update the website's sitemap to include a "Sponsors" link and reorder existing links to match the website's header. The desired order is Home, Blog, Members, About, and Sponsors.

This bug report indicates that social preview images (ogImages) are not being generated correctly for all blog entries. While the images are present in the `dist` directory, they fail to display when shared in chat applications. The issue seems to stem from the social preview image and the HTML being generated in separate folders.

The issue describes a bug where generated social preview images (ogImages) are not displayed when sharing blog post links on platforms like Telegram and WhatsApp. While the images are present in the `dist` directory, they fail to render in social previews, and there's a related problem with ogImages not being generated for all blog entries.

This issue requires fixing the color inversion of a secondary button when displayed on a dark background. In its default state, the button's text and border should be white. Upon hovering, the colors should invert to a white background with dark text.

This issue proposes creating runnable Jupyter Notebooks for each chapter of the deepagents-in-action repository, building upon previous discussions. The goal is to provide readers with step-by-step execution, intermediate state viewing, and preserved results, with a clear directory structure and detailed requirements for each notebook's content and submission.

This issue discusses the future maintenance of a repository, suggesting it's unlikely to be actively maintained. The author offers to fork and maintain it but believes an existing fork might already be doing so. Significant changes in Astro's major version updates would require a substantial rewrite, potentially leading to simplified animations in any forked version.

The customer logo rows on the financial services and retail use-case pages are left-aligned instead of centered. This is due to the current grid layout not properly distributing the logos. The fix involves replacing the grid with a centered flexbox layout, similar to a previous fix for the automotive page.

This issue proposes translating the INFO.md file from Russian to English. The goal is to standardize the documentation to a single language and improve accessibility for a wider audience, as it's considered a general improvement for forks of CV Hub.

The documentation for Kestra's Docker Task Runner example uses the deprecated `centos` container image. This image is no longer maintained and poses a security risk. The suggested fix is to replace it with a current, maintained image like `ubuntu`, `debian:bookworm-slim`, or `alpine` in multiple documentation files.

The Kestra documentation on concurrency does not explicitly state whether a paused execution holds its concurrency slot. This issue confirms that a paused execution does indeed hold its slot, preventing subsequent executions from starting until the paused one is resumed and completes. This behavior is crucial for understanding common workflow designs involving pause gates.

This issue proposes the creation of a new "General Guides" page on the website. This page will serve as a central hub for users to browse all available guides, with initial content including a "Gitguide" and plans for future additions like an "SSH guide" and "python uv guide." The suggested design involves a grid layout with individual cards for each guide, providing a brief description.

The "Quickstart →" button on the Kestra documentation homepage incorrectly links to a non-existent anchor `#start-kestra` on the quickstart page. This causes users to land at the top of the page instead of the intended starting step. The issue suggests either updating the link's target or adding a stable `start-kestra` ID to the relevant heading.

An Ansible example in the Kestra documentation contains invalid YAML due to incorrect indentation of the `---` document separator. This causes the playbook content to be parsed separately, leading to validation errors when users try to use the example. The fix involves indenting the `---` and removing an extraneous blank line.

This issue reports multiple typos and copy errors found across various pages of the Kestra website, including duplicated words, misspelled words, and missing spaces. The reporter provides specific URLs and text examples for each error, making them easy to locate and fix.

This is a long-term collaborative issue to supplement and optimize AgentSeek templates for the 'Deep Agents in Action' course. Contributions can include adding new templates for uncovered scenarios, improving existing ones, fixing framework upgrade issues, adding tests, and ensuring content accuracy. The issue prioritizes chapters 6, 8, 9, and 11, which require specific agent capabilities.

The Podman Compose guide for macOS fails because SELinux in the Podman machine VM prevents containers from accessing the docker.sock and creating subdirectories. The proposed fix involves adding `security_opt: - label=disable` to the docker-compose.yml file to run the container unconfined, resolving these permission issues.

The Kubernetes installation documentation for Kestra's Enterprise Edition incorrectly instructs users to use `docker login` to pull the `kestra-ee` image. This command does not provide credentials to the Kubernetes cluster, which is necessary for pods to pull the image. The documentation should instead guide users to create a Kubernetes `docker-registry` secret and configure the Helm chart's `imagePullSecrets`.

The user is reporting that when navigating through paginated blog or portfolio pages, the focus shifts to the top of the page after selecting a new page. They are asking if this is an accessibility issue and if the focus should automatically return to the blog section.

The top navigation bar on the website lacks sufficient contrast with the content behind it, making text difficult to read. This issue proposes applying a CSS `backdrop-filter` with a blur effect to improve contrast and legibility, as demonstrated in the provided before and after images.

This issue aims to improve the developer experience (DX) for the Prettier setup by addressing several minor follow-up items. These include recommending VS Code extensions, aligning editor configuration with Prettier's line length, restoring specific comment formatting in the README, and potentially removing redundant Prettier configurations for Astro files. The goal is to reduce friction for new contributors without impacting the build.

This issue proposes to consolidate the Node.js version definition into a single `.nvmrc` file. This will ensure consistency across the project, preventing drift between `package.json` and CI/deployment configurations. The change also includes updating documentation to guide local contributors on how to use version managers.

This issue proposes updating the copyright year displayed on the website to dynamically reflect the current year. The goal is to avoid manual updates and use a simple JavaScript solution instead of static Astro, which would require a rebuild.

This issue proposes adding community health files to the repository to improve the contribution process. It includes creating issue templates for bug reports and feature requests, a pull request template, and a CONTRIBUTING.md file to guide developers on how to contribute.

This issue addresses a file size limit for job application submissions, currently causing CORS and 413 errors due to a 10MB proxy limit. The proposed solution is to limit uploads to 8MB and potentially downsample larger files, even though the backend already performs this action.