Fix: "Submit Your Idea" button on /ideas page not opening email compose properly#661
Closed
Aarya-Chaudhari wants to merge 1 commit intoAOSSIE-Org:mainfrom
Closed
Fix: "Submit Your Idea" button on /ideas page not opening email compose properly#661Aarya-Chaudhari wants to merge 1 commit intoAOSSIE-Org:mainfrom
Aarya-Chaudhari wants to merge 1 commit intoAOSSIE-Org:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughReplaced the internal mailto Link component with an external anchor element that opens a Gmail compose URL in a new tab, complete with prefilled recipient, subject, and body fields. Styling remains unchanged. This addresses the non-functional mailto link behavior. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Author
|
Hello @Zahnentferner |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/helper/projects.js (1)
9-338:⚠️ Potential issue | 🟠 MajorPreserve
projectsobject contract used by the details page.This dataset is consumed by
src/app/projects/[slug]/page.jsxwhich directly rendersproduct.setupGuideand expectsproduct.feedbacks(see lines 129-182 there). If those fields were removed here, the setup/reviews sections regress for every project.Suggested fix (keep schema stable with safe defaults)
const projects = [ // ... ] -export default projects +const normalizedProjects = projects.map((project) => ({ + setupGuide: '', + feedbacks: [], + ...project, +})) + +export default normalizedProjects🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/helper/projects.js` around lines 9 - 338, The projects array entries removed fields that the details page expects (product.setupGuide and product.feedbacks), causing regressions; for every object in the projects array (the variable projects), restore those keys with safe defaults (e.g., add setupGuide: '' or null and feedbacks: [] to each project object) so the details renderer (which accesses product.setupGuide and product.feedbacks) always finds them and avoids runtime errors.
🟡 Minor comments (29)
src/app/ideas/2026/NeuroTrack/page.mdx-35-35 (1)
35-35:⚠️ Potential issue | 🟡 MinorVerify mentor role label for this idea page.
This NeuroTrack page points applicants to
@Contributor-Ellena, which looks mismatched and may direct them to the wrong mentor group.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/NeuroTrack/page.mdx` at line 35, The page currently references the role label "@Contributor-Ellena" which appears incorrect; verify the intended mentor role and replace "@Contributor-Ellena" with the correct role label (or remove the suffix) to match the project's canonical mentor roles (e.g., the existing "@Mentor" usage); also scan other idea pages for consistent role naming and update any mismatches to prevent directing applicants to the wrong Discord group.src/app/ideas/2026/NeuroTrack/page.mdx-10-10 (1)
10-10:⚠️ Potential issue | 🟡 MinorUse consistent product casing in the H1.
The heading says
Neurotrack, but the project/meta naming isNeuroTrack. Please keep this consistent.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/NeuroTrack/page.mdx` at line 10, The H1 heading currently reads "# Neurotrack" and should use the project’s canonical casing; update the top-level heading in page.mdx from "Neurotrack" to "NeuroTrack" so the H1 matches the project/meta name exactly.src/app/ideas/2026/EduAI/page.mdx-35-35 (1)
35-35:⚠️ Potential issue | 🟡 MinorFix spelling/casing in user-facing requirements and mentor text.
There are copy errors that should be corrected before publish.
Copy fix
-* There should be no backened or SaaS/Cloud dependencies. +* There should be no backend or SaaS/Cloud dependencies. ... - `@Contributor-BabyNest`, `@Contributor-NeuroTrack` in our discord servers. + `@Contributor-BabyNest`, `@Contributor-NeuroTrack` in our Discord servers.Also applies to: 42-42
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/EduAI/page.mdx` at line 35, Fix the copy errors in the user-facing requirements and mentor text by correcting "backened" to "backend" and normalizing casing of "SaaS/Cloud" to a consistent form (e.g., "SaaS/cloud" or "SaaS/Cloud" per project style). Locate the offending lines containing the sentence "There should be no backened or SaaS/Cloud dependencies." (and the identical occurrence referenced at the other instance) and update both to the corrected spelling and consistent casing so both the requirement and mentor text match.src/app/ideas/2026/Bot/page.mdx-5-5 (1)
5-5:⚠️ Potential issue | 🟡 MinorClean up repeated copy/branding typos.
This page has several user-facing text issues (
Github→GitHub,especialy→especially,generable→generalizable). Please normalize them in title/body for consistency and professionalism.Also applies to: 10-10, 14-14, 16-16, 18-18, 24-24, 35-35
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Bot/page.mdx` at line 5, The frontmatter and body contain repeated branding/typo issues—replace all instances of "Github" with "GitHub", "especialy" with "especially", and "generable" with "generalizable" across this page (including the frontmatter description field and any titles or paragraph text); update the description: 'Discord/Github Bot' to 'Discord/GitHub Bot' and search the document for the other misspellings (e.g., in headings or body text) and correct them so all user-facing strings (title, description, and content) consistently use the corrected spellings.src/app/ideas/2026/Djed/page.mdx-59-59 (1)
59-59:⚠️ Potential issue | 🟡 MinorAdd a concrete communication channel link.
“Discuss this idea in development” is ambiguous. Please include the exact Discord channel URL/ID (as done in other idea pages) so applicants know where to post.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Djed/page.mdx` at line 59, Update the sentence "Join our Discord servers (https://discord.gg/xnmAPS7zqB and https://discord.gg/fuuWX4AbJt) and discuss this idea in development." to point to the exact channel where applicants should post (replace the ambiguous "discuss this idea in development" with the concrete Discord channel invite or channel ID/URL used on other idea pages), e.g., include the specific channel invite/ID right after the server link so readers know precisely where to post.src/app/ideas/2026/Djed/page.mdx-4-4 (1)
4-4:⚠️ Potential issue | 🟡 MinorRemove leading whitespace from
meta.title.The title currently includes leading spaces (
' Djed'), which can produce inconsistent rendering in page lists/headings.Fix
- title: ' Djed', + title: 'Djed',🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Djed/page.mdx` at line 4, The meta.title frontmatter currently contains leading spaces (' Djed'); update the frontmatter value for meta.title (the title entry in page.mdx) to remove leading/trailing whitespace so it reads "Djed" (no extra spaces) to ensure consistent rendering in lists/headings.src/app/ideas/2026/UI/page.mdx-14-14 (1)
14-14:⚠️ Potential issue | 🟡 MinorFix typo in the background paragraph.
There is a typo in user-facing copy:
UI/UX pfshould beUI/UX of.Copy fix
-UI/UX is a rapidly evolving field. From time to time, we need to update the UI/UX pf some of our projects to align them with the latest trends and expectations. +UI/UX is a rapidly evolving field. From time to time, we need to update the UI/UX of some of our projects to align them with the latest trends and expectations.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/UI/page.mdx` at line 14, Replace the typo in the paragraph text where it reads "UI/UX pf" with the correct phrase "UI/UX of" in the page content (look for the string "UI/UX pf" in the UI/UX background paragraph within src/app/ideas/2026/UI/page.mdx and update it to "UI/UX of").src/app/ideas/2026/Choice/page.mdx-26-26 (1)
26-26:⚠️ Potential issue | 🟡 MinorFix typo: "alternaives" → "alternatives"
📝 Proposed fix
-Candidates are expected to refine these tasks in their GSoC proposals and clearly specify which projects they are going to handle and which approach and which alternaives they are going to use in each project. +Candidates are expected to refine these tasks in their GSoC proposals and clearly specify which projects they are going to handle and which approach and which alternatives they are going to use in each project.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Choice/page.mdx` at line 26, Replace the misspelled word "alternaives" with "alternatives" in the sentence that reads "which approach and which alternaives they are going to use in each project" within the Choice page content; edit the string in the page content (the paragraph containing that sentence) so it now reads "which approach and which alternatives they are going to use in each project".src/app/ideas/2026/DIT/page.mdx-26-26 (1)
26-26:⚠️ Potential issue | 🟡 MinorFix typo: "charcteristics" → "characteristics"
📝 Proposed fix
-can endorse that the holder of the token is indeed the entity that has those charcteristics. +can endorse that the holder of the token is indeed the entity that has those characteristics.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/DIT/page.mdx` at line 26, Fix the typo in the sentence fragment "can endorse that the holder of the token is indeed the entity that has those charcteristics." by changing "charcteristics" to the correct spelling "characteristics" so the line reads "...that has those characteristics."src/app/ideas/2026/DIT/page.mdx-21-21 (1)
21-21:⚠️ Potential issue | 🟡 MinorFix typo: "endrosing" → "endorsing"
📝 Proposed fix
-For example, when you get a passport, the government is endrosing the fact that you, +For example, when you get a passport, the government is endorsing the fact that you,🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/DIT/page.mdx` at line 21, In the sentence that currently reads "For example, when you get a passport, the government is endrosing the fact that you," replace the misspelled word "endrosing" with the correct spelling "endorsing" so the line reads "...the government is endorsing the fact that you,"; ensure only the spelling is changed and punctuation/spacing remains unchanged.src/app/ideas/2026/less-cloud/page.mdx-36-36 (1)
36-36:⚠️ Potential issue | 🟡 MinorUse official capitalization: "GitHub Pages"
📝 Proposed fix
-* In the case of Next.JS frontends, we can use client-side only and avoid server-side rendering, to generate static pages that can be deployed in github pages and that do not need to be deployed on Vercel's servers. +* In the case of Next.JS frontends, we can use client-side only and avoid server-side rendering, to generate static pages that can be deployed in GitHub Pages and that do not need to be deployed on Vercel's servers.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/less-cloud/page.mdx` at line 36, Update the phrase in the sentence starting "In the case of Next.JS frontends…" to use the official capitalization: replace "github pages" with "GitHub Pages" (keep the rest of the sentence unchanged); locate the string in page.mdx that contains "In the case of Next.JS frontends, we can use client-side only…" and correct only that token.src/app/ideas/2026/DIT/page.mdx-55-55 (1)
55-55:⚠️ Potential issue | 🟡 MinorFix typo: "teh" → "the"
📝 Proposed fix
-* Look for mentors with the roles `@Contributor-StabilityNexus` in AOSSIE's Discord and the `@TNT` and `@VouchMe` roles in the Discord of teh Stability Nexus. +* Look for mentors with the roles `@Contributor-StabilityNexus` in AOSSIE's Discord and the `@TNT` and `@VouchMe` roles in the Discord of the Stability Nexus.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/DIT/page.mdx` at line 55, Fix the typo in the sentence that mentions Discord roles: change "teh" to "the" in the line referencing AOSSIE's Discord and the Stability Nexus roles (the sentence containing "@Contributor-StabilityNexus", "@TNT" and "@VouchMe"); ensure the corrected sentence reads "the Discord of the Stability Nexus."src/components/ideas/IdeasHeader.jsx-71-78 (1)
71-78:⚠️ Potential issue | 🟡 MinorGmail-specific URL limits user choice.
While this fixes the original mailto: reliability issue, it forces all users to Gmail rather than their preferred email client. Users without Gmail accounts or who prefer other clients (Outlook, Apple Mail, etc.) will be redirected to a Gmail login page.
Consider keeping the mailto: link as a fallback or documenting this Gmail-only behavior.
Also, the indentation appears inconsistent with the rest of the file.
🔧 Proposed fix for indentation
<motion.div className="mt-8" whileHover={{ scale: 1.05 }} whileTap={{ scale: 0.95 }} > - <a - href="https://mail.google.com/mail/?view=cm&fs=1&to=aossie.oss@gmail.com&su=New%20Project%20Idea&body=Hello%20AOSSIE%20Team" - target="_blank" - rel="noopener noreferrer" - className="inline-block rounded-md border border-transparent bg-[`#00843D`] px-8 py-3 text-base font-medium text-white hover:bg-[`#006e32`] md:py-4 md:px-10 md:text-lg font-mono dark:bg-yellow-400 dark:text-black dark:hover:bg-yellow-500 transition-colors" -> - Submit Your Idea -</a> + <a + href="https://mail.google.com/mail/?view=cm&fs=1&to=aossie.oss@gmail.com&su=New%20Project%20Idea&body=Hello%20AOSSIE%20Team" + target="_blank" + rel="noopener noreferrer" + className="inline-block rounded-md border border-transparent bg-[`#00843D`] px-8 py-3 text-base font-medium text-white hover:bg-[`#006e32`] md:py-4 md:px-10 md:text-lg font-mono dark:bg-yellow-400 dark:text-black dark:hover:bg-yellow-500 transition-colors" + > + Submit Your Idea + </a> </motion.div>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/components/ideas/IdeasHeader.jsx` around lines 71 - 78, Replace the hardcoded Gmail URL in the anchor inside IdeasHeader.jsx with a mailto: link so users open their preferred email client (e.g., set href="mailto:aossie.oss@gmail.com?subject=New%20Project%20Idea&body=Hello%20AOSSIE%20Team"); keep the existing attributes (target, rel, className) and text ("Submit Your Idea") unchanged, or optionally provide both links (mailto primary, Gmail as a secondary button) if you must preserve Gmail behavior; also fix the inconsistent indentation around that <a> element to match the surrounding JSX formatting.src/app/ideas/2026/Phoenix/page.mdx-70-71 (1)
70-71:⚠️ Potential issue | 🟡 MinorTypo: "th respective" should be "the respective".
📝 Proposed fix
-and discuss this idea in th respective project channels under https://discord.com/channels/1022871757289422898/1311271241037905950 . +and discuss this idea in the respective project channels under https://discord.com/channels/1022871757289422898/1311271241037905950 .🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Phoenix/page.mdx` around lines 70 - 71, Fix the typo "th respective" to "the respective" in the sentence that invites readers to join Discord (the line containing the two Discord invite links and the channel URL in page.mdx); update the text so it reads "the respective project channels" to correct the spelling.src/app/ideas/2026/Zplit/page.mdx-3-6 (1)
3-6:⚠️ Potential issue | 🟡 MinorMeta description is inconsistent with page content.
The description states "A collaborative coding platform for learning and experimentation" but the page content describes Zplit as a "group transaction tracking solution" for splitting finances. The description should accurately reflect the project's purpose.
📝 Proposed fix
export const meta = { title: 'Zplit', - description: 'A collaborative coding platform for learning and experimentation.' + description: 'An open-source, decentralized group expense tracking and settlement app.' }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Zplit/page.mdx` around lines 3 - 6, Update the meta.description value on the exported meta object so it accurately reflects Zplit as a group transaction/expense-splitting solution rather than a coding platform; locate the exported const meta (title: 'Zplit') and change the description property to a concise phrase like "A group transaction tracking and expense-splitting solution" that matches the page content.src/app/ideas/2026/Zplit/page.mdx-17-17 (1)
17-17:⚠️ Potential issue | 🟡 MinorTypo: "you finances" should be "your finances".
📝 Proposed fix
-Zplit was ideated to solve this very issue, because keeping track of you finances and transactions shouldn't require you to make more transactions. +Zplit was ideated to solve this very issue, because keeping track of your finances and transactions shouldn't require you to make more transactions.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Zplit/page.mdx` at line 17, Fix the typo in the sentence "Zplit was ideated to solve this very issue, because keeping track of you finances and transactions shouldn't require you to make more transactions." by replacing "you finances" with "your finances" so it reads "...keeping track of your finances and transactions..."; update the sentence in the page.mdx content where that exact fragment appears.src/app/ideas/2026/EduAid/page.mdx-35-35 (1)
35-35:⚠️ Potential issue | 🟡 MinorTypo: "backened" should be "backend".
📝 Proposed fix
-* There should be no backened or SaaS/Cloud dependencies. +* There should be no backend or SaaS/Cloud dependencies.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/EduAid/page.mdx` at line 35, Fix the typo in the MDX content: locate the line containing the sentence "There should be no backened or SaaS/Cloud dependencies." and change "backened" to "backend" so it reads "There should be no backend or SaaS/Cloud dependencies."; update the page.mdx content accordingly and run a quick spellcheck to catch similar typos.src/app/ideas/2026/Phoenix/page.mdx-46-46 (1)
46-46:⚠️ Potential issue | 🟡 MinorTypo: "contrbiutors" should be "contributors".
📝 Proposed fix
- - For instance: What does the project need to motivate contrbiutors to maintain it and motivate users to use it? + - For instance: What does the project need to motivate contributors to maintain it and motivate users to use it?🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Phoenix/page.mdx` at line 46, Fix the typo in the sentence that currently reads "For instance: What does the project need to motivate contrbiutors to maintain it and motivate users to use it?" by replacing the misspelled word "contrbiutors" with "contributors" in the page.mdx content so the sentence reads correctly; locate the phrase containing "contrbiutors" and update that token to "contributors".src/app/ideas/2026/PictoPy/page.mdx-42-42 (1)
42-42:⚠️ Potential issue | 🟡 MinorTypo: "atleast" should be "at least".
📝 Proposed fix
-This will significantly speed up the CI workflow by atleast 300%. +This will significantly speed up the CI workflow by at least 300%.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/PictoPy/page.mdx` at line 42, Fix the typo in the sentence under the heading "CI Build Optimization Using Cached Tauri Artifacts and CDN Distribution" by replacing the incorrect single word "atleast" with the correct two-word phrase "at least" in the sentence that ends with "will significantly speed up the CI workflow by atleast 300%."; update that occurrence in the file content so it reads "by at least 300%".src/app/ideas/2026/Zplit/page.mdx-47-47 (1)
47-47:⚠️ Potential issue | 🟡 MinorTypo: "questionairres" should be "questionnaires".
📝 Proposed fix
-GSoC 2026 Contributions should conclude with a v1 deployment of Zplit to App Stores, to get the app to real users as soon as possible, and then later iterate on the App with real world feedback from users. AOSSIE already has a Play Store Developer Account, so the Candidate will be required to setup the new application here, along with filling all data safety questionairres etc., and fulfilling all publishing requirements. +GSoC 2026 Contributions should conclude with a v1 deployment of Zplit to App Stores, to get the app to real users as soon as possible, and then later iterate on the App with real-world feedback from users. AOSSIE already has a Play Store Developer Account, so the Candidate will be required to setup the new application here, along with filling all data safety questionnaires etc., and fulfilling all publishing requirements.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Zplit/page.mdx` at line 47, Replace the misspelled word "questionairres" in the GSoC 2026 Contributions paragraph (the sentence containing "AOSSIE already has a Play Store Developer Account...") with the correct spelling "questionnaires" so the sentence reads "...along with filling all data safety questionnaires etc., and fulfilling all publishing requirements."src/app/ideas/2026/Zplit/page.mdx-32-35 (1)
32-35:⚠️ Potential issue | 🟡 MinorMultiple spelling errors in this section.
- Line 32: "recieved" → "received"
- Line 35: "recieve" → "receive", "preferrably" → "preferably"
📝 Proposed fix
-Zplit will use Cryptographic signatures to sign all data transmitted between devices, to improve security on the platform. These signatures will be made using a combination of device-specific characteristics as well as self-identification information filled in by the user. This allows everyone too verify the source of any data blob recieved by their application, and reduce the risk of financial scams. +Zplit will use Cryptographic signatures to sign all data transmitted between devices, to improve security on the platform. These signatures will be made using a combination of device-specific characteristics as well as self-identification information filled in by the user. This allows everyone to verify the source of any data blob received by their application, and reduce the risk of financial scams.-As Zplit uses decentralized methods for all of its data transfer, it is required to write the business logic (aka algorithms) that the application will use to send and recieve data. There will be multiple methods and options for the end user as described in the [Zplit Repo](https://github.com/StabilityNexus/Zplit/blob/main/zplit.md). These will need to be implemented from scratch, preferrably using strongly typed Dart code. Using packages where available is allowed and preferred. +As Zplit uses decentralized methods for all of its data transfer, it is required to write the business logic (aka algorithms) that the application will use to send and receive data. There will be multiple methods and options for the end user as described in the [Zplit Repo](https://github.com/StabilityNexus/Zplit/blob/main/zplit.md). These will need to be implemented from scratch, preferably using strongly typed Dart code. Using packages where available is allowed and preferred.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Zplit/page.mdx` around lines 32 - 35, Fix the spelling mistakes in the Zplit description text: change "recieved" to "received" in the sentence starting "Zplit will use Cryptographic signatures...", change "recieve" to "receive" and "preferrably" to "preferably" in the paragraph under the "Write decentralized communication algorithms" heading, and also correct "too verify" to "to verify" where that phrase appears; ensure the updated words are applied exactly in those phrases to preserve surrounding wording and links.src/app/ideas/2026/Fate/page.mdx-60-62 (1)
60-62:⚠️ Potential issue | 🟡 MinorClarify where discussions should happen.
Line 62 says “in development” without a specific channel. Please provide a channel name or direct link.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Fate/page.mdx` around lines 60 - 62, Update the "Communication Channel" section under the "Communication Channel" header: replace the vague phrase "in development" with a specific Discord channel name or direct invite link (for example, "in the `#development` channel on our Discord (https://discord.gg/xnmAPS7zqB)") so readers know exactly where to discuss the idea; edit the line that currently reads "Join our Discord servers (...) and discuss this idea in development." to include the chosen channel identifier or link.src/app/ideas/2026/Gluon/page.mdx-49-51 (1)
49-51:⚠️ Potential issue | 🟡 MinorMake the communication target explicit.
Line 51 says “discuss this idea in development,” but doesn’t name/link a specific channel. Please provide a concrete channel reference for contributors.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Gluon/page.mdx` around lines 49 - 51, The "Communication Channel" section currently says "discuss this idea in development" without naming a specific channel; update the page.mdx content under the "## Communication Channel" heading to include an explicit channel reference and link (for example: "join our Discord and discuss this idea in the `#development` channel (https://discord.gg/xnmAPS7zqB)" or similarly name the exact server and channel like "#gluon-dev" with its invite), replacing the vague phrase so contributors have a concrete place to go.src/app/ideas/2026/DevOps/page.mdx-14-17 (1)
14-17:⚠️ Potential issue | 🟡 MinorPolish terminology/capitalization in public-facing copy.
Please normalize terms like “GitHub”, “GitHub Actions”, and “state-of-the-art” for consistency and professionalism.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/DevOps/page.mdx` around lines 14 - 17, Update the public-facing copy in src/app/ideas/2026/DevOps/page.mdx by normalizing capitalization and punctuation: replace "github" with "GitHub", "github actions" with "GitHub Actions", "state-of-the art" with "state-of-the-art", and consider changing "orgs in github" or "our orgs in github" to "our organizations in GitHub" for clarity; ensure the phrases "GitHub", "GitHub Actions", and "state-of-the-art" are used consistently throughout the paragraph.src/app/ideas/2026/Resonate/page.mdx-28-28 (1)
28-28:⚠️ Potential issue | 🟡 MinorFix possessive typo in backend description.
Line 28 uses “it's backend”; this should be “its backend”.
✏️ Proposed fix
-Resonate uses Appwrite for it's backend, and when the backend was originally designed, a number of new features didn't exist, like Relationships. +Resonate uses Appwrite for its backend, and when the backend was originally designed, a number of new features didn't exist, like Relationships.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Resonate/page.mdx` at line 28, Replace the possessive typo in the sentence that currently reads "Resonate uses Appwrite for it's backend" by changing "it's" to the correct possessive "its" so the sentence becomes "Resonate uses Appwrite for its backend"; locate this exact string in page.mdx (the paragraph describing the backend and Relationships) and update the word only.src/app/ideas/2026/OrgExplorer/page.mdx-16-43 (1)
16-43:⚠️ Potential issue | 🟡 MinorFix public-facing terminology and spelling issues.
There are a few copy errors to clean up (e.g., “github” → “GitHub”, “masively” → “massively”, “figma” → “Figma”, and “local storage/indexedDB” → “localStorage/IndexedDB”).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/OrgExplorer/page.mdx` around lines 16 - 43, Update copy in the OrgExplorer page: replace all instances of "github" with "GitHub", correct "masively" to "massively" and change the phrase "masively distributed decentralized open organizations" to "massively distributed, decentralized open organizations" (add comma), change "figma" to "Figma", and normalize storage terms "local storage" / "indexedDB" to "localStorage" / "IndexedDB"; review the text blocks around the Overview/Requirements headings in page.mdx to ensure these exact substitutions are applied consistently throughout the document.src/app/ideas/2026/Orb/page.mdx-40-41 (1)
40-41:⚠️ Potential issue | 🟡 MinorMissing @ symbol before GitHub username.
Line 41 is inconsistent with other mentor entries—it's missing the
@prefix before the GitHub username.📝 Proposed fix
* GitHub: `@Zahnentferner` ; Discord: `@b.wp` -* GitHub: DengreSarthak ; Discord: `@sarthak_09385` +* GitHub: `@DengreSarthak` ; Discord: `@sarthak_09385`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Orb/page.mdx` around lines 40 - 41, The GitHub username "DengreSarthak" in the list entry is missing the leading '@' and should match the other mentor entries; update the line containing "* GitHub: DengreSarthak ; Discord: `@sarthak_09385`" to "* GitHub: `@DengreSarthak` ; Discord: `@sarthak_09385`" so the GitHub handle includes the '@' prefix.src/app/ideas/2026/Ellena/page.mdx-51-51 (1)
51-51:⚠️ Potential issue | 🟡 MinorFix typo: "avaialable" → "available".
📝 Proposed fix
-Prepare Ell-ena for public release by publishing the mobile application on the avaialable play store. This includes making sure the app meets store requirements and feels like a complete product rather than just for a Ell-ena developers. +Prepare Ell-ena for public release by publishing the mobile application on the available Play Store. This includes making sure the app meets store requirements and feels like a complete product rather than just for Ell-ena developers.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Ellena/page.mdx` at line 51, Fix the spelling mistake in the sentence about publishing the mobile application: change "avaialable" to "available" in the page text (the line containing "Prepare Ell-ena for public release by publishing the mobile application on the avaialable play store...") so the sentence reads "...publishing the mobile application on the available play store."src/app/ideas/2026/Karma/page.mdx-15-15 (1)
15-15:⚠️ Potential issue | 🟡 MinorFix typos in the sentence.
Two typos: "the think" should be "they think", and "give price" should be "given price".
📝 Proposed fix
-Fate Protocol is a decentralized, perpetual prediction market that operates continuously without expiration. It allows users to buy bullCoins, if the think that a given price will go up and bearCoins, if they think that the give price will go down. It currently depends on external oracles to know whether the given price is going up or down. +Fate Protocol is a decentralized, perpetual prediction market that operates continuously without expiration. It allows users to buy bullCoins if they think that a given price will go up and bearCoins if they think that the given price will go down. It currently depends on external oracles to know whether the given price is going up or down.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Karma/page.mdx` at line 15, In the sentence beginning "Fate Protocol is a decentralized, perpetual prediction market..." (in page.mdx), fix the two typos: change "the think" to "they think" and "give price" to "given price" so the clause reads "...allows users to buy bullCoins, if they think that a given price will go up and bearCoins, if they think that a given price will go down."
🧹 Nitpick comments (8)
src/helper/projects.js (1)
20-20: Deduplicate the repeated Discord URL into a constant.The same literal is repeated across many entries, which makes future link changes error-prone.
Refactor example
+const COMMON_DISCORD_LINK = 'https://discord.gg/xnmAPS7zqB' + const projects = [ { // ... - discordLink: 'https://discord.gg/xnmAPS7zqB', + discordLink: COMMON_DISCORD_LINK, },Also applies to: 35-35, 47-47, 59-59, 71-71, 83-83, 96-96, 108-108, 120-120, 132-132, 144-144, 156-156, 168-168, 180-180, 192-192, 204-204, 216-216, 228-228, 240-240, 252-252, 264-264, 276-276
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/helper/projects.js` at line 20, Define a single constant for the repeated Discord invite and replace all literal occurrences with it: add e.g. const DISCORD_URL = 'https://discord.gg/xnmAPS7zqB' near the top of src/helper/projects.js (above the projects array/const that holds the entries) and update every object property that currently uses the string literal discordLink to use DISCORD_URL instead (these properties are the discordLink keys in the projects list). Keep exports and other object fields unchanged.src/app/ideas/2026/DocPilot/page.mdx (1)
3-6: Consider a more descriptive meta description.The description is just "DocPilot" which duplicates the title. A more descriptive value would improve discoverability and provide better context in listings.
📝 Proposed improvement
export const meta = { title: 'DocPilot', - description: 'DocPilot' + description: 'AI-Powered EMR Application for Conversational Prescription Generation' }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/DocPilot/page.mdx` around lines 3 - 6, The meta export (export const meta) currently sets description to just "DocPilot", duplicating the title; update the meta.description value to a more descriptive sentence (50–160 characters) summarizing what DocPilot does and including key terms for discoverability (e.g., "DocPilot — AI-assisted document summarization and search for teams, supporting PDFs, DOCX, and knowledge bases"); modify the description string in the export const meta object so listings and SEO show meaningful context.src/app/ideas/2026/orderbook-auction-exchange/page.mdx (1)
47-48: Minor: "Github" should be capitalized as "GitHub".This is the official brand name spelling.
📝 Proposed fix
-- Github: `@Zahnentferner`; Discord: `@b.wp` -- Github: `@kaneki003`; Discord: `@kaneki003` +- GitHub: `@Zahnentferner`; Discord: `@b.wp` +- GitHub: `@kaneki003`; Discord: `@kaneki003`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/orderbook-auction-exchange/page.mdx` around lines 47 - 48, Update the two contributor lines that use the incorrect brand casing "Github" to the official "GitHub": change the strings "- Github: `@Zahnentferner`; Discord: `@b.wp`" and "- Github: `@kaneki003`; Discord: `@kaneki003`" in page.mdx to use "GitHub" so they read "- GitHub: `@Zahnentferner`; Discord: `@b.wp`" and "- GitHub: `@kaneki003`; Discord: `@kaneki003`".src/app/ideas/2026/landing-pages/page.mdx (1)
14-26: Minor: "github" and "github pages" should be capitalized as "GitHub" and "GitHub Pages".These are official brand names and should use proper capitalization.
📝 Proposed fix
-Many of our projects exist merely as a github repo. This is adequate for projects whose target audience are developers, but not for projects intended for end-users. +Many of our projects exist merely as a GitHub repo. This is adequate for projects whose target audience are developers, but not for projects intended for end-users.-* Deploy each landing page in github pages with custom domain at https://<project-name>.aossie.org . +* Deploy each landing page in GitHub Pages with custom domain at https://<project-name>.aossie.org .🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/landing-pages/page.mdx` around lines 14 - 26, Replace the lowercase brand mentions "github" and "github pages" with the official capitalizations "GitHub" and "GitHub Pages" throughout the document; search for the literal strings "github" and "github pages" (e.g., the paragraph starting "Many of our projects..." and the task bullet "Deploy each landing page in github pages...") and update them to "GitHub" and "GitHub Pages" respectively to use the correct brand names.src/app/ideas/2026/Ellena/page.mdx (2)
3-6: Improve the meta description.The description just repeats the title. Other idea pages have meaningful descriptions (e.g., "A lightweight blockchain implementation for experimentation and education"). Consider adding a brief description of what Ellena is.
📝 Proposed fix
export const meta = { title: 'Ellena', - description: 'Ellena' + description: 'An AI-powered product manager that automates task management and meeting transcription.' }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Ellena/page.mdx` around lines 3 - 6, Update the meta object in page.mdx so the description field describes what Ellena actually is instead of repeating the title: locate the exported const meta (fields title and description) and replace the description value with a concise, informative sentence about Ellena (e.g., its purpose, scope, and audience) to match the style used on other idea pages.
36-36: Use proper capitalization for "GitHub"."Github" appears three times and should be spelled "GitHub" (capital H).
📝 Proposed fix
-Integrate Github to automate issue and PR lifecycle on Github directly. Opening an Engineering labelled issue on Ellena kanban board should directly open a Github issue. Creating a PR for that issue, should move the ticket on the kanban board to "In review" status. Once the PR is merged, the ticket should be moved to "Done" status. +Integrate GitHub to automate issue and PR lifecycle on GitHub directly. Opening an Engineering labelled issue on Ellena kanban board should directly open a GitHub issue. Creating a PR for that issue, should move the ticket on the kanban board to "In review" status. Once the PR is merged, the ticket should be moved to "Done" status.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Ellena/page.mdx` at line 36, The text in src/app/ideas/2026/Ellena/page.mdx uses "Github" three times; update each occurrence to the correct "GitHub" spelling (capital H) so the sentence reads: "Integrate GitHub to automate issue and PR lifecycle on GitHub directly. Opening an Engineering labelled issue on Ellena kanban board should directly open a GitHub issue. Creating a PR for that issue, should move the ticket on the kanban board to "In review" status. Once the PR is merged, the ticket should be moved to "Done" status."src/app/ideas/2026/MiniChain/page.mdx (1)
70-70: Use proper capitalization for "GitHub"."Github" should be spelled "GitHub" (capital H) for consistency with the official branding.
📝 Proposed fix
-* Github: `@Zahnentferner`; Discord: `@b.wp` +* GitHub: `@Zahnentferner`; Discord: `@b.wp`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/MiniChain/page.mdx` at line 70, Update the branding spelling in the profile line by replacing the string "* Github: `@Zahnentferner`; Discord: `@b.wp`" with the correct "GitHub" capitalization (e.g., "* GitHub: `@Zahnentferner`; Discord: `@b.wp`") in the page.mdx content so the project uses the official GitHub casing.src/app/ideas/2026/Karma/page.mdx (1)
78-80: Use proper capitalization for "GitHub"."Github" should be spelled "GitHub" (capital H) for consistency with the official branding.
📝 Proposed fix
* GitHub: `@blizet` ; Discord: `@blizet4910` * GitHub: `@yogesh0509`; Discord: `@yogesh0509` -* Github: `@DengreSarthak`; Discord: `@DenSarthak` +* GitHub: `@DengreSarthak`; Discord: `@DenSarthak` * GitHub: `@Zahnentferner` ; Discord: `@b.wp`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/app/ideas/2026/Karma/page.mdx` around lines 78 - 80, Update all occurrences of "Github" in the contributors list to the official "GitHub" capitalization so branding is consistent; specifically change lines containing "* Github: `@DengreSarthak`; Discord: `@DenSarthak`" (and any other "Github" instances) to "* GitHub: ..." and ensure other entries like "@blizet" and "@yogesh0509" remain unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@src/helper/projects.js`:
- Around line 9-338: The projects array entries removed fields that the details
page expects (product.setupGuide and product.feedbacks), causing regressions;
for every object in the projects array (the variable projects), restore those
keys with safe defaults (e.g., add setupGuide: '' or null and feedbacks: [] to
each project object) so the details renderer (which accesses product.setupGuide
and product.feedbacks) always finds them and avoids runtime errors.
---
Minor comments:
In `@src/app/ideas/2026/Bot/page.mdx`:
- Line 5: The frontmatter and body contain repeated branding/typo issues—replace
all instances of "Github" with "GitHub", "especialy" with "especially", and
"generable" with "generalizable" across this page (including the frontmatter
description field and any titles or paragraph text); update the description:
'Discord/Github Bot' to 'Discord/GitHub Bot' and search the document for the
other misspellings (e.g., in headings or body text) and correct them so all
user-facing strings (title, description, and content) consistently use the
corrected spellings.
In `@src/app/ideas/2026/Choice/page.mdx`:
- Line 26: Replace the misspelled word "alternaives" with "alternatives" in the
sentence that reads "which approach and which alternaives they are going to use
in each project" within the Choice page content; edit the string in the page
content (the paragraph containing that sentence) so it now reads "which approach
and which alternatives they are going to use in each project".
In `@src/app/ideas/2026/DevOps/page.mdx`:
- Around line 14-17: Update the public-facing copy in
src/app/ideas/2026/DevOps/page.mdx by normalizing capitalization and
punctuation: replace "github" with "GitHub", "github actions" with "GitHub
Actions", "state-of-the art" with "state-of-the-art", and consider changing
"orgs in github" or "our orgs in github" to "our organizations in GitHub" for
clarity; ensure the phrases "GitHub", "GitHub Actions", and "state-of-the-art"
are used consistently throughout the paragraph.
In `@src/app/ideas/2026/DIT/page.mdx`:
- Line 26: Fix the typo in the sentence fragment "can endorse that the holder of
the token is indeed the entity that has those charcteristics." by changing
"charcteristics" to the correct spelling "characteristics" so the line reads
"...that has those characteristics."
- Line 21: In the sentence that currently reads "For example, when you get a
passport, the government is endrosing the fact that you," replace the misspelled
word "endrosing" with the correct spelling "endorsing" so the line reads "...the
government is endorsing the fact that you,"; ensure only the spelling is changed
and punctuation/spacing remains unchanged.
- Line 55: Fix the typo in the sentence that mentions Discord roles: change
"teh" to "the" in the line referencing AOSSIE's Discord and the Stability Nexus
roles (the sentence containing "@Contributor-StabilityNexus", "@TNT" and
"@VouchMe"); ensure the corrected sentence reads "the Discord of the Stability
Nexus."
In `@src/app/ideas/2026/Djed/page.mdx`:
- Line 59: Update the sentence "Join our Discord servers
(https://discord.gg/xnmAPS7zqB and https://discord.gg/fuuWX4AbJt) and discuss
this idea in development." to point to the exact channel where applicants should
post (replace the ambiguous "discuss this idea in development" with the concrete
Discord channel invite or channel ID/URL used on other idea pages), e.g.,
include the specific channel invite/ID right after the server link so readers
know precisely where to post.
- Line 4: The meta.title frontmatter currently contains leading spaces ('
Djed'); update the frontmatter value for meta.title (the title entry in
page.mdx) to remove leading/trailing whitespace so it reads "Djed" (no extra
spaces) to ensure consistent rendering in lists/headings.
In `@src/app/ideas/2026/EduAI/page.mdx`:
- Line 35: Fix the copy errors in the user-facing requirements and mentor text
by correcting "backened" to "backend" and normalizing casing of "SaaS/Cloud" to
a consistent form (e.g., "SaaS/cloud" or "SaaS/Cloud" per project style). Locate
the offending lines containing the sentence "There should be no backened or
SaaS/Cloud dependencies." (and the identical occurrence referenced at the other
instance) and update both to the corrected spelling and consistent casing so
both the requirement and mentor text match.
In `@src/app/ideas/2026/EduAid/page.mdx`:
- Line 35: Fix the typo in the MDX content: locate the line containing the
sentence "There should be no backened or SaaS/Cloud dependencies." and change
"backened" to "backend" so it reads "There should be no backend or SaaS/Cloud
dependencies."; update the page.mdx content accordingly and run a quick
spellcheck to catch similar typos.
In `@src/app/ideas/2026/Ellena/page.mdx`:
- Line 51: Fix the spelling mistake in the sentence about publishing the mobile
application: change "avaialable" to "available" in the page text (the line
containing "Prepare Ell-ena for public release by publishing the mobile
application on the avaialable play store...") so the sentence reads
"...publishing the mobile application on the available play store."
In `@src/app/ideas/2026/Fate/page.mdx`:
- Around line 60-62: Update the "Communication Channel" section under the
"Communication Channel" header: replace the vague phrase "in development" with a
specific Discord channel name or direct invite link (for example, "in the
`#development` channel on our Discord (https://discord.gg/xnmAPS7zqB)") so readers
know exactly where to discuss the idea; edit the line that currently reads "Join
our Discord servers (...) and discuss this idea in development." to include the
chosen channel identifier or link.
In `@src/app/ideas/2026/Gluon/page.mdx`:
- Around line 49-51: The "Communication Channel" section currently says "discuss
this idea in development" without naming a specific channel; update the page.mdx
content under the "## Communication Channel" heading to include an explicit
channel reference and link (for example: "join our Discord and discuss this idea
in the `#development` channel (https://discord.gg/xnmAPS7zqB)" or similarly name
the exact server and channel like "#gluon-dev" with its invite), replacing the
vague phrase so contributors have a concrete place to go.
In `@src/app/ideas/2026/Karma/page.mdx`:
- Line 15: In the sentence beginning "Fate Protocol is a decentralized,
perpetual prediction market..." (in page.mdx), fix the two typos: change "the
think" to "they think" and "give price" to "given price" so the clause reads
"...allows users to buy bullCoins, if they think that a given price will go up
and bearCoins, if they think that a given price will go down."
In `@src/app/ideas/2026/less-cloud/page.mdx`:
- Line 36: Update the phrase in the sentence starting "In the case of Next.JS
frontends…" to use the official capitalization: replace "github pages" with
"GitHub Pages" (keep the rest of the sentence unchanged); locate the string in
page.mdx that contains "In the case of Next.JS frontends, we can use client-side
only…" and correct only that token.
In `@src/app/ideas/2026/NeuroTrack/page.mdx`:
- Line 35: The page currently references the role label "@Contributor-Ellena"
which appears incorrect; verify the intended mentor role and replace
"@Contributor-Ellena" with the correct role label (or remove the suffix) to
match the project's canonical mentor roles (e.g., the existing "@Mentor" usage);
also scan other idea pages for consistent role naming and update any mismatches
to prevent directing applicants to the wrong Discord group.
- Line 10: The H1 heading currently reads "# Neurotrack" and should use the
project’s canonical casing; update the top-level heading in page.mdx from
"Neurotrack" to "NeuroTrack" so the H1 matches the project/meta name exactly.
In `@src/app/ideas/2026/Orb/page.mdx`:
- Around line 40-41: The GitHub username "DengreSarthak" in the list entry is
missing the leading '@' and should match the other mentor entries; update the
line containing "* GitHub: DengreSarthak ; Discord: `@sarthak_09385`" to "*
GitHub: `@DengreSarthak` ; Discord: `@sarthak_09385`" so the GitHub handle includes
the '@' prefix.
In `@src/app/ideas/2026/OrgExplorer/page.mdx`:
- Around line 16-43: Update copy in the OrgExplorer page: replace all instances
of "github" with "GitHub", correct "masively" to "massively" and change the
phrase "masively distributed decentralized open organizations" to "massively
distributed, decentralized open organizations" (add comma), change "figma" to
"Figma", and normalize storage terms "local storage" / "indexedDB" to
"localStorage" / "IndexedDB"; review the text blocks around the
Overview/Requirements headings in page.mdx to ensure these exact substitutions
are applied consistently throughout the document.
In `@src/app/ideas/2026/Phoenix/page.mdx`:
- Around line 70-71: Fix the typo "th respective" to "the respective" in the
sentence that invites readers to join Discord (the line containing the two
Discord invite links and the channel URL in page.mdx); update the text so it
reads "the respective project channels" to correct the spelling.
- Line 46: Fix the typo in the sentence that currently reads "For instance: What
does the project need to motivate contrbiutors to maintain it and motivate users
to use it?" by replacing the misspelled word "contrbiutors" with "contributors"
in the page.mdx content so the sentence reads correctly; locate the phrase
containing "contrbiutors" and update that token to "contributors".
In `@src/app/ideas/2026/PictoPy/page.mdx`:
- Line 42: Fix the typo in the sentence under the heading "CI Build Optimization
Using Cached Tauri Artifacts and CDN Distribution" by replacing the incorrect
single word "atleast" with the correct two-word phrase "at least" in the
sentence that ends with "will significantly speed up the CI workflow by atleast
300%."; update that occurrence in the file content so it reads "by at least
300%".
In `@src/app/ideas/2026/Resonate/page.mdx`:
- Line 28: Replace the possessive typo in the sentence that currently reads
"Resonate uses Appwrite for it's backend" by changing "it's" to the correct
possessive "its" so the sentence becomes "Resonate uses Appwrite for its
backend"; locate this exact string in page.mdx (the paragraph describing the
backend and Relationships) and update the word only.
In `@src/app/ideas/2026/UI/page.mdx`:
- Line 14: Replace the typo in the paragraph text where it reads "UI/UX pf" with
the correct phrase "UI/UX of" in the page content (look for the string "UI/UX
pf" in the UI/UX background paragraph within src/app/ideas/2026/UI/page.mdx and
update it to "UI/UX of").
In `@src/app/ideas/2026/Zplit/page.mdx`:
- Around line 3-6: Update the meta.description value on the exported meta object
so it accurately reflects Zplit as a group transaction/expense-splitting
solution rather than a coding platform; locate the exported const meta (title:
'Zplit') and change the description property to a concise phrase like "A group
transaction tracking and expense-splitting solution" that matches the page
content.
- Line 17: Fix the typo in the sentence "Zplit was ideated to solve this very
issue, because keeping track of you finances and transactions shouldn't require
you to make more transactions." by replacing "you finances" with "your finances"
so it reads "...keeping track of your finances and transactions..."; update the
sentence in the page.mdx content where that exact fragment appears.
- Line 47: Replace the misspelled word "questionairres" in the GSoC 2026
Contributions paragraph (the sentence containing "AOSSIE already has a Play
Store Developer Account...") with the correct spelling "questionnaires" so the
sentence reads "...along with filling all data safety questionnaires etc., and
fulfilling all publishing requirements."
- Around line 32-35: Fix the spelling mistakes in the Zplit description text:
change "recieved" to "received" in the sentence starting "Zplit will use
Cryptographic signatures...", change "recieve" to "receive" and "preferrably" to
"preferably" in the paragraph under the "Write decentralized communication
algorithms" heading, and also correct "too verify" to "to verify" where that
phrase appears; ensure the updated words are applied exactly in those phrases to
preserve surrounding wording and links.
In `@src/components/ideas/IdeasHeader.jsx`:
- Around line 71-78: Replace the hardcoded Gmail URL in the anchor inside
IdeasHeader.jsx with a mailto: link so users open their preferred email client
(e.g., set
href="mailto:aossie.oss@gmail.com?subject=New%20Project%20Idea&body=Hello%20AOSSIE%20Team");
keep the existing attributes (target, rel, className) and text ("Submit Your
Idea") unchanged, or optionally provide both links (mailto primary, Gmail as a
secondary button) if you must preserve Gmail behavior; also fix the inconsistent
indentation around that <a> element to match the surrounding JSX formatting.
---
Nitpick comments:
In `@src/app/ideas/2026/DocPilot/page.mdx`:
- Around line 3-6: The meta export (export const meta) currently sets
description to just "DocPilot", duplicating the title; update the
meta.description value to a more descriptive sentence (50–160 characters)
summarizing what DocPilot does and including key terms for discoverability
(e.g., "DocPilot — AI-assisted document summarization and search for teams,
supporting PDFs, DOCX, and knowledge bases"); modify the description string in
the export const meta object so listings and SEO show meaningful context.
In `@src/app/ideas/2026/Ellena/page.mdx`:
- Around line 3-6: Update the meta object in page.mdx so the description field
describes what Ellena actually is instead of repeating the title: locate the
exported const meta (fields title and description) and replace the description
value with a concise, informative sentence about Ellena (e.g., its purpose,
scope, and audience) to match the style used on other idea pages.
- Line 36: The text in src/app/ideas/2026/Ellena/page.mdx uses "Github" three
times; update each occurrence to the correct "GitHub" spelling (capital H) so
the sentence reads: "Integrate GitHub to automate issue and PR lifecycle on
GitHub directly. Opening an Engineering labelled issue on Ellena kanban board
should directly open a GitHub issue. Creating a PR for that issue, should move
the ticket on the kanban board to "In review" status. Once the PR is merged, the
ticket should be moved to "Done" status."
In `@src/app/ideas/2026/Karma/page.mdx`:
- Around line 78-80: Update all occurrences of "Github" in the contributors list
to the official "GitHub" capitalization so branding is consistent; specifically
change lines containing "* Github: `@DengreSarthak`; Discord: `@DenSarthak`" (and
any other "Github" instances) to "* GitHub: ..." and ensure other entries like
"@blizet" and "@yogesh0509" remain unchanged.
In `@src/app/ideas/2026/landing-pages/page.mdx`:
- Around line 14-26: Replace the lowercase brand mentions "github" and "github
pages" with the official capitalizations "GitHub" and "GitHub Pages" throughout
the document; search for the literal strings "github" and "github pages" (e.g.,
the paragraph starting "Many of our projects..." and the task bullet "Deploy
each landing page in github pages...") and update them to "GitHub" and "GitHub
Pages" respectively to use the correct brand names.
In `@src/app/ideas/2026/MiniChain/page.mdx`:
- Line 70: Update the branding spelling in the profile line by replacing the
string "* Github: `@Zahnentferner`; Discord: `@b.wp`" with the correct "GitHub"
capitalization (e.g., "* GitHub: `@Zahnentferner`; Discord: `@b.wp`") in the
page.mdx content so the project uses the official GitHub casing.
In `@src/app/ideas/2026/orderbook-auction-exchange/page.mdx`:
- Around line 47-48: Update the two contributor lines that use the incorrect
brand casing "Github" to the official "GitHub": change the strings "- Github:
`@Zahnentferner`; Discord: `@b.wp`" and "- Github: `@kaneki003`; Discord: `@kaneki003`"
in page.mdx to use "GitHub" so they read "- GitHub: `@Zahnentferner`; Discord:
`@b.wp`" and "- GitHub: `@kaneki003`; Discord: `@kaneki003`".
In `@src/helper/projects.js`:
- Line 20: Define a single constant for the repeated Discord invite and replace
all literal occurrences with it: add e.g. const DISCORD_URL =
'https://discord.gg/xnmAPS7zqB' near the top of src/helper/projects.js (above
the projects array/const that holds the entries) and update every object
property that currently uses the string literal discordLink to use DISCORD_URL
instead (these properties are the discordLink keys in the projects list). Keep
exports and other object fields unchanged.
Collaborator
|
This wouldn't work for users who do not have a gmail account. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addressed Issues:
Fixes #644
Problem
The "Submit Your Idea" button on the /ideas page was previously using a mailto: link:
mailto:aossie.oss@gmail.com
In many browsers, this behavior depends on the user's configured email handler. When the button was clicked, the browser asked the user to select an email handler (e.g., Gmail), but no compose window opened afterward, resulting in the action failing silently.
Root Cause
The button was implemented using a mailto: link inside a Next.js component.
Since mailto: relies on the user's system email client configuration, it may not reliably open the compose window in browser-based email clients like Gmail.
Solution
The button was updated to directly open the Gmail compose interface using the Gmail compose URL.
The link now redirects users to Gmail with pre-filled email details.
Updated implementation:
https://mail.google.com/mail/?view=cm&fs=1&to=aossie.oss@gmail.com&su=New%20Project%20Idea&body=Hello%20AOSSIE%20Team
Result
Clicking "Submit Your Idea" now reliably opens the Gmail compose window in a new tab.
The following fields are automatically pre-filled:
Recipient: aossie.oss@gmail.com
Subject: New Project Idea
Body message:
Hello AOSSIE Team
This ensures that users can immediately start drafting their idea submission without manually entering the email details.
User Experience Improvement
Users are now directly taken to the Gmail compose interface, avoiding the browser email handler prompt and ensuring consistent behavior across browsers.
Verification
After the fix:
Navigate to /ideas
Scroll to the "Have an Idea?" section
Click "Submit Your Idea"
Gmail opens in a new tab with the recipient, subject, and greeting message already filled.
Screenshots/Recordings:
Additional Notes:
AI Usage Disclosure:
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact. AI slop is strongly discouraged and may lead to banning and blocking. Do not spam our repos with AI slop.
Check one of the checkboxes below:
I have used the following AI models and tools: TODO
Checklist
Summary by CodeRabbit