LifeLoveMe Prototype Journey

From App to System

The prototype now runs as a real site on a Mac and, over the same Wi-Fi, on an iPhone. A modest local server, a stable port, and the Mac’s LAN address are enough to prove the point: this is instrument, not illustration.

The three pillars are no longer a slogan on a slide. They are routes in the site:

• Life — wellness, rhythm, quality of days.
• Love — devotion, beauty, depth without turning away from the world.
• Me — creator, memory, legacy, and the seed of a future community hub.

What visitors can already touch includes:

• A visual launcher on Home and full Life, Love, and Me experiences
• About, Books, Poems, Creations, and Docs
• Me as the place for the human behind the work—not only biography, but archive and intention
• The Ramcharitmanas experience and the Wellness / InnerRamayan player
• A book reader wired for depth (summary, TOC, chapters, key ideas, and Q&A still on the roadmap—but the path is named)
• A command guide and desktop launcher so routine work does not depend on memorizing Terminal

The Books thread grew into a small content-management and information-extraction pipeline: Excel as the editable master, export to JSON, PDFs in public spaces, extracted text for what comes next. That spine can be read as a single flow:

Human-editable Excel
        ↓
Validation and export script
        ↓
JSON data layer
        ↓
Website and app
        ↓
Reader / player / search / future AI

The Pain of Wrong Files and Wrong Folders

Hours disappear in the gap between intention and path. A script points at yesterday’s folder. A JSON file was copied by hand and silently went stale. The browser serves an old PDF because the filename never changed. None of this is moral failure; it is the tax of building without a single agreed map.

The recurring lessons, compressed:

• Folders must match the blueprint, or the machine looks in the wrong cupboard.
• Names and locations are part of the contract—not decoration.
• Caches (browser and habit) will lie to you unless the system tells the truth.

Excel for human editing. JSON for the app. Scripts for conversion. The browser for display.

Every file that changes must carry a way for the system to know it changed.

Stable public URLs, FileVersion, and cache-busting are not pedantry; they are how you win an argument with a browser that loves yesterday.

Commands Became Memory

Terminal fluency is a wonderful skill; dependable recall of every flag and path is not. The project reached a point where commands had to live outside the head: a written command guide, a scripted Control Panel (lifeloveme.sh), and—on the Desktop—a launcher that turns fragile memory of syntax into a menu anyone can use.

Documentation and buttons do not replace understanding; they protect understanding on days when attention is thin.

A Personal Reflection

This work is not only about shipping screens. It is about building a system that compensates when short-term memory fades—while leaving analysis, structure, and care for pattern fully in play.

A sixty-seven-year-old steward—clear that recall can flicker, and equally clear that logic still serves—has used AI, disciplined folders, Excel masters, JSON, scripts, guides, and a local application to assemble a platform that remembers when the moment does not.

The app became more than software. It became an external memory system.

The Blueprint Matters

You do not finish the cathedral in one season. You dig foundations and draw plans so the next season’s wall does not contradict the last.

Foundation and blueprints matter even when everything is not built in one pass.

Named destinations—reader, search, future AI, versioned files—are promises to your future self. Building today so tomorrow is not blocked is the quiet heroism of long projects.

This section belongs in the eventual book: it ties the build to the human reason the build exists.

Orientation

• Project root (on the steward’s Mac) typically lives under iCloud Drive: ~/Library/Mobile Documents/com~apple~CloudDocs/LifeLoveMe
• Website files live in web/. The local dev server is run with web/ as the document root (commonly port 8770, bound to 0.0.0.0 so iPhone browsers on the same Wi-Fi can reach it).
• Automation and exports live in scripts/ at the project root (not inside web/).
• Ramcharitmanas source JSON and related data under data/ramayan/ (and generated outputs as documented elsewhere); wellness content under data/wellness/.

First URLs to open

http://localhost:8770/home/index.html
http://localhost:8770/docs/index.html
http://localhost:8770/docs/commands.html

The Command Guide (commands.html, also available as Markdown) is the operational source of truth for server, export, extraction, and cache-busting—not this journey page.

Books and JSON: two layers

There are two books.json paths in the tree:

data/content/json/books.json    ← pipeline / export side
web/data/content/books.json     ← what the static site loads

Before you change either file by hand, understand how export_content_json_from_master.py (and any copy/sync step in your workflow) moves data from Excel into these locations. Excel is the human-edited master for that pipeline; JSON is generated or derived—treat manual edits as temporary hacks unless the team agrees.

Extracted book text and metadata for readers live under:

web/data/extracted/books/<book-id>/

Python environment

Export and extraction scripts expect a project virtual environment (commonly .venv-rcm at the repo root). If imports fail, activate that environment first—again, see the Command Guide.

Front-end shape

• Most pillar and content pages are static HTML/CSS/JS under web/home, web/life, web/love, web/me, web/books, web/poems, etc.
• Ramcharitmanas, wellness, and InnerRamayan experiences are centered on web/apps/experience-player/, with a very large shared player.js. Assume that file is load-bearing: small, testable changes; avoid drive-by refactors until you understand playback and state flow.
• The book reader has its own HTML/CSS/JS under web/books/ (reader page and helpers).

Habits that keep the team sane

• Paths with spaces: the iCloud root contains spaces; quote paths in shell scripts and documentation.
• Caches: when PDFs or assets are replaced under the same name, use FileVersion and ?v= query parameters so browsers fetch the new bytes—see the Command Guide.
• Blueprint: for data model and long-range structure, read blueprint-foundation.html alongside this journey.

Where to go next