Project Context Content Creation Workflow
From Biblical Research to Published Study
It Starts With a Question
Project Context isn't really about answers — it's about questions. I build each study around a question I'm carrying, and those questions grow and change with each author and each season of God's people. Learning to hear them takes time. But followed far enough, they all lean the same way — toward the Messiah, and toward how Jesus of Nazareth fulfills what came before.
What keeps me at it is how congruent it all is: narrative, law, psalms, prophets, and letters telling one consistent story of God and his people over time. Capturing that story — so I can keep following Jesus faithfully through it, learning to see Scripture and the world the way he did — is what these studies are for. They're where I return for orientation and context along the way.
Each study starts from one of those questions. From there it's a process of gathering, drafting, testing, and refining: I pull from a library of commentaries and books and the teaching work of the Bible Project, work alongside AI tools to shape a first draft, then read, edit, and re-check it by hand — and against the sources I cite — until it teaches well.
One person builds these, and the whole journey is laid out in the open. The stages below trace it from the first question to the published page.
— Henry Rivera, Founder
→ Browse all studies
🤖
AI Assistant Processing
AI processes source materials and template structure to create comprehensive first draft in markdown format.
📝
Draft Components
- Biblical context and setting
- Character/theme analysis
- Theological themes
- Hebrew/Greek terminology
- Intertextual connections
🏷️
Key Terms & Definitions
I pull out the important terms — including the Hebrew and Greek where it matters — with short definitions and where they appear, so the same idea is explained the same way across every study.
🔗
Cross-References
I note related characters, themes, and passages and link studies to each other and to their section hubs, so related work is a click away instead of something you have to hunt for.
📚
Sources & Bibliography
I keep a clean list of sources and track which one supports which point. That keeps the scholarship honest and lets you go deeper on anything you'd like to check for yourself.
🧩
People, Places & Connections
I record the lasting pieces — people, places, covenants, recurring images — and how they relate. Together with the shared structure every study follows, that's what makes the site read as one connected library rather than a pile of separate pages.
💡 Why this matters to you: Capturing all of this as I go is what lets studies cross-reference each other, keeps definitions consistent across the whole site, and lays the groundwork for features like searchable glossaries and connection maps down the road.
🧭 Two Goals at Once
Solid studies today
Everything above first serves the study you're reading right now — accurate, clear, and well-sourced.
Richer tools tomorrow
The same structured notes prepare the ground for better features later — search, glossaries, and maps that connect the whole library.
✏️
Content Editing
I check the biblical details, strengthen the theology, and make sure everything stays faithful to the sources it came from.
🎯
Pedagogical Design
I reorganize for readability and make sure each study actually teaches — building in an order that makes sense for a real learner.
📐
Style Refinement
I adjust tone and examples so each study reads in a consistent Project Context voice.
💡 My editing bar: I read every study myself and hold it to one question — is it clear, faithful, and genuinely useful? Some of that is measurable; a lot of it is editorial judgment, the same kind any teacher brings to deciding whether an explanation will actually land.
🎨
HTML Development
AI transforms refined content into semantic HTML with template structure and cosmic branding
⚡
Interactive Features
Dynamic mobile tabs, reading progress, quick navigation, scroll animations
📱
Responsive Design
Mobile-first layout, touch targets, accessibility features
🔍
Initial Review
I review the HTML output for presentation quality, how it reads on the page, and overall layout and design.
➕
Data Enhancement
I add supplementary material, refine examples, and improve the visual hierarchy wherever it helps the study land.
✅
Cross-Checking With Multiple AI Tools
I run the study through more than one AI tool so they can check each other's work — verifying theological accuracy and biblical fidelity, pushing back on weak or unsupported claims, and suggesting enhancements I might have missed.
🔄 Iterative Refinement Loop
This loop repeats many times — often far more than a couple of passes. My review focuses on:
- Theological accuracy
- Literary structure and fidelity to the text
- Consistency with my authoring standards and each page's criteria
- Coherence with the rest of the studies across the canon
I keep applying revisions until the study meets my standards for accuracy and teaching.
📋
Quality Checklist
Verify metadata, navigation, cross-references, bibliography, and all interactive features
🧪
Testing
Test on desktop, mobile, tablet; verify Hebrew/Greek fonts, links, and responsive behavior
✨
Final Polish
Last-minute tweaks, typography adjustments, and visual refinements
🚀
Live Publication
Published to ProjectContext.org via continuous deployment pipeline with version control and global content delivery
📚 Product Outcomes
This workflow supports all Project Context study formats:
🔄 Continuous Development Loop
After publication, the process doesn't end. I continuously review published pages and update content as needed — refining accuracy, adding new insights, and improving presentation. Updates flow back through stages 3–6 as needed.
