Open Issues Need Help
View All on GitHubAI Summary: This issue proposes refactoring the `scri.be` website footer. The goal is to eliminate its sub-components and combine them into a single component, mirroring a similar refactor recently completed in the `activist-org/activist` project, specifically referencing PR #1914 as a guide.
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
Scribe's community portal scri.be
AI Summary: This GitHub issue proposes creating a dedicated documentation page to centralize all links to blog posts and online media about Scribe. Currently, these links are spread across various project READMEs, making them excessively long. The new page would allow READMEs to simply link to this single, comprehensive resource, though its implementation is blocked until the overall documentation structure is defined in issue #11.
Scribe's community portal scri.be
Scribe's community portal scri.be
AI Summary: The task involves adding icons to all documentation pages on the Scribe community portal (scri.be). This includes creating icons for each page (except the application landing pages, which will use existing images) and implementing a consistent `PageDocs` component to display these icons. The contributor is willing to create the icons, and needs help with the implementation of the component.
Scribe's community portal scri.be
AI Summary: Fix the rendering of text and chevrons in the collapsed sidebar of the scri.be website. The task involves modifying the `SidebarLeftContent.vue` component to prevent the display of dropdown text and chevrons when the sidebar is collapsed, and potentially aligning the docs book icon with other dropdown icons within sub-components.
Scribe's community portal scri.be
AI Summary: The task involves reviewing and merging a pull request that fixes TypeScript path aliases (@/* and ~/*) in a Nuxt.js project's tsconfig.json file. The fix ensures correct path resolution for TypeScript compilation and IDE autocompletion across different environments (local development, Docker, CI).
Scribe's community portal scri.be
AI Summary: Investigate various documentation services (Docus, Nuxt Content, VuePress, VitePress) to determine the best fit for scri.be's documentation. The chosen service will then be implemented to create base documentation pages for the project. Collaboration with the community is encouraged.
Scribe's community portal scri.be
AI Summary: The task involves adding Hindi localization to the scri.be website by creating an `hi.json` file containing Hindi translations of strings from the existing `en-US.json` file. This will initiate the internationalization process for the Hindi language.
Scribe's community portal scri.be
AI Summary: The task involves adding Nepali language support to the scri.be website by creating a new `ne.json` file containing Nepali translations for existing English strings. This will initiate the internationalization process for Nepali. The project uses Nuxt.js, Vue.js, and a structured i18n system.
Scribe's community portal scri.be
AI Summary: The task involves adding Telugu language support to the scri.be website by creating a `te.json` file containing Telugu translations of existing English strings. This will initiate the internationalization process for Telugu. The existing English strings are located in `frontend/i18n/en-US.json` and the new file should be placed in the `frontend/i18n` directory.
Scribe's community portal scri.be
AI Summary: The task involves adding Malayalam language support to the scri.be website by creating an `ml.json` file containing translations of strings from the existing `en-US.json` file. This will initiate the internationalization process for Malayalam.
Scribe's community portal scri.be
AI Summary: The task involves adding Tamil language support to the scri.be website by creating a `ta.json` file containing Tamil translations for existing English strings. This will initiate the internationalization process for Tamil. The existing English strings are located in `frontend/i18n/en-US.json`, and the new file should be placed in the `frontend/i18n` directory.
Scribe's community portal scri.be