Cultivate
Case study · AI Tools & Strategy
A personal learning environment: one offline-capable hub where a faculty member keeps a professional growth plan, resources, deadlines, and a classified AI-in-education news feed, so attention goes to learning rather than to managing where the learning lives.
If you are opening Cultivate on your own device, expect some links to look broken. That is by design, not a defect. It was built for one iPad, where the documents and videos are saved locally and the logged-in resources open normally. A visitor who is not signed in, or who is on a different device, will hit dead ends that work perfectly on the intended iPad.
1. Summary
Cultivate is a personal learning environment: one offline-capable hub where a faculty member keeps a professional growth plan, resources, deadlines, and a classified AI-in-education news feed, so attention goes to the learning rather than to managing where the learning lives. It is a single-user tool, in daily use, that collects nothing and runs entirely on the user’s own device.
2. Goal
Cultivate exists to hold one faculty member’s learning together in a single place. The problem it solves is not technical, it is cognitive. When resources live in bookmarks across three browsers, notes sit in another app, and deadlines sit in a calendar nobody opens, the effort of managing that scatter consumes the attention meant for the learning itself. Consolidating them into one hub lowers that extraneous load, in the sense Sweller’s cognitive load theory intends, so the next right action is visible without hunting for it.
It is a personal learning environment in the truest sense: a hub the learner curates and owns, not a closed institutional platform that owns the learner’s work. The one part that is connectivist is the news feed, a live network of sources kept current because AI in education moves too fast to hold in your head. The rest is intentionally simple. Cultivate organizes professional growth, it does not deliver or measure learning, and it does not connect people, so it is a personal learning environment, not a learning network.
3. Users and context
One faculty member, its author: a Digital Media Arts instructor building AI literacy deep enough to teach it, supporting a campus community of practice, and developing student-facing tools. It is designed around real working conditions, read between classes and offline while traveling, on an iPad and a laptop, where long lists and context switching carry a real cost. Being single-user is the point, not a limitation. That constraint is why it can stay this simple, and why it belongs to one learner by definition. Other educators are welcome to fork the architecture for their own goals; it is not a shared product and is not meant to become one.
4. How it works
Six linked HTML pages share one design system, one header, and one navigation pattern, with no backend, no login, and no build step. Each page loads on its own.
| Page | What it does, and why |
|---|---|
| Resources hub | The entry point: classified news feed, resource cards, a progress bar, and a link into the growth plan. It answers “what should I look at today” without a search. |
| Growth plan | A priority roadmap with real target dates, checkboxes, and deadline badges. Making the next step and its deadline visible is the intervention; hidden deadlines are the ones that slip. |
| Activity log | Fed automatically as tasks are checked off, with category badges and CSV export. It quietly produces the record a faculty evaluation plan needs and that almost nobody keeps by hand. |
| UX toolkit | A reference of design tools, vocabulary, and practice projects, the working library behind the teaching. |
| Conference page | A single working proposal: abstract, learning outcomes, and a preparation list, with the deadline surfaced. |
| Context block | A one-tap copy block that restores project context in a new AI session, so the tool and the AI stay in sync without re-explaining. |
The news feed
A curated pool of RSS sources is fetched on each refresh and routed to the right tab by a keyword classifier, then cached locally for 24 hours so it stays readable with no connection. Because RSS endpoints block cross-origin requests, fetches fall through three public proxies in sequence; if a source fails on all three it is skipped silently and the feed degrades rather than breaking. This is the one fragile part, the public proxies are outside anyone’s control, and it is the weak point of the tool. Offline reliability is a design goal on purpose: the tool was built to work on an iPad in the air and in rooms with no reliable wifi.
No AI model runs inside Cultivate. AI helped build it, and the feed is routed by a plain keyword classifier, not a model, which keeps it fast, free, and fully offline. That is the intended posture across this portfolio: AI as scaffolding, not as the thing running underneath.
5. Data, privacy, and governance
Cultivate collects nothing. Checkboxes, notes, and the activity log live in the browser’s localStorage on the user’s own device; there is no account, no analytics, and no transmission of user data anywhere. No student data ever enters it, so there is no FERPA exposure. A tool that collects nothing has nothing to govern, which is the same data-sovereign line the student-facing tools in this portfolio hold.
6. Build and portability
Six linked HTML pages share one design system, one header, and one navigation pattern, with no backend, no login, and no build step, so the whole thing hosts as static files and each page loads on its own. Checkboxes, notes, and the activity log persist in the browser’s localStorage on the user’s own device. The news feed fetches a curated pool of RSS sources on each refresh, routes them with a plain keyword classifier, and caches them locally for 24 hours so the tool stays readable with no connection; because RSS endpoints block cross-origin requests, fetches fall through three public proxies in sequence and degrade silently if a source fails. No AI model runs inside Cultivate: AI helped build it, but nothing calls a model at runtime, which keeps it fast, free, and fully offline. The architecture is forkable, another educator can copy the structure for their own goals, and there is no key or account to carry across.
7. Pilot and testing
Cultivate is not piloted, and it is not meant to be. It is a single-user personal tool in daily use, and its test is whether it holds up in real working conditions: read between classes and offline while traveling, on the intended iPad where the local documents and logged-in resources open normally. Validation is qualitative and continuous, does the next right action stay visible without hunting, and does the feed stay readable with no wifi, rather than a cohort study.
8. Definition of success
Cultivate succeeds when the next right action and its deadline are visible without hunting, when the feed and saved materials stay readable offline, and when the activity log quietly accumulates the record a faculty evaluation needs without the user maintaining it by hand. Because it is uninstrumented and single-user by design, success is simply that it stays in daily use and lowers the overhead of managing where the learning lives, not a number.
9. Rollout
There is no rollout. Cultivate is a personal learning environment and belongs to one learner by definition, so it is not headed for a cohort or a district deployment. Other educators are welcome to fork the architecture for their own goals. Explicitly out of scope: turning it into a shared or departmental platform, which would mean accounts, a backend, and a data agreement, and would convert a tool that collects nothing into one that collects something.
10. Open questions and risks
- The public proxies. The news feed depends on three public cross-origin proxies outside anyone’s control. They are the one fragile part, and if they fail the feed degrades rather than breaks.
- Local-only state. Checkboxes, notes, and the log live in localStorage, so a cleared browser can erase a year of notes. There is no server backup, by design.
- Off-device dead ends. Because documents and logged-in resources are saved on the intended iPad, a visitor on another device or not signed in hits dead ends that work on that iPad. This is by design, but it means the live page is not a general-audience artifact.
11. Roadmap
If Cultivate grows it will be small, optional tinkering, never a platform: a quick add-a-resource input, and an export of all local state so a cleared browser cannot erase the notes and the log. Anything larger, accounts, a backend, or sharing, would cross the no-data line the tool exists to hold, so it stays off the map on purpose.