Astro good first issues

This issue proposes a "good first lab" for DevSecOps and Agents, focusing on npm lifecycle scripts like `preinstall` and `postinstall`. The lab will demonstrate how these scripts execute automatically during installation and how the `--ignore-scripts` flag prevents this, highlighting the security implications of running arbitrary code. It builds upon a previous lab about agent configuration persistence.

This issue proposes a new "good first lab" for the "Practical Cybersecurity" path, focusing on HTTP security headers. The lab will teach about headers like Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, and X-Frame-Options, demonstrating their defensive capabilities against XSS attacks using a local toy server and `curl` commands. The expected outcome includes before-and-after header comparisons and a mitigation table.

This is a "good first issue" lab focused on backend architecture, specifically demonstrating that CORS (Cross-Origin Resource Sharing) is a browser security policy and not a server-side authentication mechanism. The lab will use a toy server and `curl` commands to show how clients other than browsers ignore CORS, and that `Access-Control-Allow-Origin` only controls browser access, not actual server authorization which relies on tokens or sessions.

This issue proposes a new "good first lab" for Linux users focusing on environment variables and the PATH. It aims to teach why commands might not be found, how the shell resolves commands using PATH, and the difference between shell and exported variables. The lab will involve practical exercises with a toy script and a discussion on the security risks of including the current directory in PATH.

This issue proposes a "good first lab" for the "Networks and Internet" path, focusing on understanding network ports. The lab will teach how to identify which process is listening on a port and how to connect to it using local commands like `ss` and `curl`. It also aims to explain the difference between binding a service to 127.0.0.1 versus 0.0.0.0.

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.

Links within the 'Event schedule' section of the Hacktoberfest landing page have poor color contrast against their dark background, making them difficult to read. The issue stems from the styling of links rendered within dynamically generated HTML content in `Schedule.astro`. A suggested fix involves applying global link styling to ensure visibility and accessibility.

This issue requests adding speaker eligibility criteria to the "Adding yourself as speaker" documentation. The goal is to clarify who can be listed on the Speakers page, preventing unqualified submissions and providing reviewers with clear guidelines. The criteria include identifying as a woman based in Singapore, having spoken at a WomenDevsSG event, and optionally linking to other conference talks.

This is a feature request to enhance the blog preview layout by displaying the author's name instead of the publication time. This change aims to give more recognition to blog contributors.

The `astro-icon` package is generating a build warning because the default `src/icons` directory is missing. This warning appears during development and build processes, adding unnecessary noise to the console. The issue suggests several straightforward solutions, such as tracking the directory with a placeholder file or reconfiguring `astro-icon` if local icons are not required.

On the public-services and software-providers use-case pages of kestra.io, the last customer logo in the logo strip is misaligned on mobile devices. It appears in the left column of the final row, making the section look unbalanced instead of centered.

When the search overlay is opened on kestra.io, the right-side scrollbar gutter incorrectly displays as a solid black bar. This visual glitch appears to be related to how the scrollbar is handled when page scrolling is locked by the overlay. The issue is reproducible by simply opening and closing the search feature.

This issue requests an update to the documentation for adding new members. Specifically, it asks to include the `volunteer` property in the "Adding yourself as a new member" guide, as this property is already in use for volunteer member profiles but not explained in the guide. The proposed changes involve adding a description of the `volunteer` property to the member profile table and including it in the sample profile.

This issue is an open invitation for WomenDevsSG community members to contribute blog posts about their experiences, technical insights, or learning journeys. Contributors should create a new Markdown file in the specified directory, following formatting guidelines and including specific frontmatter details. The goal is to foster knowledge sharing and inspiration within the community.

This issue invites community members to add their profiles to the WomenDevsSG website's Members section. Contributors need to create a Markdown file with their name, bio, and GitHub link, following provided guidelines and membership criteria. This is presented as an excellent first contribution opportunity.

The Council of Europe logo on the public services use-case page is nearly invisible due to a dark logo on a dark background. This contrasts with other logos in the same strip which are clearly visible. The issue also notes that the logos in this row are of varying sizes.

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.

The blueprint card on the Kestra homepage is displaying with asymmetrical heights, creating a visual inconsistency. This issue is labeled as a 'quick-win' and a 'good first issue', suggesting a straightforward frontend fix is needed to align the card heights.

On Kestra's industry use-case pages, cards within sections like "Infrastructure & Platform Orchestration" visually indicate clickability through hover effects (lifting, shadow, blue border) but lack actual links. This leads to user confusion as clicking them results in no action. The issue suggests either adding the intended links or removing the hover effects to prevent misleading users.

The second row of customer logos on the Kestra retail use-case page is left-aligned instead of centered, creating an unbalanced appearance. Additionally, the Leroy Merlin logo in the top row is too dark to be clearly visible against the background.

The AI tools documentation page incorrectly states there are over 1,400 plugins, when the actual number has surpassed 2,000. The proposed fix is to update the page to dynamically display the plugin count using a component similar to the main index page, while acknowledging potential UI and search indexing issues.

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.

The documentation for Kestra's webhook trigger incorrectly states that it has built-in HMAC signature validation. In reality, the core webhook trigger does not perform this validation, and the only security mechanism is a shared secret embedded in the URL. This misleading information was reported by a customer and needs to be corrected in the best practices documentation.

The financial services use-case page on kestra.io has a logo strip where the second row of logos (Matmut and Gate.io) is left-aligned instead of centered, creating an unbalanced appearance. Additionally, the iCapital logo in the top row is oversized and has an unwanted gray background box.

This issue aims to implement proper logos for several high-value applications. Currently, all apps display the GitHub owner's avatar due to a missing `logoUrl` record. The proposed solution involves collecting and approving logo candidates from various sources, storing them locally, and updating the `logoUrl` to point to these new assets.

This issue identifies multiple broken external links within the Kestra documentation, primarily due to 404 errors or DNS failures. The reporter has provided a detailed list of affected documentation pages and the specific broken URLs, suggesting they should be updated or removed to maintain documentation integrity.

The pricing page on kestra.io has a significant empty space above the feature comparison table's column headers. This visual gap appears to be a layout bug and detracts from the user experience. The issue is reproducible by simply navigating to the pricing page and scrolling to the relevant section.

This issue addresses a problem where KPI values and labels are concatenated incorrectly in Markdown rendered by AI agents due to how adjacent inline spans are processed. The fix involves refactoring the `Quotes.vue` component to use a description list (`<dl>`) structure for KPIs, ensuring proper separation and semantic correctness.

The partner cards on the Kestra website have inconsistent link labels. While most links say "Visit [name] website" with an external link icon, a few, like Conapi, Ntico, and Ashisuto, incorrectly say "Visit [name] page" and lack the external link icon. The goal is to standardize all these link labels to "Visit [name] website".

This issue reports two invalid YAML examples on the LogShipper documentation page. The Splunk example has incorrect indentation for the `tasks` key, and the Graylog example has a leading space before the `id` key. Both issues cause parse errors and need to be corrected to ensure users can successfully copy and paste the examples.