LearnNewsExamplesServices
Frontmatter
id7296
titleHacktoberfest 2025: Build Your AI Development Skills with Neo.mjs
stateClosed
labels
help wantedgood first issueepichacktoberfest
assignees[]
createdAtSep 28, 2025, 2:23 PM
updatedAtNov 2, 2025, 10:30 AM
githubUrlhttps://github.com/neomjs/neo/issues/7296
authortobiu
commentsCount3
parentIssuenull
subIssues
7297 Create a Modern ''Getting Started'' Guide
7298 A Beginner''s Guide to View Controllers
7299 Add Intent-Driven JSDoc to Tab Container Example
7301 Add Intent-Driven JSDoc to `splitter.MainContainer` Example
7305 Test and Use the `createExample` Script to Build an `Image` Example
7306 Exploration Quest: Make the AI Aware of `buildScripts`
7307 Re-framing the VDOM - Neo.mjs''s Lightweight Messaging Protocol
7328 Create Guide: Neo.setupClass() Deep Dive
7342 Hacktoberfest Mission: Train the AI - Test Its Memory! (1/5)
7343 Hacktoberfest Mission: Train the AI - Test Its Memory! (2/5)
7344 Hacktoberfest Mission: Train the AI - Test Its Memory! (3/5)
7345 Hacktoberfest Mission: Train the AI - Test Its Memory! (4/5)
7346 Hacktoberfest Mission: Train the AI - Test Its Memory! (5/5)
7417 Polish the new ''Getting Started'' Guide
7465 Hacktoberfest Mission: Implement the Memory Protocol Fix
7467 `ai:query` fails to find content in existing blog post
7474 Improve AI Query Scoring to Boost Content Matches
subIssuesCompleted17
subIssuesTotal17
blockedBy[]
blocking[]
closedAtNov 2, 2025, 10:30 AM

Hacktoberfest 2025: Build Your AI Development Skills with Neo.mjs

Closed v11.0.0 help wantedgood first issueepichacktoberfest
tobiu
tobiu commented on Sep 28, 2025, 2:23 PM

🚀 Level Up Your Career in 5 Minutes

Add these to your resume after Hacktoberfest:

  • ✅ AI-Augmented Development Experience
  • ✅ Open Source Contributor to Production Framework
  • ✅ Next-Gen JavaScript Architecture (Multi-threading, RAG Systems)
  • ✅ Published Technical Content (if you write a blog post)

Hacktoberfest starts October 1st - Your competitive edge awaits!

Choose Your Path - All Lead to Success

Path 1: The Classic Contributor (No AI Setup Required)

Dive directly into the codebase and make a tangible impact. This path is perfect for developers of all skill levels who prefer a traditional workflow. Here are some high-impact ways to contribute:

  • Write High-Quality Documentation: Good documentation is the backbone of a healthy open-source project. Help fellow developers by adding clear, intent-driven JSDoc comments to undocumented classes and methods in the /src directory. Bonus: Our AI-native system consumes these comments, so every piece of documentation you write also makes our AI assistant smarter.
  • Build New Examples: Create a new, practical code example for any component in the /examples folder. This is one of the best ways to learn the framework and help others.
  • Strengthen the Codebase: Add or improve unit tests for existing functionality.
  • Fix Bugs & Refactor: Tackle an issue from our good first issue list or propose a refactoring to improve code quality.

Path 2: AI-Powered Development (15-minute setup, then fly)

Let AI do the heavy lifting while you learn. The one-time setup takes about 15 minutes and leverages Google's generous free tier, which works in two parts:

  • Knowledge Base: Building and querying the knowledge base uses the text-embedding-004 model, which is free for up to 60 queries per minute.
  • AI Agent: For interactive development, if you use the Gemini CLI, it uses the gemini-pro model, which provides up to 3 million tokens per day for free.

1. Read the Guides:

  • Working with AI Agents: First, read this playbook for you, the human developer. It provides essential strategies for guiding the agent and maximizing its performance.
  • AI Knowledge Base Quick Start Guide: Then, follow this guide to build the local knowledge base that the AI uses to understand the project.

This will walk you through building the local knowledge base that the AI uses to understand the project.

2. Then, just chat with your AI:

gemini
> "Help me find something to improve in Neo.mjs"

The AI handles everything - you just guide and learn!

Path 3: Content Creator Route

Write about your experience, no coding required:

  • Document your Hacktoberfest journey
  • Review Neo.mjs from your perspective
  • Compare it to frameworks you know
  • Share what you learned

We especially value blog posts! They help others learn.


How to Contribute: The Neo.mjs Way

Unlike traditional Hacktoberfest projects where you pick from a pre-existing list of issues, we encourage you to propose your own contributions. This is a core part of our AI-native philosophy: you will use the AI agent as a partner to explore the codebase, identify areas for improvement, and define your own work.

Our workflow is designed to mirror a real-world development process:

  1. Explore and Discover: Use your chosen path (Classic or AI-Powered) to find something to improve. This could be missing documentation, a component that needs an example, a bug, or a potential refactoring.
  2. Propose Your Task by Opening an Issue: Once you have an idea, open a new issue on GitHub. Clearly describe the work you intend to do. This is your proposal.
  3. Get Approval and Assignment: A maintainer will review your proposal. If it's aligned with the project goals, we will approve it, assign it to you, and add the hacktoberfest label. Please wait for this approval before starting your work.
  4. Implement Your Change: Once approved, you can start working on your contribution.
  5. Submit Your PR: Link your Pull Request to the issue you created.

This "propose, then build" model is exactly how professional software development works. It gives you a more realistic and valuable experience than simply grabbing a pre-made ticket. While we will still tag a few issues with hacktoberfest for those who prefer a traditional start, we highly encourage you to try our discovery-led process.


What Makes Neo.mjs Different (Optional Reading)

Neo.mjs is the first framework built for AI collaboration. While others bolt AI on top, we built it into our DNA.

Want the full story? Read "AI-Native, Not AI-Assisted" on GitHub or Medium (friends link, no paywall) (or skip it and just start contributing!)

Example Contribution Workflows

Classic Contribution: Adding Documentation

This workflow shows how a classic contribution directly improves the codebase.

Before: An undocumented function.

createVnode(vdom) {
    // complex logic here
}

After: Clear, intent-driven documentation is added.

/**
 * Transforms a JSON blueprint into a virtual DOM node structure.
 * Part of Neo's reactivity system - enables surgical DOM updates.
 * @param {Object} vdom - JSON blueprint describing the UI component
 * @returns {Object} Virtual node ready for DOM rendering
 */
createVnode(vdom) {
    // complex logic here
}

This documentation is now part of the knowledge base, making the AI smarter for the next contributor.

AI-Powered Contribution: Learning and Building

This workflow demonstrates using the AI as a pair programmer to learn and contribute simultaneously.

You: "Find me a component that needs better examples"
AI: "I found Neo.button.Split lacks examples. Let me explain what it does..."
You: "Create an example showing its features"
AI: [generates code]
You: "Explain how this works"
AI: [teaches you the concepts]

Who Succeeds Here?

Complete Beginners - "I learned more in one PR than a month of tutorials"
Designers - "I described a UI, AI built it, I learned how it works"
Writers - "My blog post about the experience got 500 views"
Senior Devs - "Finally saw how RAG works in production"
Students - "Added 'AI Development' to my internship applications"

Only requirement: Basic Git/GitHub (standard Hacktoberfest knowledge)

Contribution Ideas by Time Investment

Got 15 minutes?

  • Fix a typo
  • Add a missing JSDoc comment
  • Improve an error message

Got 30 minutes?

  • Document a utility function
  • Add an example to a component
  • Write about your first impression

Got 1 hour?

  • Create a component demo
  • Write a comparison blog post
  • Migrate a test with AI help

Got 2+ hours?

  • Build a mini-app
  • Deep dive into architecture
  • Create a tutorial

The Multiplier Effect

Your contribution doesn't just add code - it makes everyone after you more productive:

  1. You document a function → AI can now explain it perfectly
  2. You write a blog post → Next person learns faster
  3. You add an example → AI uses it to teach patterns
  4. The ecosystem gets smarter → Everyone benefits

Support When You Need It

Stuck? We've got you:

Start Contributing NOW

🎯 Fastest Start (2 minutes)

<h1 class="neo-h1" data-record-id="22">Find any file, add any comment, make any improvement</h1>

git clone https://github.com/neomjs/neo.git
cd neo
<h1 class="neo-h1" data-record-id="23">Browse /src, find something unclear, clarify it</h1>

🤖 AI-Powered Start (15 minutes)

Set up once following the AI Knowledge Base Quick Start Guide, then the AI guides everything.

gemini  # or your preferred AI tool
> "Guide me through my first Neo.mjs contribution"

✍️ Writer's Start (0 setup)

  • Fork the repo
  • Create a file in /learn/blog/
  • Write about why you chose Neo.mjs for Hacktoberfest
  • Submit PR

Look for These Labels

hacktoberfest - Counts for the event
good first issue - Great starting points
documentation - No coding required
blog-post - Content needed
help wanted - Where we need you most

Why This Matters for Your Career

Companies are desperately seeking developers who can work with AI effectively. By contributing to Neo.mjs, you're not just adding to open source - you're building proof of your ability to:

  • Collaborate with AI systems
  • Understand modern architectures
  • Contribute to production codebases
  • Communicate technical concepts

This experience sets you apart in job interviews.


Remember: Every PR is a learning opportunity. Every comment makes the framework smarter. Every blog post helps someone else.

Join us. The future of development is being written right now.

Neo.mjs: Where your contributions compound into everyone's success.

tobiu added the help wanted label on Sep 28, 2025, 2:23 PM
tobiu added the good first issue label on Sep 28, 2025, 2:23 PM
tobiu added the epic label on Sep 28, 2025, 2:23 PM
tobiu added the hacktoberfest label on Sep 28, 2025, 2:23 PM
tobiu added sub-issue #7297 on Sep 28, 2025, 2:48 PM
tobiu assigned to @tobiu on Sep 28, 2025, 2:49 PM
tobiu added sub-issue #7298 on Sep 28, 2025, 2:50 PM
tobiu added sub-issue #7299 on Sep 28, 2025, 2:53 PM
tobiu referenced in commit bf5b347 - "#7296 subs md files" on Sep 28, 2025, 3:09 PM
tobiu added sub-issue #7301 on Sep 28, 2025, 3:34 PM
tobiu added sub-issue #7302 on Sep 28, 2025, 3:50 PM
tobiu removed sub-issue #7302 on Sep 28, 2025, 3:51 PM
tobiu referenced in commit 9062317 - "#7296 sub md file" on Sep 28, 2025, 3:52 PM
tobiu added sub-issue #7305 on Sep 28, 2025, 4:07 PM
tobiu added sub-issue #7306 on Sep 28, 2025, 4:13 PM
tobiu referenced in commit 240d918 - "#7296 ticket md files" on Sep 28, 2025, 4:14 PM
tobiu
tobiu Sep 28, 2025, 4:27 PM

This ticket itself is already an example of the "ai native" workflow. It was created as a combined effort of Claude and Gemini with guidance. I will keep it unassigned, so that it hopefully show up in event search tools.

tobiu unassigned from @tobiu on Sep 28, 2025, 4:27 PM
tobiu added sub-issue #7307 on Sep 28, 2025, 5:25 PM
tobiu referenced in commit 1cca92a - "#7296 new sub md file" on Sep 28, 2025, 5:26 PM
tobiu
tobiu Sep 29, 2025, 11:58 AM
tobiu referenced in commit 6a7ddda - "#7296 internal tickets update" on Oct 1, 2025, 10:11 AM
tobiu added sub-issue #7328 on Oct 2, 2025, 7:42 PM
tobiu referenced in commit a321602 - "#7296 new sub md file" on Oct 2, 2025, 7:42 PM
tobiu referenced in commit ebd2804 - "#7296 new sub md file => gh id" on Oct 2, 2025, 7:43 PM
tobiu cross-referenced by #7289 on Oct 3, 2025, 6:13 PM
tobiu cross-referenced by #7287 on Oct 3, 2025, 6:15 PM
tobiu cross-referenced by #7283 on Oct 3, 2025, 6:17 PM
tobiu added sub-issue #7342 on Oct 4, 2025, 10:37 AM
tobiu added sub-issue #7343 on Oct 4, 2025, 10:41 AM
tobiu added sub-issue #7344 on Oct 4, 2025, 10:46 AM
tobiu added sub-issue #7345 on Oct 4, 2025, 10:48 AM
tobiu added sub-issue #7346 on Oct 4, 2025, 10:52 AM
tobiu referenced in commit 0e84aea - "#7296 new sub-ticket md files" on Oct 4, 2025, 11:30 AM
tobiu
tobiu Oct 4, 2025, 4:22 PM

Hi guys! As the epic mentions: you are welcome to open hacktoberfest tickets on your own. E.g. using the "ai native" workflow, gemini can easily provide you with ideas.

Alternatively, you are also welcome to just ask here for more tickets (ideally with a short summary on what you would like to work on).

tobiu cross-referenced by #7364 on Oct 5, 2025, 12:34 PM
tobiu cross-referenced by #7391 on Oct 6, 2025, 1:58 PM
tobiu cross-referenced by #7399 on Oct 7, 2025, 11:26 AM
tobiu added sub-issue #7417 on Oct 8, 2025, 3:19 PM
tobiu cross-referenced by #7418 on Oct 8, 2025, 4:32 PM
tobiu added sub-issue #7465 on Oct 11, 2025, 8:47 PM
tobiu added sub-issue #7467 on Oct 12, 2025, 1:08 PM
tobiu added sub-issue #7474 on Oct 13, 2025, 11:20 AM
tobiu closed this issue on Nov 2, 2025, 10:30 AM