Mission and objectives
Mission Statement Chipco Preserve is committed to protecting fragile ecosystems, advancing sustainable agriculture, and empowering Indigenous and Veteran communities through education, advocacy, and stewardship. We honor cultural heritage, foster resilience, and build connections between people and the natural world to ensure a healthier future for all. Objectives Uplift Indigenous Voices: Partner with Indigenous leaders to preserve cultural knowledge, promote sovereignty, and share traditional ecological practices. Support Veterans: Provide opportunities for Veterans to engage in land-based healing, conservation, and community leadership roles. Protect and Restore Ecosystems: Safeguard native habitats and species, restore degraded landscapes, and model regenerative farming practices that integrate food production with biodiversity. Educate and Inspire: Offer programs, workshops, and public engagement that connect communities with conservation, cultural heritage, and sustainable living. Foster Community Engagement: Involve schools, families, and volunteers in hands-on stewardship projects that cultivate responsibility and awareness. Ensure Organizational Sustainability: Strengthen long-term impact through transparent reporting, strategic partnerships, and diversified funding.
Context
How does this task contribute to Chipco Preserve’s objectives? Converting our Godot 4.2 game into a browser-based version directly advances Chipco Preserve’s education and outreach goals by making our learning content more accessible, easier to share, and easier to use in classrooms and community settings. A web-playable game removes the barrier of downloading software, which increases participation among students, educators, and supporters. It also supports Chipco’s broader mission to promote conservation literacy and engagement by turning our educational materials into interactive experiences accessible from anywhere. What is the background context into which this volunteer contribution will fit? This task is part of Chipco Preserve’s larger effort to build a digital education ecosystem that includes: -short wildlife micro-courses (Wix-based, like our existing bat course), -community storytelling and public engagement (e.g., “Stories of Care”), -downloadable learning materials for educators, -and interactive online learning tools, including games. The Godot game is intended to function as a public-facing learning experience that complements our courses and outreach content. Once the game is browser-based, it can be embedded or linked from our website and promoted through social media as a mission-centric tool for education, engagement, and community participation.
Task Description
Project Title Convert Godot 4.2 Game to Browser Playable (HTML5/Web Export) + Deployment Guide Project Overview Chipco Preserve has an existing Godot 4.2 game currently packaged for Windows (e.g., .exe + .pck). We want to make it playable directly in a web browser so educators, students, and supporters can access it without downloading an app. The online volunteer will convert the project to a web export, test it across devices, and provide deployment instructions. Primary Goal Produce a working browser-based version of the game that loads reliably from a standard web host (Wix site, subdomain, or a simple static host), plus a clear handoff package so Chipco can publish and maintain it. What the Volunteer Will Do (Specific Responsibilities) 1) Intake & Environment Setup Review what Chipco provides (Godot project folder). Install and configure Godot 4.2 and the required export templates. Confirm the project opens and runs locally in the editor. Output A short “Project Intake Notes” summary of what was received, what’s missing (if anything), and the export plan.
2) Web Export Configuration (Godot 4.2) Enable and configure the Web/HTML5 export settings for Godot 4.2 (or newer version if necessary). Set correct: canvas size/stretch settings input handling (mouse, keyboard, touch if applicable) audio behavior (autoplay restrictions, user gesture start) performance settings (quality vs speed, texture compression if needed) Ensure any plugins/addons used by the project are compatible with web export. Output Web export preset created and saved in the project. Notes on any compatibility changes required.
3) Troubleshooting & Adaptation for Browser Constraints The volunteer will identify and fix common issues that prevent web builds from working, such as: file access paths (browser sandbox limitations) threading limitations (if used) shader/graphics features that don’t translate well to the web memory/performance constraints (large textures/audio) fonts/resources not loading due to casing or import rules Output Updated project settings and/or minor code adjustments required for web compatibility. A change log describing modifications.
4) Build, Test, and Validate Produce the web build artifacts (typically .html, .wasm, .pck, plus supporting files). Test in at least: Chrome (desktop) Firefox or Edge (desktop) Mobile browser sanity check (if the game is intended to be mobile-friendly) Verify: -game loads and starts reliably -controls work as expected -audio plays after user interaction -no broken assets or missing textures -acceptable loading times -Output -A tested web build folder ready to upload. -A short testing report (what was tested + known limitations).
5) Deployment Plan + Handoff Package Volunteer will provide a clear publishing path for Chipco, based on your chosen host. Options might include: Wix (embedding via iFrame or hosting files on a connected domain/subdomain) GitHub Pages / Netlify / Cloudflare Pages (static hosting) Any basic web host (upload build folder) Output “How to Deploy” step-by-step guide (written for non-developers), including: where to upload files, required folder structure, how to embed the game in a webpage, any caching/CORS considerations, and how to update builds later
Deliverables (End of Project) 1. Browser/Web export build of the Godot 4.2 game (HTML/WASM/PCK build folder). 2. Export preset saved in the project (so Chipco can rebuild later). 3. Testing report + known limitations list. 4. Change log of any modifications required for web compatibility.
Daily Logistics (How the Work Will Run)
Communication Primary: Email or UN platform messaging (asynchronous) Shared files: Google Drive/Dropbox folder (Chipco will provide) or direct download Optional: brief messages for quick questions/answers
Status Updates Volunteer provides 1-2 brief status updates per week explaining: What was completed, What’s next, and Blockers/questions
Schedule: Week 1: intake, access, feasibility, export plan Week 2: troubleshooting decisions, mid-test review Week 3: deployment walkthrough + handoff Availability Requirements No fixed daily hours required. Volunteer should respond within 24–48 hours to unblock progress. During final deployment week, faster turnaround (same-day once or twice) is helpful.
Competencies and values
Living conditions and remarks
This position is no longer open.
