AI BUILDERS WEEKEND · MTSU · NOVEMBER 20–22, 2026Free registration is open ↗

HOURLY FOLLOW-UP 4 · NOVEMBER 2

Your workspace, within reach.

Phone navigation now shows the current organizer section in a labeled selector with all eleven sections. Switch directly to contacts, sponsors, drafts or research without searching a clipped horizontal strip. Existing view filters, edited drafts, command search and browser Back continue through the same workspace controller.

Open the organizer hub ↗

MERCH COLLECTION · NOVEMBER 2

All the shirts, together.

Browse 59 existing shirt concepts and 76 renders across the original capsule, learning studies and streetwear drop. Search, filter by theme, compare alternate/candid views and share a link to a specific design. This is a concept lookbook; ordering, pricing and final production are not announced.

Explore the merch collection ↗

HOURLY FOLLOW-UP 3 · NOVEMBER 2

Stay in your flow.

Unchanged organizer source refreshes now keep active tables and disclosures in place. Full public-source reads continue, and every content, policy or visibility change still applies. Open records update even when a field changes without a new revision number.

Official Luma and Slack entry pages were reached on November 2. The community guide adds existing-member sign-in, a fresh-invitation request and a separate event-registration route. Registration completion and invitation acceptance were not performed.

Open the joining guide ↗

HOURLY FOLLOW-UP 2 · NOVEMBER 2

Partnerships with a next step.

The organizer sponsor collection now separates owner and follow-up attention from prospect research. Find overdue dates or missing owners/actions, copy an exact filtered view and update the original record in the source workspace. Cash received, recorded pledges and proposed asks remain separate, with missing amounts labeled rather than treated as zero. Attention views respect existing outreach restrictions; no messages are sent.

Open sponsor follow-ups ↗

THE REASON BEHIND THE RELEASE

Useful references.
Practical improvements.

A deeper release across first-time builder onboarding, event clarity, partner conversations and the organizing workflow.

CONTINUED IMPROVEMENTS / NOVEMBER 2, 2026

A clearer route from information to action.

The new Launch desk exposes overdue work, missing owners, P0 priorities and declared prerequisites. It prepares a dated briefing for organizer review; it never assigns work, marks readiness or posts to Slack. Briefings stay frozen until explicitly refreshed.

Campuses & groups turns the existing contact research into searchable campus summaries. Human and group routes remain separate. Address counts are deduplicated case-insensitively, and shared-address filters help organizers avoid repeating outreach to the same inbox. Each campus can open an invitation draft with a placement label already selected. The campus navigation count reflects distinct groups, and compact page introductions keep the useful cards closer to the first screen.

Contact and sponsor details can now select the exact record in the existing email composer without repeating the search. Previously edited message text stays intact, and choosing the address remains explicit. Current-record policy, stage and attempt restrictions apply to the table/detail mail links as well as the composer. No message is sent or scheduled. Inside the working hub, header Search and Ctrl+K now search the full source workspace; public marketing pages keep their website search.

The planner and project-story tool now share an optional build notebook: a local, versioned .json file for carrying preparation and unfinished answers between visits. Opening a file previews it first. Plans supply only a title, audience and separately labeled intentions; they never fill in evidence of a working project. Story restoration is explicit, and nothing is uploaded or submitted.

The homepage now exposes arrival-source timestamps and manual refresh. Removing previously announced room or parking information clears it on the next successful source refresh. Changed event dates warn visitors on both the landing page and the event guide; equal date instants with different ISO offsets do not create a false warning.

Open the Launch desk ↗   Explore campuses & groups ↗

These tools use the existing public projection. They add no participant database, automatic outreach or new claim of institutional partnership. The contact index reflects recorded research, not a complete census or proof that an address is deliverable.

HOURLY FOLLOW-UP / NOVEMBER 2, 2026

The event comes first.

The landing page now presents the weekend’s details and agenda before the optional learning examples. Its hero links directly to that summary, where Sunday’s in-person presenter requirement is visible without switching tabs. The sticky page index follows the same reading order.

On phones, the three benefits are compact image/text rows with one complete, keyboard-reachable link each. Their titles, descriptions and images activate the same destination; responsive image hints fit the smaller thumbnails. Desktop artwork remains large, and all existing project ideas, planning tools and community material remain available.

Repeated command search in the organizer workspace now preserves the current query without adding duplicate browser-history entries. These changes were checked as navigation and layout improvements; no conversion or attendance increase is claimed.

FOR THE FIRST-TIME BUILDER

Start with a small win.

A four-step project plan, complementary team roles, a searchable event guide and take-away checklists make the first action easier to understand.

Try the project planner ↗
FOR THE ORGANIZING TEAM

Keep the source clear.

Task boards, focused filters, current recipient eligibility, preserved manual drafts and separately labeled contact routes make the existing workspace easier to use.

Open organizing tasks ↗

What the research supports.

This release adds 20 official event, learning and organizer references to the previous 20 AI brand references. These are editorial inputs, not a ranking or a measured conversion study. The new set was reviewed through primary-source content extraction; it was not visually inspected. Nine of the earlier AI sites received direct visual checks.

We applied a concrete first-project path, separate attendee and organizer journeys, clear pending logistics, practical sponsor choices and optional learning resources. We did not copy other events’ eligibility, staffing, meal, overnight or prize promises.

What is connected.

Organizer collections read the existing public operations API. A small arrival-information endpoint reads only selected event settings. Luma handles registration. Slack links open the existing workspace and invitation. Draft and sharing tools prepare text locally; they do not send email or post messages.

What still needs an organizer decision.

Room, access hours, approved parking lots and Friday pass pickup; submission route and deadline; confirmed mentor and judge coverage; final judging criteria and awards; food, loaners and consent arrangements. These remain source tasks, rather than promises in attendee marketing.

Delivery notes.

The static Vercel site uses content-fingerprinted scripts/styles, bounded responsive image delivery and original-image fallback. Native Vercel image optimization is metered under the existing hosting account. No plan or billing settings were changed.

20 ADDITIONAL PRIMARY SOURCES

Learning, events
and event operations.

Reviewed November 1, 2026. Open an entry for observed patterns, proposed adaptations and extraction limits.

21 / MLH Hackathon Organizer Guide

Organizer guidance

Observed

  • The guide separates planning into sponsorship, registration, logistics, judging, schedules, mentorship and after-event work.
  • Its website chapter separates registration, event explanation, sponsors, FAQ and support documentation.

Applied direction

  • Give organizers a concise readiness view with owners, source-linked tasks and unresolved decisions.
  • Keep the public page focused on attendee decisions; put deeper organizing work in the connected hub.

Generic sample policies are examples, not TNHackathons rules. In particular, do not inherit example food, age, team-size, travel, workshop, overnight or hardware promises.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
22 / Global Hack Week

Participant onboarding

Observed

  • The page links registration, schedule, FAQ, sponsorship and a community channel.
  • Upcoming editions are separated from example challenges and recordings of earlier sessions.

Applied direction

  • Offer a clear before-event path: register, find one small challenge, introduce yourself, form a team.
  • Keep live/next-event information separate from reusable examples and past material.

The current page lists November and December 2026 editions. Its free, worldwide model and Discord choice do not establish TN event eligibility, delivery or staffing.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
23 / TreeHacks

Event explanation and team formation

Observed

  • The page offers distinct about, track, speaker, sponsor and FAQ paths with an application action.
  • FAQ topics explicitly cover first-time coding, arriving without a team, price and participation eligibility.

Applied direction

  • Answer the no-experience and no-team objections close to registration.
  • Explain the team-building route and what different strengths contribute.

The live page is for February 2027. Flights, meals, sleeping areas, workshops, attendance and prizes belong to TreeHacks and must not be copied as TN promises.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
24 / Cal Hacks 13.0

Pre-event conversion and practical clarity

Observed

  • The page exposes an application timeline, venue directions, pre-event activities and a categorized FAQ.
  • Team formation and an introductory workshop appear alongside registration-related steps; some incomplete activities are labeled pending.

Applied direction

  • Make the route from first interest to team formation visible.
  • Show confirmed information and explicitly pending logistics separately; add orientation dates only after organizers confirm them.

Its team limit, student eligibility, awards, prior-work rules and sponsored activities differ from TN requirements. No conversion superiority was measured.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
25 / PennApps XXVII

Single next action

Observed

  • The current announcement gives the next edition status and presents name/email interest fields.
  • A direct contact address remains visible.

Applied direction

  • Keep one primary action obvious for the current event state.
  • If future-event interest capture is later implemented, provide a real destination and accurate confirmation before displaying a signup-success state.

Only exposed controls and text were reviewed; the form was not submitted. The displayed spring-semester announcement is not a verified date for the TN event. Do not add a pretend mailing list.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
26 / HackHarvard 2026

Event state and schedule

Observed

  • The current site leads with a completed-event message and a recap route, while retaining a future-sponsorship contact.
  • The program is organized by day and distinguishes activities requiring in-person attendance.

Applied direction

  • Use a date-aware event state and keep completed-event material distinguishable from current registration.
  • Label the real Sunday in-person requirement in text, not color alone.

hackharvard.io redirects to this official event site. The October 2026 edition is past. Its sponsors, award criteria, overnight limitations and scheduled sessions are not TN facts.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
27 / HackIllinois

Upcoming edition and support routes

Observed

  • The current landing page separates a countdown, an interest action, a detailed information site and an earlier-edition link.
  • The information site distinguishes general inquiries from mentoring/judging contacts.

Applied direction

  • Keep the next attendee action separate from mentor/judge participation.
  • Use a stable event guide and label earlier-edition information rather than mixing it into the current program.

The live landing page points to the 2027 season; some information-site footer text is older. Do not infer a current TN schedule from its countdown.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
28 / VandyHacks XIII

Inclusive contribution and practical FAQ

Observed

  • The introduction recognizes coders, designers and storytellers.
  • The FAQ exposes questions on first-time attendance, team formation, submissions, virtual participation, equipment and mentoring/judging.

Applied direction

  • Describe useful non-engineering roles with concrete examples.
  • Make eligibility, remote-building limitations, team expectations and what to bring easy to find.

The page is for March 2027 and says applications open soon. FAQ answer execution was not tested; exposed question topics are the verified observation. Its college-only context does not restrict the TN 18+ audience.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
29 / HackDavis 2026

Honest event state and varied recognition

Observed

  • The site clearly says registration is closed and gives separate empty states for live and upcoming activities.
  • Prizes can be filtered by categories including design, business and nonprofit work, with eligibility explanations.

Applied direction

  • Use explicit empty/pending states instead of fabricated activity.
  • When TN awards are confirmed, explain eligibility and recognize multiple contribution types; until then, keep the prize target clearly a target.

The page shows a completed 2026 edition. None of its prizes, award eligibility, sponsors or guaranteed opportunities are transferable to TNHackathons.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
30 / NASA Space Apps Challenge — NASA Science announcement

Role-inclusive invitation

Observed

  • NASA describes collaborative work for programmers and nonprogrammers, naming scientific, design, storytelling and technology contributions.
  • The invitation connects a real-world challenge, open data, teams and registration.

Applied direction

  • Frame the TN event around solving a useful problem with complementary strengths.
  • Show a small project outcome and why research, design, writing and business judgment matter alongside coding.

This is an October 15, 2026 official announcement, not a visual review of the Space Apps website. Its November dates, all-ages eligibility, scale and challenge themes are not TN event facts.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
31 / CS50’s Introduction to Artificial Intelligence with Python

Structured learning path

Observed

  • The course publishes prerequisites, numbered topic sections, hands-on projects and a short lecture-to-project workflow.
  • Learning materials, community help and optional credential routes are distinguished.

Applied direction

  • Give a beginner a short sequence ending in a demonstrable artifact.
  • If offering optional technical study links, label prerequisites and keep them separate from event admission requirements.

This course expects CS50x or substantial Python experience. It is not a prerequisite for the TN weekend, and a weekend does not confer its certificate or expertise.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
32 / Grow with Google — AI training

Goal and audience paths

Observed

  • Training is grouped by practical audiences and outcomes, including educators, students, small businesses and job seekers.
  • Cards expose course length/type and distinguish learning more from starting a program.

Applied direction

  • Let visitors choose their goal and see a fitting small project.
  • Set clear expectations about a short first step, a weekend prototype and longer-term learning.

Program offers, subscriptions, credentials, costs and labor-market statistics belong to Google and were not verified for use as TN claims. Do not label every linked course free.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
33 / fast.ai — Practical Deep Learning

Practical artifact before deeper theory

Observed

  • The page organizes lessons and summaries with a contents navigation and direct first-lesson action.
  • It states that learners need some coding experience and describes practical model-building/deployment outcomes.

Applied direction

  • Start with one visible working flow and let visitors explore deeper explanation afterward.
  • Keep an optional advanced-learning path without implying that beginners need to complete a long technical course first.

The main course text identifies a 2022 recording. Use its educational structure, not its tool versions as current 2026 technical advice.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
34 / Google Machine Learning Crash Course

Modular self-paced learning

Observed

  • The page offers separate start, module-browse and prerequisite actions.
  • Modules are self-contained, while newcomers are advised to follow an order; exercises and interactive explanations are named.

Applied direction

  • Provide a recommended first-time route and a browse-all route.
  • Organize project help into small, independently useful steps with a clear next action.

This is technical ML education. Its module content and prerequisites are not event rules, and completion is not promised during the weekend.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
35 / Hugging Face Learn

Topic-based learning library

Observed

  • The catalog separates courses by concrete subject areas such as language models, agents, robotics, audio and computer vision.
  • A cookbook route offers reusable worked material alongside full courses.

Applied direction

  • Filter builder resources by intent or project type.
  • Distinguish a short reusable worksheet from a longer external course, and offer both without making the library a wall of undifferentiated links.

Catalog/control structure was reviewed; individual enrollment, pricing and lesson prerequisites were not tested. Course availability may change.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
36 / MIT App Inventor

Beginner-to-advanced project onboarding

Observed

  • The page presents a first-app action and groups tutorials into beginner, intermediate and advanced levels.
  • Project examples include a short description, starting expectations and a clear way to open the build.

Applied direction

  • Use a first-project pathway with a manageable outcome, input, useful output and a test.
  • Show how someone can progress after the event without promising instant expert status.

Its browser/app setup and course time estimates belong to App Inventor. TN tool access, hardware and workshop staffing remain separately confirmed facts.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
37 / Microsoft AI for Beginners

Curriculum with boundaries and reusable practice

Observed

  • The official repository organizes lessons with practical labs and quizzes, provides translations and names material it does not cover.
  • Setup and supporting resources are separated from the lesson sequence.

Applied direction

  • Give project briefs a clear scope, test cases and honest limits.
  • Make preparation materials reusable and clearly label optional technical setup.

The rendered curriculum root was not readable, so this observation is of Microsoft’s official repository README. Its longer curriculum is not a weekend completion promise.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
38 / The Odin Project

Learn, build and connect

Observed

  • The page explains a progression from curated study through portfolio projects to community support.
  • Full curriculum browsing and an initial get-started action are both exposed.

Applied direction

  • Connect learning, a project someone can try and collaborators in one coherent journey.
  • After the weekend, suggest an honest project writeup, next iteration and continued community participation.

This is a web-development curriculum reference, not an AI course or evidence that the TN weekend leads to employment. Testimonials and hiring claims were not reused.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
39 / Day of AI

Time-based entry and critical thinking

Observed

  • The homepage routes visitors by available time, from a short activity to a longer course.
  • It separates professional-learning and family/community resources, and describes AI literacy without requiring AI-tool use.

Applied direction

  • Offer a small preparation step and a longer build plan instead of an all-or-nothing learning burden.
  • Help participants question outputs and explain their own decisions, not merely generate a result.

This program primarily serves educators and K–12 learners. Its audience and partner claims do not alter the TN event’s adult 18+ policy. No signup was submitted.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗
40 / MLH Sponsorship Prospectus

Sponsor decision support

Observed

  • The guide recommends a short, legible prospectus with event basics, a clear purpose, sponsorship tiers and a custom-package contact.
  • It distinguishes basic publicity/recruiting benefits from higher-tier additions.

Applied direction

  • Give sponsors a concise comparison, specific proposed benefits and a direct human inquiry route.
  • Provide a downloadable discussion brief while labeling packages and funding as proposals until agreed.

The guide’s pricing ratios and prescriptive email-link advice are opinions/examples, not adopted TN policy. Keep the user’s proposed $200/$500/$1,500 discussions and do not promise attendance, recruiting outcomes or unapproved benefits.

Not performed. Official content and exposed control labels only; no claims about unobserved typography, color, animation or executed interactions.

Read the official source ↗

THE EARLIER AI REFERENCE SET

Twenty brand references.

Source content and visual observations were tracked separately. No reference artwork or brand marks were reused.

Download the new research notes ↓
FIND YOUR NEXT STEP

Search TNHackathons.

YOUR FIRST BUILD BRIEF