> For the complete documentation index, see [llms.txt](https://wiki.tinkerhub.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.tinkerhub.org/campus-community/whats-new-in-2026.md). # What’s New in 2026 ### Scaling Without Losing Our Core Values TinkerHub is growing — in reach, in participation, and in the number of active learners across campuses. But growth doesn’t mean compromising what we stand for. As we build systems and structures to support thousands of learners, we’re ensuring that they remain people-first — designed with empathy, inclusivity, and accessibility. We aim to scale without losing the warmth, care, and community that brought us here. *** ### Never Give Up (Never Alone) Things might feel heavier right now. AI is moving faster that we can track, there's chaos in the world and deadlines are piling up. It's easy to feel overwhelmed, even to quietly give up on things you used to love. But as makers, we know what to do when a build fails or a circuit won't work. We ask someone who's seen something similar before. We're strong because we support each other. So this year, when things get hard, we don't freeze or quit. We reach out, we check in on each other, not just the project they're working on. We help the person next to us, and let them help us back. We never give up, and we never do it alone. {% content-ref url="/pages/AWjdQiq0YruFjIWw0RLx" %} [2026 Theme](/campus-community/2026-theme.md) {% endcontent-ref %} *** ### Multidisciplinary by Default TinkerHub in 2026 is open to all — not just programmers. We welcome and support **designers, storytellers, researchers, entrepreneurs, artists, farmers, and engineers** — anyone curious and committed to learning. We believe that real-world problems require collaborative, cross-disciplinary thinking, so our programs are intentionally designed to bring diverse minds together. *** ### Build Systems with Care We’re critical of outdated systems that don’t serve learners — but we approach change with responsibility and intention. We believe it’s possible to challenge the status quo while remaining kind and constructive. Instead of reacting with frustration, we choose to build better systems — ones that are inclusive, transparent, and sustainable. *** ### Mentors Who Learn and Build With You Great mentorship doesn’t come from one-way lectures. We are building a mentor network of practitioners — people who code, design, make, and teach alongside learners. These are professionals and peers who are willing to listen, share real stories, and help debug both projects and thought processes. *** ### Our North Star: Did You Learn Something? Whether it's a meetup, a hackathon, or a campaign — our primary metric is **learning**. Every initiative we run is anchored in this question:\ \&#xNAN;**“Did the people who attended actually learn something new?”** That’s what guides our decisions, defines our success, and shapes what we do next. ### Scaling Without Losing Soul We’re growing — not just in numbers, but in depth.\ But here’s the deal: **we won’t trade warmth for efficiency.**\ We’re building systems that scale *with tenderness* — people-first systems that grow with you, not past you. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.tinkerhub.org/campus-community/whats-new-in-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.