Overview
What the project is designed to do
A large static Teoyube prototype bringing Scripture promises, calling tools, a personal canon, reflection, and the Book of the Saint into one navigable browser application.
The build contains more than two hundred local files and data-driven surfaces without a framework, database, authentication, or protected source media.
When approved media is absent, that surface explains nothing is published while the rest of the application remains functional.
Problem
What needed to change
A broad ministry vision needed a coherent frontend without depending on unfinished backend or media workflows.
Solution
How the release responds
Package the public experience, local assets, runtime data, and read-only fallbacks into a deterministic static release.
Key features
What visitors can use
- Daily Scripture experience
- TeoyubeSearch, Canon, and Promise Table
- Calling Compass and Book of the Saint
- Reflection and testimony
- Optional-media unavailable state
Implementation
How it was built
- 01
A custom deterministic script assembles the static release.
- 02
Browser-readable JSON drives product surfaces.
- 03
Two read-only functions provide promise seed and YouTube fallback data.
Architecture
Delivery shape
A self-contained HTML, CSS, and JavaScript app is deployed with two read-only fallback functions.
Product boundary
What this release does not claim
- No owner tools, protected media, approvals, local paths, or secrets
- No claim that optional media is published
