Development Review
Artifact info
Title:

Holomovement LMS Development Kickoff

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
December 30, 2025
Next Meeting Date:
December 23, 2025
Hide This
December 22, 2025
Hide This
December 12, 2025
Hide This
November 21, 2025
Hide This
November 14, 2025
Hide This
August 31, 2025
Hide This
October 24, 2025
Hide This
People
Ivan Gonzalez
James Redenbaugh
Artifact Image
Meeting Summary

Project Introduction

James Redenbaugh introduced Ivan Gonzalez to the Holomovement ecosystem, a network of organizations dedicated to consciousness studies, collaboration, and global transformation (03:17). The Holomovement brings together diverse communities including scientists, artists, meditation teachers, and cultural contributors through events, podcasts, and educational programs. Their flagship Wave event moves to Portugal for the next gathering, following a successful event in Asheville where James presented on technology and consciousness (03:41).

The organization emphasizes intergenerational dialogue, bridging older practitioners with time and resources with younger participants bringing fresh energy and perspectives. Maro serves as director, with founders Emanuel and Laura transitioning from their previous nonprofit Greenheart and the Global Purpose Movement (04:42). Partner organizations include Evolutionary Leaders, featuring notable figures like Bruce Lipton and Ken Wilbur, though their website requires significant modernization (06:36).

Strategic Vision for Digital Engagement

The core challenge James outlined is maintaining the palpable sense of connection and possibility that exists at in-person Wave events throughout the year when participants return home (09:41). The LMS and app ecosystem aims to recreate this "field of synchronicity" digitally, making visible the connections and transformations that happen within the community. The system must balance the inspired, sacred frequency of the movement with grounded, practical functionality that facilitates real collaboration and learning.

James emphasized that this isn't about static content delivery but creating interactive, touchable experiences that facilitate ongoing connections between members (16:45). The design philosophy prioritizes seeing people, enabling discovery, and creating opportunities for meaningful collaboration outside conference settings.

[technology="Online Learning Platforms"]

[technology="Custom Membership System"]

Existing Synergist Directory System

James demonstrated the current synergist directory on the Holomovement website, which displays member profiles on an interactive map without requiring login (11:09). Members complete a form that triggers an automated assessment using n8n [tag="n8n"] and Claude AI [tag="claude"], which analyzes their responses about purpose, projects, and ancestral wisdom influences.

The system generates personalized feedback and recommends connections to other synergists based on compatibility, facilitating introductions via email without exposing addresses (13:42). It also suggests relevant podcast episodes members can listen to directly. This no-login approach removes barriers to participation while still enabling intelligent matching and communication.

[technology="Intelligent Matching Algorithms"]

[technology="Assessment Systems"]

[technology="Communication Automations"]

Technical Architecture and Stack Decisions

The team will use Supabase [tag="supabase"] as the primary database instead of Airtable [tag="airtable"], even though Airtable is currently used extensively on the website with Whalesync [tag="whalesync"] for instant synchronization with Webflow [tag="webflow"] (20:19). This decision prioritizes scalability, fluid data operations, and built-in authentication capabilities that Supabase provides. Lesson content may still sync with Airtable for easier bulk editing, but user data and membership information will live in Supabase.

Stripe [tag="stripe"] checkout will handle payments for both one-time course purchases and subscription memberships (28:50). The system must sync membership status between Stripe and Supabase so that when subscriptions lapse, access is automatically revoked. Multiple products may connect to the same membership tier, and bundled offerings may grant multiple memberships from a single purchase.

For email communications, the team discussed moving from Gmail [tag="gmail"] to ActiveCampaign [tag="activecampaign"] for newsletter and automation capabilities, replacing the client's current Constant Contact setup (18:55). Ivan shared his approach using ChatGPT playbooks with the Atlas browser for high-volume email management in Gmail.

MAST Framework Implementation

James showcased the MAST framework he's been implementing as the foundation for the LMS template (25:36). This component-based system includes intelligent features like automatic color and class naming, built-in light/dark mode, and extensive utility classes. He added custom scripts that automatically update the style guide when variables change, eliminating repetitive manual updates across projects.

The framework's slot functionality enables sophisticated component reuse while allowing clients to drag, drop, and customize layouts using Webflow's [tag="webflow"] builder (27:48). While MAST takes components to an extreme, James plans a balanced approach, using components strategically rather than for every element. This template will be duplicated not only for Holomovement but as a foundation for future client projects.

Course Structure and Access Control

The LMS will organize content hierarchically with courses containing modules, which contain lessons (28:50). Lessons may be renamed to "sessions" or "experiences" and could include multiple content types. An access level field will enable flexible permissions, allowing some introductory content to be freely accessible while restricting premium material to paid members.

The system will track user progress by monitoring lesson completion and scroll depth, currently stored in cookies but moving to Supabase for persistence and admin visibility (39:25). This data enables both user progress tracking and administrative insights into engagement patterns. Automation workflows using n8n [tag="n8n"] can analyze user responses to assessment questions and generate personalized communications based on their engagement and interests (16:45).

James emphasized avoiding limitations of existing platforms like MemberStack and Outseta, which the team has used previously. Building a custom solution prevents vendor lock-in and enables the innovation required for the unique learning experiences they want to create (31:19).

Knowledge Base and Documentation Strategy

James initiated a knowledge base on GitHub [tag="github"] organized into Development, Design, Operations, and Platform categories (32:50). The structure includes sections for the 12 core technologies IRIS offers, with initial focus on online learning platforms, membership systems, communication automation, and assessment systems.

The documentation uses markdown files with metadata, initially organized in folders but likely shifting to a single folder with manifest-driven hierarchy to avoid duplication (37:55). Some documents will be public and appear as blog posts, while others serve internal reference. James stressed the importance of documenting not just what was built but why, enabling future developers to understand architectural decisions and evolve the system.

He also built a script registry tool to track external scripts used across websites, currently requiring manual JSON updates but eventually planned for automation (40:37).

Development Approach and Initial Spike

The team agreed to begin with an authentication spike, implementing Supabase [tag="supabase"] login functionality on the MAST template in the IRIS Webflow [tag="webflow"] workspace (24:39). This initial work will establish the foundation for user profiles, password management, and session handling that the entire membership system depends on.

James will duplicate the MAST template as a starting point and provide Ivan access to the necessary tools (46:31). Ivan confirmed his Webflow account exists and will need access to Supabase, with n8n [tag="n8n"], GitHub [tag="github"], and Airtable [tag="airtable"] access provided as needed during development. Using an extra client account will allow Ivan to work in the IRIS workspace despite potential occasional conflicts with the German-based client who shares the account.

Personal Projects and Lab Environment

James briefly showcased personal projects in the IRIS lab environment, including a numerology app and a laser shooter game built with Claude [tag="claude"], demonstrating the experimental, playful approach to learning new technologies (42:11). The lab page serves as an index for the knowledge base and includes the simple LMS demo showing lesson tracking and completion functionality.

Action Items

James Redenbaugh

  • Provide Ivan access to Webflow account using the extra client account (44:29)
  • Create Supabase account and grant Ivan access (44:59)
  • Provide access to n8n, GitHub, and Airtable as needed (45:30)
  • Duplicate MAST template and prepare as starting point for LMS development (46:31)
  • Update script registry when new scripts are added to template (42:11)

Ivan Gonzalez

  • Begin authentication spike with Supabase integration on MAST template (46:25)
  • Report any blockers encountered during initial setup and development (46:07)
  • Review knowledge base structure and contribute documentation as work progresses
Relevant Initiatives

Holomovement App

Priority: 
Very High
Size: 
XXL
Planning Stage

Membership Authentication System

Priority: 
Very High
Size: 
L
Planning Stage

Assessment Development

Priority: 
Medium
Size: 
Planning Stage

Knowledge Base & Documentation System

Priority: 
Medium
Size: 
M
Creation Stage

Email Infrastructure Migration

Priority: 
Medium
Size: 
S
Planning Stage
Transcript