Precision Nutrition — Extracted Board Text

Source: Precision Nutrition.pdf (a single giant 34224×19632pt page — a Miro/FigJam-style planning board exported to PDF). Text below is cleaned up from raw extraction and organized by the board's sections, in left-to-right / top-to-bottom order. Two reference screenshots (mockups of the "Prep Your Pantry" page, used in the Aug 13 usability discussion) were supplied separately as PNGs and aren't reproduced here.

1. Kickoff Meeting (July 28, 2026)

Resource links

• https://eat-move-save.extension.illinois.edu
• Shared Drive folder (Google Drive)
• More resources on Teams shared folder
• Gamification research from Lisa (ChatGPT share link)

Notes — prefer Teams for both communication & documentation. (Leigh)

Current status of the app (Leigh)

• Has a previous design; a pilot version of the app exists (open to scrapping it and starting fresh)
• Collected user feedback from community members, not Extension employees
• Trained UIE staff (~20 people); they used the app with their programs; asked community members to create accounts, log in, check into programs, give feedback

Goal of the pilot testing (Leigh)

• Can user create an account? Check in to a program? Use their account to check into a class?
• Can they recognize their attendance and get points/rewards in some type of class record?
• Can user see what they've attended / what their transcript looks like?
• Can they indicate participation in texting program / newsletter program (currently unavailable)
• All of these were accomplished

Learned (Leigh)

• The tangible reward system was not feasible, needed, or wanted — hard to track, and people didn't care
• Need to transition to non-tangible rewarding mechanisms
• An intern reviewed other health behavior-promoting apps to look at app structure, theoretical basis, and how they rewarded people for changes

Find Food IL vs. UIE audience (Leigh)

• Find Food IL: faces a specific audience (limited-resource families) for a specific funding source
• UIE: serves families across income brackets
• Caitlin: not sure how to accommodate these different needs
• Matt: could have a user intake quiz to figure out who this person is and customize the interface for them

Tech Details (Leigh)

• Might need to move "Events Manager" from AWS to internal servers
• Build things in a portable way before knowing which infra will be used
• Could start from user-profile-management work before design team finalizes features
• Not sure where new mobile app should live — AWS or campus
• Find Food IL uses an iframe; unclear how that works in a mobile app

Timeline (Leigh) — two releases for the year, at 6 months and 12 months; might need to show concepts around the 3-month point (from Jennifer)

Next step (Leigh) — Caitlin to find out if the old app is live and share a PowerPoint summary of the pilot

Background

• Current website: https://eat-move-save.extension.illinois.edu/
• Pilot version: create account → email confirmation → confirm email (Leigh)
• For events: participants could see programs in their area (tied to what staff created in Events Manager); could register or indicate plans to attend (Leigh)
• For staff: early mockups of creating an event; the live program now exists (Leigh)
• For activities: heavily dependent on what the SNAP-Ed program was (Leigh)
• Original idea: participants have their own account and can do everything themselves from their own device (Leigh)

2. EAT·MOVE·SAVE Plus (for SNAP-Ed) — Findings from User Research

Competitive analysis of healthy eating & physical activity apps (spreadsheet linked)

Apps reviewed: Lifesum, MyFitnessPal, Walkr (Fitness Space Adventure), Pokémon GO, Eat Right Now, Cooking Matters, Kitchen Stories, My H-E-B (Texas only), WIC Smart, Change4Life, Fabulous (Daily Routine Planner), Loop Habit Tracker (best free app), ChefTap (recipe clipper), Cozi, Noom, Yummly

Theory-based behavior change models used | Theory | # apps | Examples | |---|---|---| | Transtheoretical Model | 9 apps | — | | Health Belief Model (HBM) | 1 app | MyFitnessPal | | Social Cognitive Theory | 3 apps | Walkr, Pokémon GO, Fabulous | | Social Ecological Model | 1 app | Pokémon GO | | Theory of Planned Behavior | 7 apps | — | | Unified Theory of Acceptance and Use of Technology (UTAUT) | 1 app | WIC Smart | | Self-Determination Theory | 1 app | Fabulous |

Strategies/techniques: material incentive behavior, social comparison, social support, demo of the behavior — all 4 used together in Kitchen Stories.

3. Early Brainstorming

Motivate people toward a healthier life via daily goals and long-term goals. (Leigh)

Eat

• Create a community: sharing what they eat
• Leaderboard of top-used recipes
• Occasional themed campaigns (e.g., apple & peanut butter week/day)
• Use seasonal food info from the website; local food resources

Move

• Community: sharing exercise activity
• Leaderboard: top participated activities
• Gamification: collect points to grow something (a digital plant) — e.g. 5 pts for water, 10 for sunlight; the flower dies if you stop eating healthy / exercising

Gamification: Personalized goal setting

• Goals should be specific, achievable, relevant to the user's health status/environment, e.g.:
  • Eat vegetables on five days this week
  • Drink one fewer sugary beverage each day
  • Cook one healthy meal at home this week
  • Complete three walking sessions this week
• Encourage repeated behaviors via streaks/milestones, e.g.:
  • Log meals for 7 consecutive days
  • Meet fruit-intake goal for 2 consecutive weeks
  • Complete 4 healthy challenges within a month
  • Achieve exercise goal for 3 consecutive weeks
• Purpose: not to pressure an unbroken streak, but help users recognize repeated healthy behaviors are becoming lasting habits

Gamification: Other ideas (digital plant)

• Users earn points by completing healthy habits, which grow a digital plant: +5 water it, +10 give sunlight, +15 add nutrients, +20 unlock a new leaf/bloom
• Consistent healthy eating/activity → plant grows from seedling to thriving flower; stopping → plant wilts/loses leaves; returning to habits → recovers and blooms again

4. Meeting (Aug 8, 2026) — Kate Arneson joins

Existing resources / current progress

• Landing page alive but disabled: https://myeatmovesave.org/
• Another page: https://eat-move-save.extension.illinois.edu/
• Pilot-program pages originally designed off the SNAP education program (Kate Arneson)
• Originally wanted participants to: create an account, check into events (Kate Arneson)
• For events: participants could see area programs (tied to Events Manager) and register/indicate plans to attend (Kate Arneson)
• Since then, Extension built out systems for checking users into events (Events Manager + iPad) (Kate Arneson)
• Has a live app in the app store to check participants into class — offline app on staff iPads: staff enter their program, check participants into class (Leigh)
• So self-check-in via the app/website would just be a "nice to have" — core functionality already covered by existing systems (Kate Arneson)

Findings

• Tangible rewards (physical mailed items) were too complicated; people didn't get it. Virtual rewards/badges lived on and remained motivating for behavior change (Kate Arneson)
• Don't like the current look/feel — especially photos of people in masks; need a fresher, more welcoming, modern-audience look (Leigh)
• Upcoming events UI was like a swipe left/right; open to other ideas (Leigh)

Earlier naming ideas

• "EAT·MOVE·SAVE" — generalized content for everybody
• "myEMS" — personalized environment; still access to generalized content while logged in
• Track engagement; future goal: outcome evaluation on relationship between content/event engagement and behavior change (Leigh)

Staff-side workflow

• Create-event page for staff → "myinep" portal: access learning resources + Events Manager (already implemented workflow)
• Events created in portal go live in the offline app at their scheduled time; staff use iPad to check participants in; after event, iPad connects to wifi and data syncs back to the portal (Kate Arneson / Leigh)
• Events can include multiple sessions; can schedule each session in a series with lesson info (Leigh / Kate Arneson)
• Apple currently reviewing their app store submission; iPad used for check-in now, participants might self-check-in via app/website in future (Kate Arneson)
• Eventually this system should connect to the larger reporting system via an API

Types of content on website: recipes (with possible reviews/comments/"tried" tracking), grocery store games, articles (Kate Arneson)

Competitive analysis done ~5 years ago on healthy eating apps by an intern (spreadsheet) (Kate Arneson)

Scope for this round of design/development — open question (Kate Arneson)

• App look & feel could be modernized (website already updated; mask photos are ~5-yr-old COVID-era)
• Can users get to myEMS from the main website? After login, still want access to all main content
• Events Manager & myinep need migration from AWS to internal servers; may need rebuilding, which could limit integration scope
• Maybe focus on more fun features for now (content access, gamified virtual rewards) since core functionality is/will be covered by existing systems
• From a data perspective: nice to have users logged in when accessing content, so Caitlin can tell a data story about user impact/interaction
• Reward-points system for eating/exercising etc.: doesn't exist yet; would like to move that direction. Lisa: figure this out soon — could users define their own goals tied to rewards?
• Goal: feel cohesive within the Extension ecosystem but let users personalize their experience (future: personalized nutrition chatbot)
• Much later: could include personal devices/wearables/biometric data (e.g. smartwatch)
• Focused on early-phase behavior change (intention, motivation), not verification/completion of goals. Funders may want to see how users changed behavior because of X.
• Engagement/motivation ideas: gamification, themed campaigns (seasonal nutrition), leaderboards (top recipes/exercises), community sharing/ratings
• Intern's old spreadsheet may also have ideas on theories/patterns used
• myEMS should generally align with the EMS website
• Somewhat follow UIUC branding guidelines but have been creative (different blue/orange, also yellow/green)
• Mascot/character graphics available in Teams — found to work better for engaging users

Primary thing: participant-facing experience — start to engage with digital content (Leigh)

• Use existing Extension IT system for user signup
• Extension has its own user account system (offline app): check people into class, register attendance, collect demographic info

Long-term vision: explore how Extension education/resources can positively impact community members' lives; provide a personalized experience based on individual situation (Leigh)

Overall approach: blend in-person traditional education with newer digital gamification (Leigh)

High-level design direction (short-term): encourage account creation and content engagement; support early behavior change rather than demonstrating long-term health outcomes (Leigh)

Possible detailed design direction: users set up personal goals (maybe during account setup) and get rewards; this stage could use manual self-reporting (later, automated data sync) (Leigh)

Confirmed with IT: can add additional questions to the registration process (Leigh). Caitlin: but wants visual matching with what we're doing.

Brainstorming: During account creation, users first select their primary goal — Save money / Exercise more / Eat healthier / or all of them. Progress is then personalized:

• Eat healthier: earn progress via recipe/nutrition content
• Exercise more: earn progress via workout/fitness content
• Save money: earn progress via grocery-shopping content/activities

5. Reference Apps

Spreadsheet of Healthy Eating Apps from Intern (5 years ago) (linked)

Behavior Change Support Strategies (apps grouped by primary strategy; * = uses multiple approaches)

• UNDERSTAND ("help me understand why I behave this way and what I can change"): Eat Right Now, Noom*, WIC Smart, Change4Life
• START & SUSTAIN ("help me decide where to start and keep doing it"): Lifesum*, MyFitnessPal*, Loop, Fabulous, Noom*
• ENABLE (reduce practical barriers): Kitchen Stories, Yummly, ChefTap, My H-E-B, Cozi, Lifesum*, MyFitnessPal*

Summary

• Common theories: Theory of Planned Behavior, Transtheoretical Model
• Common features: planning, lists, integration of external data (scraped recipes, wearables, health/fitness apps), community (shared views/support), progress tracking & feedback, personalized recommendations, education & guided learning
• Common reward systems: non-tangible (feedback, badges/stickers/"achievements"), tangible (physical items, money), social recognition & community participation
• Open questions: several of these apps no longer exist (5 yrs later). How will myEMS sustain engagement? What does it offer that the internet/other apps/AI tools can't? How does it integrate Eat/Move/Save into one cohesive experience? What role should it play (awareness, getting started, reducing barriers, or a mix)? Can it encourage healthy behavior without feeling like a "health assignment"?

Other apps (not on original spreadsheet)

• Eating: MyFitnessPal (comprehensive, pricier), Lose It! (simpler/cheaper), Noom (psychology-backed weight loss), Cronometer (science-backed calorie counting)
• Moving: Nike Training Club (free workout library), Strava (social/competitive), Fitbit (wearable integration), Apple Fitness+ (Apple Watch/activity rings)
• Saving: YNAB ("give every dollar a job"), local deals (Flipp, Flashfood, Too Good To Go), cash-back (Ibotta, Fetch, Rakuten), community resources (food shelves/pantries, Buy Nothing groups, Olio)
• General habit building: Fabulous (Duke behavioral econ lab; ritual + coaching), Loop (visual calendar-grid habit tracking), Habitica (RPG gamification), Finch (self-care/virtual pet)

6. Design Focus Areas (Summary)

• Account creation/profile — may include indicating personal goal(s) (Kate Arneson)
• Content engagement — goal: support early behavior change; strategy: gamification; constraint: collect engagement "data" so a behavior-change story can be told (Kate Arneson)
• Design strategy questions (Kate Arneson): How will myEMS sustain itself and keep engaging users? What does it offer that the internet/other apps/AI tools can't? How does it integrate Eat/Move/Save into one cohesive platform/experience?

7. Meeting (Aug 12, 2026)

Notes from Zoom — copy/paste from Beth's chat: Badging/point ideas

• Daily/weekly streaks — log in, do at least one thing in the app (access one piece of content?)
• Choose a goal (preset menu); make a new recipe; eat a new fruit/veg; try a new food
• Make a shopping list before going to the store; plan weekly breakfast/lunch/dinner meals
• Add 10 minutes of favorite activity; avoid impulse purchases at the store
• Badges based on content type used: Recipes, Grocery Store Tour, Local Foods/Illinois Grown, Cooking Smart, Meal Planning, Moving More, Movement Library, Save-Making a Plan, Using Budget Calculator, Pantry Prep, Using Scrap Veggies (regrowing, making broth, etc.), Find Food IL, Share with Others (social media? SMS/text?)

(More detailed notes in linked Google Slides deck)

Target user groups (Leigh)

1. Participants who attend Extension education programs (in-person or virtual) and use the app — primary group; already engaged with the education program before using the app
2. Participants who only use the app
3. Open question: how does this fit the overall scope of learning for people experiencing both vs. just the app?

Behavior Change Model (Leigh)

• Less suitable (per Caitlin): Transtheoretical Model — better suited to the overall program than the app itself
• Suitable for app dev (per Caitlin):
  • Social Cognitive Theory — could become features like challenges/leaderboards; focuses on learning from/observing others
  • Theory of Planned Behavior — focuses on intention → action: "This is what I want to do, and this is how I'm going to make a change."
• Still being explored (per Beth): Self-Determination Theory — more about user retention/app usage; 3 basic needs (may not all be feasible this round):
  • Autonomy — long-term growing mechanism
  • Confidence — rewards and/or monitoring system
  • Relatedness — community, messages, sharing
  • (Beth will share an article about this theory later)

Design focus

• Want to focus on all 3 pillars: Eat, Move, Save
• Create a personalized journey — personalization is the best first angle, and may help later funding applications

Brainstorming ideas (design & dev)

• Caitlin: Focus on one theory (e.g. Theory of Planned Behavior). Understand users' goals, guide them toward the most relevant content, keep all other content accessible. During onboarding, ask what types of goals they have / what content they'd like to see most; initially show only related content; after accomplishing things, prompt them that other content exists.
• Lisa: Use onboarding to understand interests/goals but not to restrict what they can see. Create a recommendation/push system that surfaces content based on interests/goals — users shouldn't have to hunt for content; existing content can resurface over time to feel fresh/personalized.
• Caitlin: They can access everything, but we could show a small window based on their specific goals.
• Matt: Tech side could tag the content.
• Caitlin: Maybe using AI, but needs manual review — not sure if that's in scope for this round.
• Capture-behavior ideas: Beth's list above; interact with EMS content; streaking concept (check into the app — very common).
• Caitlin: Pre-programmed motivational statements; if user says "no," show encouraging messages.
• Caitlin: EMS website should provide an entry point into myEMS — maybe a popup prompt.
• Matt: Early phase — simple prompts directing users to relevant website content and point-earning opportunities. Long-term vision — make website and app experience more integrated; users earn points/see badges/track progress while browsing the website. Full integration would need more coordination with the web team and is likely beyond end-of-September scope.

8. Internal Meeting (Aug 13) — Screenshots / Usability & Layout Suggestions

Reference: Illinois Extension Events page (https://extension.illinois.edu/global/events)

Usability/Layout suggestion examples (annotations on a mockup — see uploaded reference images)

• Non-standard anchor links — image/text treatment evokes something that might link to a new page, vs. more-standard anchor links to sections of the same page
• Section title placed above image
• Header includes: # views, "trending," est. reading time — maybe some content types could also have a "rating," which could be included in page-level info too
• Tips called out with a distinct visual treatment from main article content (the FIFO tip wasn't easily visually discernible — very small section)
• Opportunity to add interactive content (e.g., checklists within an article, or consolidate to an article-level button indicating the user has tried these tips, etc.)
• "Back to top" buttons for easier mobile navigation of long pages (this mockup includes all content from the corresponding existing EMS page)
• Checklist could provide opportunity for actual checkbox interaction for more content engagement
• Comment area for community building; maybe some content types also have a "rating" component

Navigation options comparison

9. Brainstorming from/after 8/13 Internal Meeting (Brain Dump)

Organized under the three theories in play:

Theory of Planned Behavior — more for the app; focuses on intention → action ("This is what I want to do, and this is how I'm going to make a change.")

Self-Determination Theory — Autonomy (long-term growing mechanism) → Goal-setting (onboarding)

• Ask a small set of introductory questions about what brings the user to myEMS and what they're interested in improving
• User picks an avatar (if supporting an other-user-facing profile)
• Free-text custom user-created goals (self-reported, future)
• User picks which pillar(s) — Eat, Move, Save — to focus on
• User selects pillar-specific pre-written goals (list of specific pre-written goals, e.g. "cook one healthy meal this week," mapped to existing content actions — not free-text)
• Surfacing relevant content: recommended events; recommended content (articles, recipes, exercises, etc.); seasonal content recommendations (e.g. seasonal produce on existing site); recommendations based on users with similar interests; recommendations based on onboarding goals/interests; recommendations based on trending/popular content/aggregated user metrics
• Recommendation based on an Eat/Move/Save tag (binary) / score (continuous) assigned to content or events (possibly done by AI)
• Content recommendations based on national/international awareness days, events, holidays, cultural relevance, etc.
• Personalized nutrition chatbot (Vlad) — future, or maybe demo only
• Follow-up recommendations if a user "checks in" on a goal and is looking for support
• Incorporate content from other IL Extension services (events, podcasts, blog posts, etc.)

Self-Determination Theory — Autonomy (long-term growing mechanism) → Earning "points"

• Mark recipe as tried; open recipe; open article; view content = 1pt
• Meaningfully consume content (scroll/watch through, download activity) = 3pt
• Mark as tried = 5pt
• Leave a review on a recipe
• Full points for chosen pillar(s), half points for other pillar(s); extra bonus points for seasonal-themed content
• Leave a comment on a recipe/article/exercise — pulls points for all pillars, but recommended content makes it more likely the user engages with selected pillar(s)
• Access/download attachments or resources linked from an article/page
• Integrate wearables for data collection (future)
• Point-earning activities: in-app (read an article, view a recipe, complete educational content) and real-world (eat breakfast, drink water, try a recipe, take a walk)
• Completing curated goals (pre-written, or self-written in future) earns points beyond its base action (e.g., marking the 3rd recipe as tried for the goal of trying 3 recipes in 1 week)
• Photo-based food logging (future)
• Credit for attending an event tied to the event check-in mechanism (future)
• Read full recipe / mark recipe as tried / point for opening the app
• Read full article / "check in" on goal
• Watch full exercise video / mark exercise video as tried
• Add rating / add comment / mark article tips as tried
• Limit on points earned per day (to support long-term engagement rather than binge-earning)
• Points assigned based on quantity of interaction types (not type of interaction) — works with a tiered badge system that splits different interaction types into different badge categories

Social Cognitive Theory + Self-Determination Theory (Relatedness — community, messages, sharing) → Fostering community

• Events: comments/discussion — converse/share media with other attendees and leaders
• Leaderboard — don't want to do this exactly (creates comparison/competition feeling), but maybe a more community-oriented option exists
• Article comments; recipe rating; user ability to share activities/engagement (maybe future); exercise rating; recipe comments; community forum spaces; exercise comments
• Display accumulated user metrics on top of content (views, tried, downloaded, trending/popular, etc.)
• Ability to view others' profiles and their Eat/Move/Save "personality" (e.g. spider-plot idea)
• Ability to leave rating and/or comments on relevant content types

Self-Determination Theory — Confidence → Rewards and/or monitoring system

Self-Determination Theory — Autonomy (long-term growing mechanism) → Visual progress

• Visual representations of user's own progress; streaks (best & current); reports (weekly/monthly/etc.) of activity/engagement
• Types of engagement for calendar color-coding: open app/log in, points earned toward badge, badge completed, completed goal, attended event
• Events "passport"; user-profile "spider" plot of Eat/Move/Save "scores"; badges (+ progress indicator toward next badge)
• Badges — generic point levels: Level 1: 1, Level 2: 3, Level 3: 5, Level 4: 10, Level 5: 20, Level 6: 50+
  • General/cross-cutting: daily streak (open app ≥1×/day) — 7 days, 1 month, 1 year, 2 years, etc.; weekly streak (open app ≥1×/week) — 1 month, 3/6 months, 1/2 years, etc.
  • Goals: created, check-ins completed, completed — all generic levels; events attended — generic levels
  • Eat: consuming content, trying recipes, fostering community (rating/comment) — generic levels
  • Move: consuming content, trying exercise, fostering community — generic levels
  • Save: consuming content, trying tips, fostering community — generic levels
• Calendar heatmap of activity/engagement
• User "plant" visualization of reward points; user garden with 3 beds (Eat, Move, Save)
• User's plant doesn't die (too harsh) — maybe weeds just grow instead
• Ability to customize plant ("free" or "paid" with points)

(Recap of the three theories repeats at the end of this section, same content as above.)

10. Proposed Information Architecture

Three parallel site maps — one per pillar (EAT / MOVE / SAVE) — sharing the same overall structure:

Common flow: Welcome/Login → (Returning Login / Claim Existing Record) or (New Account → Onboarding Questions → [Verify Email if required] → Account Created, choosing a focus pillar) → Account Menu (Profile & Settings, My Progress, About myEMS & EMS, Contact, Logout) → Choose Goals (several small challenges, complete progress) → Home (avatar/username, daily check-in, goals & complete progress, recommended events/content, prompt to explore other pillars) → Events (saved/featured, filter, card list with title/photo/date/location/focus types/views/saved#/action buttons, → Event Detail) → pillar content section → Resources

Pillar-specific content section:

• EAT: Recipes — saved/featured/filter/all-recipes card list (title, photo, views#, saved#, tried#, action buttons) → Recipe Detail (title, photo, nutrition facts, ingredients, preparation, categories, views/saved/tried#). Resources include Grocery Store Tour.
• MOVE: Movement/Exercise — saved/featured/filter/all-exercise card list → Exercise Detail (title, photo, video, duration, ability level, equipment, steps, category)
• SAVE: Home also includes a Food Budget Calculator; Resources include Grocery Store Tour and the Food Budget Calculator; other structure otherwise matches EAT/MOVE (Resources → Featured Resource, Filter, All Articles and Tools List, Article Details)

Also present on Home for all three: "Recommended Resources," "Find Food IL," "Prompt to Explore Other Pillars."

11. Claude-Powered Content Discovery (after 8/13 Internal Meeting)

Based on estimates from a Claude quick web-crawl + scoring pass per pillar.

Scale (0–3, applied independently per pillar): 0 = not relevant/not mentioned · 1 = minor/tangential mention only · 2 = clearly relevant, a meaningful secondary theme · 3 = primary focus of the page

EMS Subsite (https://eat-move-save.extension.illinois.edu/)

529 standalone pages: 478 from Drupal templates, 51 static hand-authored, 20 embedded game modules, 78 listed blog posts (2015–2026, the only content type that regularly crosses pillars). Breakdown: 16 content pages, 9 grocery-tour pages, 8 interactive grocery games, 312 individual recipes, 24 Illinois-grown produce pages, 8 content pages, 66 individual exercises, 6 content pages, 2 interactive grocery games.

IL Ext Events (next 9 months, 8/13/26–5/12/27)

282 events; 166/282 (59%) score 0/0/0. 60 events (21%) score Eat≥2 (nutrition classes, cooking demos, food preservation/canning workshops, food safety cert). 9 events (3%) score Move≥2 (almost entirely dedicated fitness classes — Tai Chi, chair yoga, A Matter of Balance, Fuel and Fit — not the many nature walks/hikes on the calendar). 7 events (2%) score Save≥2 (budgeting/financial-literacy sessions, a few food-waste cooking classes).

IL Ext Blogs

42 all-time topics, 5,900+ all-time posts; scored 1,207 posts (last year of posts, ≥25 per topic); 9 topics (6 active/3 dormant), ~1,200 posts since 2014.

Selected blog breakdown tables (Eat-leaning, Save-leaning, and mixed groups) — active/dormant status and post counts per topic (e.g. Live Well. Eat Well. ~325 posts since 2014, active; Simply Nutritious, Quick and Delicious ~519 posts since 2012, active; PlanWell.RetireWell. ~253 posts, dormant since Nov 2024; BeCentsible ~60 posts, dormant since March 2022; etc.)

IL Ext News

1,671 all-time news releases since 8/4/2016; 131 in the last year (8/13/25–8/13/26).

Related topics: Food Access/Safety & Nutrition (11, 8%), Health & Wellness (8, 6%), Farm Business/Finance & Legal (4, 3%). Non-related: Agriculture/Crop & Livestock (34, 26%), Natural Resources & Environment (32, 24%), Youth Development/4-H (14, 11%), Horticulture/Gardening (12, 9%), Staff/Org & Facilities (12, 9%), Community & Economic Development (4, 3%).

IL Ext Podcasts

12 series, 9 active, 4 weekly series; scored up to 50 episodes/series (297 episodes); two relevant series — Good Growing (48 capped, weekly horticulture/gardening; Eat≥1: 11) and Wellness Wake-Up Call (48 capped, weekly health/nutrition; Eat≥1: 29, Move≥1: 7, Save≥1: 1).

IL Ext Video Library

373 unique videos; 246/373 (66%) score 0/0/0; skews heavily toward agriculture, natural resources, pest/species ID. Notable: 32-video food-preservation series, 18-video venison-recipe series. Only 3 videos even reach a score of 1 for Save (Conscious Credit, Choosing a Financial Professional, What's Your Job Worth, Your Steps to Investing, Investing Basics).

IL Ext YouTube (@UIExtension)

~1,000 videos all-time, 24 all-time shorts, 24K subscribers; only scored 302 from the last year (200 of which were uploaded within two days in March). Notable: "Picking, Preparing, and Storing [produce]" series (9 videos, 2026-01-07, all Eat); IL-EATS food access program profiles (5 videos, all Save).

IL Ext Publications (pubsplus.illinois.edu, best-selling)

100 products in the best-selling category; over half related to pesticides/invasive species. Fruit & Vegetable Growing (7, 7%), Health & Family (1, 1%), Personal & Family Finance (5, 5%).

IL Ext Courses (Coursera-style)

151 courses in 27 subcategories. Agriculture (66), Family/Finances/Food (7).

IL Ext Socials

Facebook (38K followers), Instagram (3,651), LinkedIn (2K), Bluesky (318 followers, 300 posts).

Drupal Endpoints (JSON:API)

Additional per-endpoint pillar-score tables were included (videos, blogs, recipes, produce, exercises), e.g. recipes scored 100% Eat (323/323), produce 100% Eat (24/24), exercises 100% Move (66/66).

99 remote-video breakdown by channel: Eat.Move.Save. UofI Extension (81), UMN Extension Real Life. Good Food. (8), Illinois Nutrition Education Programs (6), UIExtensionFJPRW (4).

12. Data-Centric Thinking (Charles Blatti)

Prioritization tiers

• Top 8 for Design and Full Release: EMS/myEMS Contact, Support, Help
• Top 2 for Design and Beta Release: (grouped with above tier in source)
• Top 3 for Design Only: myEMS Tutorial content
• 40 Rest for Backlog and Future Planning: LLM Nutrition Chatbot (ask questions, get goal-related responses)

Data model notes (by area):

Overall EMS Goals: suggested templates; free-text entry; use frequency; preferred Eat/Move/Save domain; preferred content types/complexities

Interaction complexity tiers:

• Simple: logins, present/serve, save for later, click/open, like/favorite/not interested
• Complex: hover/preview, time spent, following

EMS Recipes: 312 recipes — type, time, number served, equipment requirements, age compatibility, steps, nutrition facts, shopping list; tags for ethnicity/holidays, diets, allergens, cost, complexity

Eat Profile: food favorites, ethnic cuisines, distastes, allergies, cooking quantity/times/equipment preferences/restrictions

EMS Exercises: 66 exercises — time, type, ability level, equipment, steps, tips; tags for age/fitness compatibility, target areas, intensity, calorie estimates

Move Profile: mobility/stamina limitations/benchmarks, weight, height, target areas, current/target time-or-cal per week, equipment/resource availability, nearby free resources

EMS Articles: 51 content articles — pillar, read time, content; tags for goals, likes/dislikes, user profiles

Save Profile: household wealth (savings, assets, retirement, debt), annual income, expense categories, food programs

EMS IL Produce: 24 fruits/veg — season, food group, nutrition, choosing, storing; tags for ethnicity, diets, allergens, nutrition, cost

Household Info: age, gender, at-home meals/week, special needs free text

IL Ext Events: 80 events in next 9 months — date, location (online/hybrid), cost, keywords, program areas, time of day, description, addresses, email, phone; tags for pillars, goals, likes/dislikes, host reviews

IL Ext Blogs: 42 topics, 1,207 in last year (min. 25/topic) — topic, date published, read length, content; tags for pillars, goals, likes/dislikes, related content

IL Ext Videos: 100 content videos in library — keywords, length, description, content; transcription, summary, tags for goals/complexity/specificity

Engagement/Summaries: likes/dislikes, comments, comment likes/dislikes, comment responses

Notification Preferences: in-app/email/text/phone; frequency; types of info (recommendations, activity summary, goal progress, next milestones)

Find Food IL: location type, zip, address, phone, email, website, languages, location hours, accepts SNAP, offerings

Friends: by lookup, or by recommendation of proximity + goal similarity

Volunteer Activity Logs: exercise/walking, cooking

General User Activity: by time period (week/month/year/all-time); relative content engagement (open) compared to other active/similar users; calendar, spider plot, advanced visualization

Goal-Oriented User Activity: percentage of goal-related content engagement (open, try), or self-reported progress toward goal

User Progress: real-world activity; want/completed/failed; tried event date and feedback; patron status(?)

Badges: predefined thresholds, temporal streaks, view/feedback quantities, real-world counts

User Opinions: engage/comment (ratings, precanned)

User Support: tickets, status, follow-through

Sharing: with a specific person, or with a friend group

Spatiotemporal recommendations: nearby/upcoming; by upcoming external seasons and holidays

Most Popular Content: by time period; serve/view/liked/try statistics; top comments

Recommended Content: by similar-user-also-liked; by goal tags

Compare Activity: between yourself and a small group of selected users

Data source types

• Generated: NCSA Chat or OpenAI for demo / simple placeholders when lacking data — long-term production plan TBD
• User Provided: long-term data management plan; issues relating to separate Extension data; most important APIs
• User Tracked: long-term data management plan

Social/Community data

• Core: metro size; email, alias, birth year, zip, preferred language, text/phone
• LLM User Profile (per pillar): merge user-provided + user-tracked data to create a text-based description for similarity ranking
• Extra: full name, full address, professional category, education level, race, join date, avatars, profile/activity sharing
• User Studies: study goal, treatment arm, related user responses

Manager-side sections

• User Management
• User Demographics Overview
• Content Management
• Content Engagement Overview
• Events Management: posting, sign-ups, check-in, contacting
• User Content Moderation
• User Activity Overview