​Here's what's in Preach360 v2.14.0! ​NEW: Preach360 Essentials Studio (preach360.com/essentials) - Streamlined 4-Step Prep Flow: Move ​e​ffeciently through ​developing your Keyword​ and Four Movements. - Flexible Development: Work on, develop, and refine any section in any order that fits your workflow. - Continuous On-Demand Coaching: Access helpful coaching prompts whenever needed, paired with real-time autosave. - Fully Editable Sermon Guide: Edit every single line directly on the page, with instant print preview, generated movement transitions, and one-click copy. - Seamless Exports: Send your work straight into the Sermon Studio with one click for deeper development, or export as ready-to-use PDF or TXT files. ​NEW: Full Sermon Assessment (preach360.com/sermon-assessment) All active subscribers can now run comprehensive diagnostic sermon assessments directly from their account dashboard. You can easily copy your full report to your clipboard ​t​o use for sermon revision and optimization before Sunday. ​IMPROVED: Studio-Wide Study HighlighterThe study highlighter now works across all six sermon studio panes with a dedicated Highlighter menu in the toolbar. All of your sermon highlights now carry over seamlessly into your PDF and DOCX exports, too. ​FIXED: Expository Maps​ Performance & Reliability Fixes - Rock-Solid Tab Stability: Resolved the browser tab freezing and crashes during map generation. Long coaching replies now render smoothly without stalling the page, and the stream sends keep-alive pings so generations can run safely up to 290 seconds without timing out. - Immediate Generation: ​The Expository Maps step begins generation ​i​mmediately after the foundation is poured—regardless of how you phrase the prompt—eliminating unnecessary confirmation friction. - Complete Thematic Maps: Maps now cite Scripture references instead of quoting extended passages, ensuring generations finish completely without running into content-filter limits.

Hey everybody, Wondering what lessons you learned on Sunday. - What went well? - Did you try anything different? - Are you planning on trying anything different this upcoming Sunday? - Have any advice for the rest of us?

For those interested in what web app construction looks like, here's what happened this week under the hood. As always, if you come across any tech bugs, let me know and send a screenshot if you're able. By the way, a huge shout out thank you to our developer genius, @Michael Byrd, who went WAY above and beyond this week. - Fixed the Sermon Builder walkthrough freezing after a fumbled confirmation — step completion is now driven by the confirmed field, so a stale step self-heals on the next confirmation - Fixed confirmations dead-ending on "ready to move on" — the AI now opens the next step's coaching in the same reply, using scripted wording and never inventing options - Fixed manuscript generation failing on a desynced walkthrough — blocked generation attempts now heal the step index at the end of the turn - Fixed duplicated chat bubbles caused by sends racing an in-flight response stream, and repaired already-corrupted saved conversations - Fixed repeated coaching messages by pinning the Vertex provider SDK to the last good version, plus a filter that suppresses any verbatim repeated text - Fixed silent content-tool failures behind "manuscript won't generate" reports — unavailable tools now explain themselves and guide the walkthrough forward, mistyped tool parameters are auto-repaired, and AI usage is recorded on aborted streams - Fixed production log issues: client error serialization, /projects hydration mismatch, and AI SDK patch updates - Required every numbered coaching part to be answered before a manuscript section can be drafted - Stripped echoed session-context blocks from model output and healed already-saved histories - Surfaced mid-stream generation failures (e.g. rate limits) with the real reason instead of silently claiming success - Guarded the admin prompt fragment editor against silent save loss — unsaved-changes confirmation when switching fragments, and stale-tab saves now detect conflicts instead of overwriting newer work

Hi y'all, What do you want to discuss in tomorrow's office hours? - How do analyze the heart in the problem movement? - How to apply the "minimum effective dose" principle? - How to use the vocab of grace in application? - How to connect any text to the cross? - How to preach with your own voice? - How to apply the "clarity cap?" Or anything else? Just let me know in the comments. McKay

I'm having difficulties accessing preach360.com today. Here is the message I kept getting: "Something went wrong An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error."