1. Overview for Hub Leads

In stage 3 we move from exploration into creation. Participants now begin building skills while continuing to develop their solutions. The emphasis is on applied learning: teams learn Cardano development tools and apply them directly to their emerging project ideas.
Hub leads act as both coordinators and mentors, ensuring that learning spaces are accessible, inclusive, and connected to real-world application.

2. Objectives of the Phase

By the end of this stage, participants should:

Understand the fundamentals of the Cardano development ecosystem.
Begin integrating Cardano infrastructure (SDKs, APIs, Plutus, Aiken, Mesh SDK, and SingularityNET/ASI tools) into their projects.
Establish collaborative workflows, including code repositories and version control.
Demonstrate progress toward a working prototype.

3. Facilitation Philosophy

Continue holding a regenerative orientation even during technical work. Skill development should remain connected to purpose and place. Encourage participants to see technology as a medium of service, not an end in itself.

Facilitation considerations:

Integrate reflection into technical sessions: ask how what they are learning connects to their community’s needs.
Create peer-learning clusters where teams share insights and teach each other.
Pair experienced developers with new learners to strengthen the hub’s collective capacity.
Maintain inclusivity: ensure that non-technical members also contribute through design, research, and documentation.

4. Core Activities and Flow

Weekly live technical sessions with regional mentors.
Asynchronous learning through recorded modules and open-source resources.
Optional GitHub challenges and code sprints.
Weekly peer-learning circles for progress sharing and troubleshooting.
Mid-phase review to assess progress and refine project scope.

5. Holding the Space

Hub leads should ensure that the technical learning remains relational and context-driven. Encourage collaboration over competition. Facilitate check-ins on well-being, group dynamics, and purpose alignment. When participants face technical frustration, bring them back to the “why” of their project.

6. Expected Outputs

Please see submission.

7. Documentation and Storytelling Guidance

Please see story-publishing.

8. Checklist for Hub Leads

Ensure all participants have access to training materials.
Schedule and host weekly technical sessions.
Facilitate peer-learning and reflection circles.
Review code repositories for activity and progress.
Gather mid-phase feedback and adjust support accordingly.