9 Open Issues Need Help Last updated: Jul 29, 2025

Open Issues Need Help

View All on GitHub

AI Summary: Fix the editor terminal's wrapping behavior. The terminal should only wrap text when necessary, such as on smaller mobile screens; it should not wrap on larger screens where sufficient horizontal space is available. This requires adjusting the editor's sizing logic to dynamically handle different screen sizes.

Complexity: 4/5
bug help wanted good first issue
Custom README for docs about 1 month ago

AI Summary: Create a custom README.md file for the documentation site (/docs/README.md) that explains the site's purpose, tech stack, contribution guidelines (using JSDoc for documentation generation), project development details (source code location, build scripts, VS Code configuration), and links back to the GitHub page. The README should not reuse the main project's README.

Complexity: 3/5
documentation enhancement help wanted
Docs | Project Section about 1 month ago

AI Summary: Document the project structure, build and serve scripts, VS Code configuration, JSDoc commenting style, and contribute to the project's documentation by submitting pull requests for both documentation and code changes. The documentation should explain how to use the provided example of a JSDoc-commented function.

Complexity: 3/5
documentation enhancement good first issue
Docs | Docs Section about 1 month ago

AI Summary: Update or add documentation for a JavaScript project using JSDoc. This involves editing JSDoc comments within the source code, running a build command to generate documentation, and ensuring the documentation is accurate and complete. The project uses a `jsdoc.json` configuration file and provides an example of proper JSDoc comment formatting.

Complexity: 2/5
documentation enhancement good first issue
Docs | Main Section about 1 month ago

AI Summary: Create a separate README.md file for the /docs directory, distinct from the main project's README. This new README should provide an overview of the documentation site's purpose, list the technologies used, and include a link back to the GitHub page. The purpose should clarify who the documentation is for (developers, internal team, etc.).

Complexity: 2/5
documentation enhancement good first issue

AI Summary: Dynamically inject SEO meta tags (description, OG tags, Twitter tags, canonical URL) into the `/lesson` and `/course` pages using JavaScript. The tags should be tailored to the specific lesson or course content, leveraging data fetched from APIs within `main.js`.

Complexity: 4/5
enhancement help wanted good first issue

AI Summary: Add comprehensive JSDoc-style docstrings to all exported classes and their methods within the `src/js/main.js` file. Docstrings should clearly explain the purpose, parameters, return values, and provide examples where applicable.

Complexity: 3/5
documentation enhancement good first issue
bug good first issue mobile

AI Summary: Create a README file for the GitHub repository, providing a clear and concise description of the project.

Complexity: 2/5
documentation enhancement good first issue