SCSS good first issues

This issue requests a Spanish translation for the term 'continuous random variable' and its accompanying definition. The provided definition describes a random variable that can take any real number value, whether bounded or unbounded, with examples like age or distance.

The timepicker component's disabled state is not visually consistent with other disabled components in the application. This issue requires styling adjustments to ensure a uniform disabled appearance across all UI elements.

This issue requests an upgrade of the project's Go version to 1.27.1. The task involves updating the Go directive in go.mod, modifying build configurations in CI/CD pipelines and Dockerfiles, and ensuring all tests pass after the update.

This issue proposes expanding the documentation to include information on installing Scala and sbt using package managers other than SDKMAN, such as Homebrew on macOS. The goal is to provide users with alternative installation methods that they might already be familiar with.

This issue proposes creating an automated workflow for GitHub issues. When an issue is marked as 'done', the workflow will check if the 'Time Spent (h)' field is empty. If it is, the workflow will copy the value from the 'Hours' estimation field into 'Time Spent (h)'. This aims to improve tracking of development speed for burndown charts and statistics.

This issue requests that the 'Legend' component be moved to its own dedicated documentation page within Storybook. Currently, its documentation is not properly organized, and it needs to be treated as a distinct component as per Figma specifications.

This issue proposes adding an example to the Tabs documentation page that demonstrates how to use icons within page tabs. This could be implemented as a new control or a dedicated story within the existing documentation.

This issue tracks the documentation status of various API and webhook changes introduced in Mastodon versions 4.0.0, 4.1.0, and 4.2.0. It lists specific features and their corresponding pull requests, with checkboxes indicating whether the documentation has been updated.

This issue proposes automating cross-browser testing for the project. The author suggests exploring platforms like CrossBrowserTesting or BrowserStack to achieve this. It's an enhancement request seeking community help to implement this functionality.

The user wants header elements in posts to be clickable, similar to how links to specific sections on GitHub documentation work. They've identified a potential solution using Kramdown's 'header_links' option, but it's not functioning as expected.

The user is experiencing invisible or black backgrounds in GTK4 applications when using the Rose Pine theme on Arch Linux with X11 and picom. This issue appears to be related to how the GTK4 theme interacts with the compositor, as removing picom results in black backgrounds instead of invisible ones.

This issue requests the removal of Bootstrap 4, which has reached its end-of-life. The goal is to transition to a newer version while maintaining compatibility with both Bootstrap 5 and the future Bootstrap 6, similar to the current support for Bootstrap 4 and 5.

The user is reporting a CSS conflict between `djangocms-admin-style` and Django's built-in `autocomplete_fields` in the admin interface. When `djangocms-admin-style` is active, the autocomplete fields appear visually broken, whereas they display correctly when the styling is disabled.

This issue identifies that font files within the djangocms-admin-style project are missing proper attribution and licensing information. The fonts appear to be derived from Font Awesome 4.4.0, which requires shipping the original copyright and license terms under the OFL-1.1 license. The project needs to be updated to comply with these licensing requirements.

This issue reports that collapsible fieldsets in the Django CMS admin interface are not being styled correctly when using Django 5 and Django CMS 5. The user expects the styling to match the behavior seen in CMS v3, where these elements were properly presented. The problem appears to be a visual regression or a compatibility issue with the latest Django and CMS versions.

The 'Trusted by Business' section on the website is currently static and lacks scroll animations. Additionally, there's an overlapping issue where posts are not positioned correctly. The desired behavior is to implement animations for posts appearing on scroll, either by stacking them or animating them from the bottom.

This issue proposes optimizing image loading on the Kanvas website by converting Markdown-rendered PNG and JPEG images to WebP format at build time. This will be achieved by leveraging Hugo's asset pipeline and implementing an image render hook to generate responsive `<picture>` tags with WebP sources and original fallbacks, thereby reducing page load times and bandwidth usage.

This issue proposes synchronizing pre-commit checks across projects, specifically by adopting the Ruff linter and formatter from django-cms. The core task involves updating configuration files (`.pre-commit-config.yml` and `pyproject.toml`) to match django-cms's setup, migrating `exclude` and `ignore` directives to `extend-ignore` and `extend-exclude`, and addressing failing checks by creating a `# TODO fix separately` block.

The Django admin interface has a visual bug where long label text overlaps with readonly field values. This is due to a CSS conflict where the label's width is set to 'auto!important' instead of the expected '160px', causing the readonly field's left margin to misalign.

The user is reporting a visual bug where the help text for checkboxes in the djangocms-admin-style is not aligned or spaced correctly. They have provided screenshots illustrating the expected and actual appearance of the help text.

This issue requires updating the GraphQL documentation to reflect the addition of new `contains` and `startsWith` directives. The update should include examples of how to use these directives in queries, similar to the provided example.

This issue proposes adding a curated list of external GraphQL learning resources to the documentation. The goal is to help users new to GraphQL understand how to use GUAC's GraphQL playground effectively. No new content needs to be written, only links to existing, high-quality resources.

This issue requests documentation for selectively importing CSS components to reduce bundle size. It highlights the importance of import order and asks for a list of CSS component entry files in the correct sequence to ensure consistent styling when individual components are imported.

The user is requesting the addition of a dark theme to the project. They specifically suggest using the `@prefers-color-scheme` CSS media query, providing a link to MDN documentation for guidance. This indicates a desire for the application to adapt its appearance based on the user's operating system or browser's color scheme preference.

This issue proposes relocating a niche procedure concerning DHCP integration from its current placement to a more relevant section within the "Integrating Provisioning Infrastructure Services" guide. The author questions the current timing of this step, suggesting it might be premature as users haven't yet installed the server.

This issue proposes adding a specific note to the Bare_Metal.adocs documentation. The note clarifies that PXE workflows can also provision virtual machines outside of the project's direct control, as suggested in a previous PR.

This feature request aims to enhance the USWDS documentation site by showcasing all possible states and options for form controls. The goal is to provide clear examples of form controls with hints, error states, or both, to improve accessibility and ensure correct programmatic associations, as teams often struggle to find this information.

This issue proposes creating a structured online course for the PlanB Network's education platform, similar to a previous "Learning Bootcamp" project. The scope can range from basic written content with videos to more interactive formats including tasks, challenges, and scheduled online classes. The initial suggestion is to start with a basic, self-guided introductory course to gauge platform usage and user feedback.

This issue proposes adding an automated behavioral test for the built JavaScript bundle of USWDS. This test is crucial for ensuring the integrity of the JS bundle, especially before a planned bundler replacement, as current CI processes do not verify its runtime behavior.

This issue aims to improve ESLint configuration to better detect mistakes when converting between CommonJS and ES Modules (ESM) in the USWDS project. It proposes restructuring the ESLint configuration to apply specific rules to ESM files, such as catching incorrect named imports from CommonJS modules and preventing import cycles.