Local development · read-only help

Data editing guide

How to maintain Wellness Library, yoga postures, mudras, practice units, audio, and deploy preview — without editing generated JSON or deploy/web_public by hand.

Source of truth

Quick map

Feature Edit Build Output JSON
App Registry data/registry/app_registry_master.csv build_app_registry.py app_registry.json
Wellness Library cards Excel Wellness sheet build_wellness_units_from_metadata.py wellness_units.json
Pranayama / plan blocks Excel Wellness (practice rows) build_practice_units_from_metadata.py practice_units.json
Ritual / mood audio WellnessAudioLibrary sheet lifeloveme.sh build wellness-audio wellness_audio_library.json
Yoga / mudra images web/assets/wellness/.../final/ paths in Excel → units JSON
Books / poems Excel Books / Poems convert_creations_metadata_master.py web/data/creations/

Typical workflow

  1. Edit Excel or add an asset under web/assets/
  2. Run the matching build script from the repo root
  3. Restart source: ./scripts/lifeloveme.sh restart source
  4. Test the app area (library, Experience Player, or Ask)
  5. prepare-deploy · restart deploy · check assets deploy

Test commands (Terminal)

./scripts/lifeloveme.sh test wellness-library source
./scripts/lifeloveme.sh test experience-player source
./scripts/lifeloveme.sh test ask source

After deploy preview, repeat with deploy instead of source.

Open apps (port 8780)

Related guides

Canonical Markdown lives under docs/ in the repo and is not served by the local web server (avoids 404 on deploy preview).

← Home