Marketing Global Marketing and Brand Services (GBMS) Blogs Blog Brief Template This is a really thorough article about developing content briefs . Blog Title Descriptive and must include focus keyword       URL Grab keywords from title to create an easy-to-find URL Should be self-descriptive Try take out stop words (and, the, but, can, etc) from title and keep larger keywords. Try avoid numbers Identify User intent What is the user expecting to find by reading this blog? Context/ Pitch/Big idea No piece exists in a vacuum, so the brief must offer practical contextual information. (naturally refers to other related JFP blogs) The info required changes depending on format—for example, what a writer needs to create a blog is different from what they need to produce a video script. If you’re briefing a keyword-based piece, this section would include primary and secondary keywords, search intent, and a list of internal links to and from other relevant content.   Focus Keyword This should be in your title, body copy, and meta data. There should only be one focus keyword per blog. There should never bees 2 blogs using the same focus keyword (this causes cannibalism) Supporting Keywords List at least 5 secondary keywords that will help support your content in ranking Blog Objectives Each new piece must fit within the larger narrative of JFP. This brief clearly illustrates the company’s goal for the piece, its unique take on the topic, and how the company itself and its products/services fit into the story. Competing blog articles List URL of good quality URLs that we can glean from     Internal links List internal links to blogs and other pages owned by JFP that would support your writing. Try to aim for at least 5 internal links. Search for existing JFP blogs on Google –-> In the search bar type in “site: jesusfilm.org/blog/ [insert topic]” External links Find at least 3 external links (non-JFP URLs) that would support your content points. Audience Believer (needs to be more specific) All briefs should start from the audience, since they are the reason you’re creating something in the first place. This version begins by summarizing who the audience is, their jobs-to-be-done, and what they should take away from the piece. Technical Level Beginner/Entry-level Blog Content Type E.g. how-to guide Blog Deliverables ~2,500 word article, images, videos, etc Blog Outline Link to the blog outline when it is completed References (external links) Content Category (i.e. missional living) Call to action Blog Template: Comparisons   This is a template for writing "comparisons" for blogs.  Use these section to organize and optimize your blog writing. Title I.e. [ABC] vs. [XYZ]: Which [Item] is Better? E.g. Difference Between KJV and NKJV Bible Versions Introduction Brief overview of the items being compared Mention your JFP subtly, if applicable Explain not what you’re going to cover, but what readers will get out of your post ABC vs. XYZ at a glance [Create a comparison table with key features and ratings] Feature ABC XYZ Feature 1 ⭐⭐⭐⭐⭐ ⭐⭐⭐⭐ Feature 2 ⭐⭐⭐  ⭐⭐⭐⭐⭐ Feature 3 ⭐⭐⭐⭐⭐ ⭐⭐⭐  [Best for] [User type/use case] [User type/use case] Etc Etc Etc Key Differences 1. Difference 1 Explanation for Competitor 1 Explanation for Competitor 2 2. Difference 2 Explanation for Competitor 1 Explanation for Competitor 2 3. Difference 3 Explanation for Competitor 1 Explanation for Competitor 2 Feature Comparison Feature Category 1 Competitor 1: Description Competitor 2: Description Our take: Brief analysis [Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences] Feature Category 2 [Competitor 1: Description Competitor 2: Description Our take: Brief analysis [Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences] Feature Category 3 Competitor 1: Description Competitor 2: Description Our take: Brief analysis [Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences] User Experience and Interface E.g. Comparison of user interfaces E.g. Ease of use for different user types Customer Support and Resources Comparison of support options Available resources (documentation, tutorials, community) [Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences] Use Cases When to choose ABC [Scenario 1] [Scenario 2] [Scenario 3] When to choose XYZ [Scenario 1] [Scenario 2] [Scenario 3] Alternatives to consider Introduction to your brand's offering How your product/service compares to the competitors discussed Unique selling points of your brand Call-to-action to try or learn more about JFP Final thoughts Summary of key points Recommendations based on different user needs       Blog Template: Expanded Definitions or Topics   This is a template for writing "Expanding on definitions or topics" for blogs.  Use these section to organize and optimize your blog writing. Title What is [Concept]? [Brief/Quick/Detailed] Explanation E.g. What is Salvation? A Thorough Explanation Start with “what is/are” questions Establish credibility Add context Introduction 1-2 sentence definition, including bolded keywords (helps to earn visibility in Google). Keep it short Why [topic] matters Explain the importance and relevance of the concept in 2-3 paragraphs. How [topic] works Provide a concise explanation of how the concept functions or its process. What are the key features of [topic]? List and briefly explain the main features of the concept. Feature 1 Short explanation and example. Feature 2 Short explanation and example. Feature 3 Short explanation and example. How to use/approach [topic] Provide practical advice on how to use or implement the concept. Audience question 1? Address 3-4 frequently asked questions about the concept, based on audience research. Provide concise answers upfront for more chance of appearing in a SERP feature. Audience question 2? Address 3-4 frequently asked questions about the concept, based on audience research. Provide concise answers upfront for more chance of appearing in a SERP feature. Audience question 3? Address 3-4 frequently asked questions about the concept, based on audience research. Provide concise answers upfront for more chance of appearing in a SERP feature. Final thoughts Summarize key points in 2-3 sentences.  Encourage readers to implement or learn more.               Blog Template: Lists & Listicles This is a template for writing "lists or listicles" for blogs.  Use these section to organize and optimize your blog writing.   Title I.e. [Number] [Topic] [Tips/Ways/Techniques/Tools/Reasons] for [Desired Outcome/Audience] E.g. Top 10 Christian Bibles Study Resources to Grow Your Faith Introduction Keep it short Establish trust and expertise in 2-3 sentences Explain not what you’re going to cover, but what readers will get out of your post 1. [Benefit-Focused List Subheading] E.g. Capture trending traffic by stealing Top Stories keywords from your rivals Explanation of the first point. Include:  why it's important how to implement real-world example or case study [Add image, video, social media embed, or screenshot to illustrate the point] 2. [Benefit-Focused List Subheading] Explanation of the second point, following the same structure as above [Optional: Add a relevant quote from an expert or statistic to support your point] [Optional: Add a “Pro tip” related to this point to make post even more actionable and break up text] 3. [Benefit-Focused List Subheading] Explanation of the third point. [Optional: Include a step-by-step mini-list if this point requires a process explanation] Step one Step two Step three ... X. [Benefit-Focused List Subheading] Explanation of the final point in your list Conclusion/Wrapping up Summarize the key takeaways from your list. Add one or two final, actionable tips that readers can implement immediately. [Optional: Include a question to encourage comments and engagement] Add a call-to-action or link to a related resource. CTA Example CTA: Want to learn more about growing your faith? Check out these related articles: ????? ????? ?????               Blog Template: Writing a Beginner’s Guide This is a template for writing "Beginner guides" for blogs.  Use these section to organize and optimize your blog writing. Title I.e. [Topic] for [Beginners/Noobs/Dummies]: The [Complete/Essential/Ultimate] Guide E.g. A Simple Guide To Reading and Understanding The Book of Matthew Reinforce why they need to know this State that it’s for beginners/Noobs/new users, etc Keep it simple (use shorter sentences and keep fletch reading score) Introduction Hook sentence or interesting fact to grab attention Encourage readers that the topic is manageable Provide a quick overview of what they'll learn What is [topic] and why is it important? Clear, concise definition Brief history or background (if relevant) Key concepts or terminology Explain the significance of the topic in simple terms and give real-world applications. What are the key components of [topic]? Component 1 Explain the first key component Component 2 Explain the second key component Component 3 Explain the third key component What are the benefits of mastering [topic]? [Benefit 1] [Benefit 2] [Benefit 3] Key things to know about [topic] Best Practice 1 Explanation and implementation tips Examples Best Practice 2 Explanation and implementation tips Examples Best Practice 3 Explanation and implementation tips Examples How to get started Step 1: Provide detailed instructions for the first step Step 2:  Provide detailed instructions for the second step Step 3: Provide detailed instructions for the third step Common mistakes to avoid with/in [topic] Mistake 1:  Explain the mistake and how to avoid it Mistake 2:  Explain the mistake and how to avoid it Mistake 3:  Explain the mistake and how to avoid it Top tools for [topic/audience] [Tool 1]: [Image/screenshot/video/quote/review]: [Brief description] [Tool 1]: [Image/screenshot/video/quote/review]: [Brief description] [Tool 1]: [Image/screenshot/video/quote/review]: [Brief description] Helpful resources to learn more [Resource 1]: [Brief description] [Resource 2]: [Brief description] [Resource 3]: [Brief description] Wrapping up Summarize and offer a couple of unheard tips, quotes, or insights. Offer some final encouragement, and link to further resources:  Further Reading [Related article 1] [Related article 2] [Related article 3] Blog Template: Writing a How To / Detailed Guide This is a template for writing "How To's" or "Detailed Guide" for blogs.  Use these section to organize and optimize your blog writing. Title I.e. How to [ Achieve Desired Outcome ] in [ Number ] Steps E.g. How To Become More Confident Of The Bible's Accuracy Tips Mention the desired outcome - Audiences desired goal/objective List the number of steps Introduction Hook to grab reader's attention  Write in a way that connects with your audience Show you understand the problem e.g. personal experience/anecdote, or analogy Present the problem this guide will solve Show proof you have the solution Tree of thought (concept is from prompting, but can be used for writing) Chain of thought (concept is from prompting, but can be used for writing) (link to external sources, quote others, use logic in your explanation You can also include: Who is this guide for?  Describe the target audience and their skill level What you'll learn [Key takeaway 1] [Key takeaway 2] [Key takeaway 3] Why You Can Trust Me/Why I Am A Reliable Source Use the PSP (Problem-Solution-Proof) formula to establish credibility Problem: Show you understand the issue Solution: Briefly present your solution Proof: Demonstrate your experience and success in solving the problem Step 1: [present tense verb] Detailed explanation of this step Tips or best practices for this step Common pitfalls to avoid [Add images, videos, embeds, or screenshots to illustrate the step] Step 2: [present tense verb] Detailed explanation of this step Tips or best practices for this step Common pitfalls to avoid [Add pro tips, images, videos, embeds, or screenshots to illustrate this step] Step 3: [present tense verb] Detailed explanation of this step Tips or best practices for this step Common pitfalls to avoid [Continue with additional steps as needed] [Add pro tips, images, videos, embeds, or screenshots to illustrate this step] Final thoughts Quick summary of the process taught in the post Reinforce the benefits of following this guide Encourage the reader to take action Next steps Suggest related topics or advanced techniques to explore Call-to-action for further engagement (e.g., subscribe to newsletter, check out related products) Blog Template: Writing Thought-leadership & Opinion Copy   This is a template for writing "Thought Leadership or "Opinion" blogs.  Use these section to organize and optimize your blog writing. Title I.e [Provocative/Contrarian Title: State Your Main Argument] E.g. What does it mean to “carry your cross”? Are You Doing It? Use a provocative, contrarian, or surprising statement (not click-bait) Check out stfo.io Include non-typical language and to capture attention It is important to show credibility (especially with opinions pieces) Introduction Open with a hook highlighting a familiar scenario or common belief in your industry Briefly state your contrarian or thought-provoking stance Hint at the risks or flaws of the topic Outline the current state of things Describe the prevailing wisdom or practice right now This is one of the few times where you can use industry jargon or familiar phrases. It’s a good way to create a shared experience and platform your expertise Give examples of how things are typically done   Tease the immediate risk Describe a significant, immediate risk of the common practice Tease the impact on a real-world person/brand/industry/thing example to illustrate the point – but withhold the details of how it happened until later on Outline the problem [Problem 1] Start building in more tangible evidence Make a bold, declarative statement in the H2 Describe the problem from different angles so readers can get to grips with your argument  Include metaphors, analogies, or thought experiments to make your point more readable  [Problem 2] Start building in more tangible evidence Make a bold, declarative statement in the H2 Curate compelling data, stats, or visuals to support your argument Return to your real-world example/case study from earlier and tell the full story of why/how they were impacted Feature quotes from others who share similar views Dive into the far reaching implications Make a bold, declarative statement in the H2 Broaden the scope to discuss how this practice affects entire groups/tribes/industries/countries etc. Discuss the potential long-term negative effects of the practice Draw comparisons with related concepts or scenarios Use hypotheticals or projections to illustrate your point Include tweets or quotes from industry leaders to add credibility Suggest the counterintuitive solution/alternative approach Make a bold, declarative statement in the H2 Propose a better way of doing things Explain why it works, despite seeming counterintuitive Offer actionable tips/a framework for implementing your suggestion Encourage experimentation and adaptation Address objections A rhetorical question, or bold, declarative statement in the H2 Anticipate and address potential criticisms of your approach Use analogies or comparisons to make your point more relatable Reinforce the benefits of your solution Final thoughts Summarize your main points Reinforce your central/counterintuitive argument End with a thought-provoking statement/question Further Reading [Related article 1] [Related article 2] [Related article 3]   Blog Writing Guidelines and Checklist Resources What makes quality content? - Blog Blog Writing Templates Brief Writing a How To / Detailed Guide Writing a Beginner’s Guide Writing Thought-leadership & Opinion Copy Expanded Definitions or Topics Comparisons Lists & Listicles Checklist Writing Guidelines Description     Who is the intended audience At the very least must be believers. What are they expecting, what do they like/dislike, what content suits their needs best, etc. Write to them specifically.     Use only 1

mean "title"

is a title. Like a book, there should only ever be one title for each blog post Use

for sub headings There should be several

subheadings for every blog piece Use

for sub-sub headings

should be used for sub-sub headers (optional)     Link out to at least 3 external resources Link out to websites that are not JFP properties e.g. Authors, bible verses (e.g. Bible Gateway), other relevant blogs, etc. These external links should open in a new tab (done automatically)     Link to at least 5 internal resources Link to JFP content e.g. videos, blogs, etc. Try to drive traffic to other blogs. Must NOT open in a new window. Search for existing JFP blogs on Google –-> In the search bar type in “site: jesusfilm.org/blog/ [insert topic]”   Include a featured image A featured image is the image that is used to be shown on the blog page (represents the blog you wrote). Get legally free images to use: Pexels.com , Unsplash.com Include at least one other image or video Include other relevant images or video within the blog post to help break up the content and provide supplementary media. This exudes the ‘featured’ image.     Word count Try to write at least 2000 words. More words allows for better understanding of context. Allows for more natural inclusion of relevant keywords. This is dependent on the blog type. E.g. a listicle blog would not need 2000 words     Make it scannable for easy reading You should use consistent formatting throughout, break up long paragraphs for better readability, and use bold text to highlight key points. Use numbered lists and bullet points. Keeping reading level between grade 3 to 9. Use Hemingway Editor for gauge. Include bullet points or numbered lists Every blog post should include at least one list (bullets or numbers). Important for skim-ability.   1st paragraph/Intro The first paragraph needs to identify what the blog is about and what the users should expect to get from it. Very important. Keep intros fluff free. Keep it short and focus on establishing your expertise or the post's value. Answer real user questions:  Find and answer relevant questions people are asking about the topic. Use keyword research provides from SEOs. Title should be descriptive Longer titles that are more descriptive resonate better with users. It provides clear context before the user has to start scrolling. Offer content variety Use examples, case studies, or statistics to support your points, and add visuals to break up text and illustrate concepts. Be objective Maintain an objective tone throughout. Present facts and features without bias.   Write YOUR opinions in YOUR voice While you represent JFP, it is important to share your personal view. This is important for SEO because it differentiates our content from others. Don't be afraid to show personality through your own style of writing. People trust people, people don’t trust companies. Back up your opinion with evidence Challenge conventional wisdom, but back up your claims with data, expert opinions, and case studies. Your opinion matters but it should have proof. ( Credibility ) Use analogies Draw comparisons between more tangible topics to help readers understand complex ideas. Jesus used parables, we use analogies. Encourage engagement Use pull quotes to encourage social sharing of your key points. Offer practical tips Give readers actionable steps to implement your ideas, even if on a small scale.   Trustworthiness Incorporate the problem-solution-proof formula to establish credibility, prove why your tips work, and why you/JFP should be trusted. Try to create credibility. Try include IRL experiences Try to center first-hand experience through personal anecdotes, quotes, reviews, or interviews. This adds value for readers making decisions.   Include a CTA List posts (especially tool based ones) are inherently actionable, and will make a reader want to go away and do something. Show them the way, with an unmistakable CTA. E.g. sign up for email. Guest Post Guidelines for Guest Authors Your “About the Author” bio A short bio : Please keep this to 70-75 words max. Imitate the style of any you see on the JFP blog page . A hi-res image of yourself : It should be a square. Dimensions: minimum 300x300 pixels. The basics An ideal length for a typical blog post is 2,000-2,500 words or more . Your blog title should be descriptive and specific . Readers appreciate a title that clearly indicates what is being covered in the post. Avoid teaser titles. Create a brief introductory section (3-4 paragraphs max) with a final “thesis statement” at the end. Who the speaker is (through context clues) and the target audience should be immediately apparent. A concluding sentence at the end of the blog is encouraged. Provide statistics (if applicable) and cite your sources (hyperlinks preferred) . Include credible, external sources to link to on the web that support your argument. Aim for simplicity and skimmability of your blog post. Write at a 6th-8th grade reading level and no higher. Use the Hemingway app . Show youʼre a real person, not AI , by including anecdotes and real-life examples. Break up your post into several sections, with headings and subheadings to clearly convey (no teasers) what each section/subsection covers. Each section/sub-section header should be easy to scan in the table of contents. Create plenty of white space by avoiding lengthy paragraphs . Include bulleted and/or numbered list for important points. Keep your topic focused and on track from beginning to end. General content guidelines An overall theme/topic will be provided . Cover the theme in your voice and style, lending it an angle thatʼs unique to you. Niche is good! We will help shape the content to align well with our content calendar and blog strategy. We will also suggest bolded content and callouts (quotable, will appear in large red text). Allow user intent to guide your content. Consider: Who is your audience? What is the audience's question/problem? Your blog should provide answers. Why should readers care about this content? Ensure you hold their interest. Focus not only on what you want to say, but what the audience needs/wants to read. Use the keyword research provided. If appropriate, we may provide keywords to include during the drafting and revision process. We will also look for opportunities to link to other Jesus Film Project blogs and internal links from your blog post. Creative Creating images for the JFP website Image File Types and Optimization: Most images should be saved as JPG files to ensure detailed colors and smaller file sizes. For images requiring a transparent background, save them as PNG files. Always "optimize for web" when saving any image. Aspect Ratios and Sizing: General Horizontal Images: A 16:9 aspect ratio is preferred for most horizontal images, matching our movie clips. You can verify your cropping at  https://aspectratiocalculator.com/16-9.html . Full-length "Hero" banner image (main page): Typically 1920 x 1080 pixels. The web team can overlay text and darken the opacity of the image as needed. Other horizontal images on webpages: Usually 700 x 394 pixels. DevCard Image (main page): Typically 393 x 516 pixels (portrait layout). This image will need to be darkened to ensure text copy is visible. Blog Post Images: Currently 1200 x 627 pixels. Leader Portrait Images ( see "Team" page ) : 1240 x 1560 pixels. Creative/Branding Creative/PrintShop Web Experience Best Practices for File Names and URLs Ditch the junk: No underscores, weird characters, or spaces in your file names or URLs. Just don't. Dashes are your friends: Use dashes instead of spaces. They're totally fine. Search engines recognize them as word separators. Capitalization counts (sometimes): Title casing is cool for file names like "Document.pdf" or "Video.mp4," but keep extended URLs all lowercase (like "jesusfilm.org/watch," not "jesusfilm.org/Watch"). Version it up: Even if you think it's the final version, slap a version number on it. You never know! Think like a downloader: Name files in a way that someone searching for it in the future will be able to find it. Maybe add "JFP" at the start. Throw in the year at the beginning or end, too. Why all the rules? Mostly for SEO (search engine optimization), but also to avoid links looking weird and to prevent issues with older browsers. Plus, keeps things tidy. Internal vs. Public: You might get away with anything for internal stuff, but sticking to best practices saves headaches later, especially if you plan to share files publicly. Further reading: https://www.woorank.com/en/blog/underscores-in-urls-why-are-they-not-recommended Cru Policy on Bit.ly Links Prohibited Use Bit.ly URL shortener links are prohibited for any emails using Cru IPs in the sending process. Reason Use of Bit.ly links results in a "ReturnPath Certification" violation. Consequence Violations lead to Cru emails being blocked due to the lack of certification whitelisting. Check the Bit.ly Link Add a  +  to the end of any bit.ly link in your browser address bar (e.g.,  bit.ly/xxxx+ ) to preview the destination page and inspect the URL before navigating. What is an SME? SME most commonly stands for Subject Matter Expert , an individual with deep, specialized knowledge in a particular field, process, or topic, sought for their insights and problem-solving skills. The role of a Subject Matter Expert (SME) is crucial across various industries and often involves: Content Development: Providing accurate and detailed information for training materials, technical documentation, and project specifications. Consultation and Guidance: Serving as a key resource for project teams, stakeholders, and clients to ensure alignment with best practices and industry standards. Problem Solving: Applying specialized knowledge to diagnose complex issues and develop effective solutions. Quality Assurance: Reviewing deliverables to ensure technical accuracy and compliance. Google Doc or PDF? This is the current best practice: Links to Google Docs are usually for internal use only for staff, partners and patrons. Links to PDFs are typically for public use. An updated PDF can be reuploaded to the same area, so URL stays the same. Suggest using a version number at the bottom for changes, so you know which one is the most current. Updates can be made in Google Docs as normal, saved, exported as PDF and then someone can upload to Media. With picking the right options, the file URL can stay the same and Vanity URL stays the same. More in depth information (AI): A Google Docs link might not be ideal on a website because it can disrupt the visual flow of your page by opening a separate Google Docs interface, potentially requiring users to log in to view the content, and may not seamlessly integrate with your website's design, making the experience less user-friendly ; furthermore, depending on the sharing settings, users might be able to edit the document if you haven't set appropriate permissions. [ 1 , 2 , 3 , 4 , 5 ] Key reasons why a Google Docs link might not be good on a website: [ 2 , 3 , 4 ] Visual disruption: When a user clicks a Google Docs link, they are taken away from your website to a separate Google Docs page with a different layout and navigation, which can be jarring for the user experience. [ 2 , 3 , 4 ] Login requirement: If the Google Doc isn't set to "Anyone with the link" viewing permission, users might be prompted to log in to their Google account to access the document, creating an extra step for the viewer. [ 4 , 6 , 7 ] Lack of design control: You cannot fully customize how the Google Doc appears within your website, potentially leading to a mismatch in style and branding. [ 2 , 3 , 5 ] Editing concerns: If you share the Google Doc with "Editor" access, users could inadvertently make changes to the document when they click on the link. [ 1 , 4 , 7 ] Better alternatives to using a direct Google Docs link on a website: [ 2 , 5 ] Embed the document: Use the "Publish to the web" option in Google Docs to generate an embed code that can be directly integrated into your website, allowing for better visual control. [ 2 , 5 ] Export as PDF: Download the Google Doc as a PDF and upload it to your website, ensuring a static and consistent view for all users. [ 2 , 3 , 5 ] Copy and paste content: If necessary, manually copy the content from the Google Doc and paste it directly into your website's text editor, formatting as needed. [ 2 , 3 , 5 ] Generative AI is experimental. [1] https://ecins.com/us/the-limitations-and-dangers-of-using-google-docs-and-spreadsheets-for-student-support-case-management/ [2] https://learninginhand.com/blog/google-document-url-tricks [3] https://www.reddit.com/r/gsuite/comments/ki2bfq/why_doe_embedded_google_docs_look_so_terrible_it/ [4] https://www.youtube.com/watch?v=2X0XrRBKgOU [5] https://support.google.com/docs/answer/183965?hl=en&co=GENIE.Platform%3DDesktop [6] https://www.reddit.com/r/sysadmin/comments/o3dja3/clicking_google_doc_links_safety_concerns/ [7] https://support.google.com/drive/answer/2494822?hl=en&co=GENIE.Platform%3DDesktop Landing Page Process Overview of Process This document outlines all the parts involved in creating a landing page. There are several phases that need to occur in order for a landing page to be designed, created, launched and maintained. The typical length of time for a landing page to be created, from discovery to launch, is approximately 8 weeks. This is contingent on stakeholders and other participants keeping to the timeframe and keeping the project within scope. Any changes in scope or delays in deliverables by their due dates, may delay the launching of the landing page. For admins - access the original Google Drawing of the landing page process here . The project and/or phases need to have roles assigned. Use RACI matrix . What is a landing page? A landing page is simply a single web page that’s built with one goal in mind—getting visitors to take a specific action (e.g. fill in form, donate, sign up to email, etc). Think of it as a targeted “destination” on the website, where someone arrives after clicking an ad, an email link, or a social‐media post, etc. What is a discovery meeting? A discovery meeting is the first structured conversation between the Web team, Story team, project managers and stakeholder. Its sole purpose is to uncover everything you need to know in order to design the right solution—whether that’s a new website, a marketing campaign, a software project, etc. Where are the discovery questions? This is a list of generic discovery questions that will be asked of the Stakeholders. Not every question may be applicable depending on the circumstance. This is just a guide use at your own discretion. Phases 1: Discovery Assemble the team - Once the HOS ticket has been approved by the steering committee, project managers need to identify the people to be on the project. I.e. Web team members, Story team members, Stakeholders, etc. Discovery meeting   (web team will lead this) - Project managers schedule a discovery meeting with all team members and stakeholders to identify: Identify scope To gain more context Identify hinderances Understand the strategy Ideate Ask clarifying questions, etc. Assets and Expectations - We need t identify what assets are assets required, these need to be fully available before phase 2 starts.  Who is providing the assets? Images - Where can we get them? Videos, Where to we get the videos? (Note: we don’t upload mp4 files to the site, video need to be YouTube needs embed only) Who is providing the copy? Is the stakeholder or the GBMS Story team creating the copy for the landing page? Accept/Reject - Based on what is uncovered in the discovery the team will decide if they can/should continue Proceed or Postpone - Our the web teams needs (required assets) have to be fulfilled before we start the project. Project will be postponed or delayed in starting if we don't have all the assets required. Copy is an exception if GBMS is creating the copy If there is no strategy, or the strategy does not align with Jesus Film's objectives, the project will be rejected. Due to limited resources we can only commit to projects that are clearly aligned to the organization objectives and goals. 2: Content & Design Wireframes - After the Discovery meeting, the copy writers (Story team) will collaborate with web design (Web team) to develop content, mock-up layouts and eventually wireframe. Further collaboration - Copy writers and web designers may need to collaborate with SEO (Web team) if this landing pages needs to rank in search engines. Deliverables - The designers (Web team) will present wireframe (this not a finished design) to Stakeholders for approval and feedback. Feedback and update - if there is feedback and updates required, these will need to be re-delivered and approved. There is only one round of revisions approved to keep the project in scope. Other changes can be done after the page is live. Finalization of wireframes - Once approved, the team can move onto phase 3. What is a wireframe? A wireframe is a simple, low‑fidelity sketch of a web page or app screen that shows the basic layout and structure—where elements like the header, navigation, images, text blocks, and buttons will go—without any colors, fonts, or detailed graphics. Think of it as the blueprint or floor plan. 3: Build Provide assets - All images, copy, videos and other assets need to be given to the web developer (Web team) in the correct format, size, compression etc. Functionality - UX (Web team) to collaborate with web developer to communicate desired functionality, aesthetics and expectations of finalized landing page Development - Web developer will proceed on building out the landing page on a staging site Approval - Both web team and creative (Story team) need to approve final build of landing page (stakeholders are not included in approval process as this point) Review - Stakeholder are able to review the landing page. No further changes will be accepted as this point. Updates can be made post launch. All landing pages need to built on the staging site first, not the live/production version of the website. The staging site can be found here: develop.jesusfilm.org 4: Launch Web team to launch page into production (from staging site) Link to landing page URL will be shared to project managers who will share it to respective team members 5: Updates (Post Launch) If there are required updates that are simple and easy to fix, such as changing and image, or changing some text, then it will be done post launch If there is a significant updated or change required a new HOS ticket will need to be processed. Rubric for Website Development Rubric for Website (including webpages and CPT) Development or Feature What are we creating or building? Why are we doing this? What benefit or value does it provide (ROI)? Is it worth doing? What audience needs this (understand the user, challenge or validate assumptions)? Others provide this value already? What are the business goals and how will they be measured? What is the clear call to action or next step for each page? Stakeholders: Influencers (usually with veto power)? Finances for development, design, marketing, etc.? Who creates content, form, function, analytics? Who approves and then signs off on Scope of Project? Who implements/provides data model, wireframe, etc.? GBMS team who will develop or approve design, text copy, image assets, etc. Who leads the delivery of a viable product or service? Who will manage content, assets, adds, deletes, updating? Who will market/promote? Ongoing support or SLA (adding users, onboarding, etc.)?  Who uses and acts on data, including emails from forms? Considerations: Overall JFP/Cru business strategy and existing timelines. All development uses Branding Guidelines. Includes page templates, navigation, etc. User-centric design (users are expressing the need for this). Consider the look of the “responsive” design, especially on mobile devices. SLA (service level agreement): What GBMS Operations will do (must document what we can realistically provide, create or maintain). Note all assumptions (things we will not do). What WPVIP will do (uptime, page load speed, ticket response, etc.) Data Insights reporting. All this is listed in the Scope of Project. More details may be needed: Strategic URL naming (may also need a redirect) Hidden or public facing (noindex/nofollow)? Source code “keywords” and “description”? Do we need to set up first in Staging? Special plugins needed that we don’t already have available? Analytics Basic UX: Strategy - User needs, business goals Scope - Requirements, specifications Structure - Information Architecture Skeleton - Navigation and layout (wireframing) Surface - Visual UI design & coding When building an inquiry/comment form: First name only or first and last (two fields) Email address What other fields? Email goes to who? Notification information? Any text copy for Subject line, etc.? Other: https://form.asana.com/?k=OeMUzqgwHGrIKlTE5Zz8Eg&d=657768513276 What is a Responsive Website? A responsive website is a website designed to automatically adjust its layout and content to fit different screen sizes and devices, like desktops, tablets, and smartphones, ensuring a consistent and optimal viewing experience regardless of the device used to access it; this is achieved through techniques like flexible grids, responsive images, and CSS media queries.  Key points about responsive websites: Adapts to different screens: The website automatically rearranges its elements to fit the screen size of the device being used, whether it's a large desktop monitor or a small mobile phone. Improved usability: Users can easily navigate and interact with the website on any device without needing to pinch or zoom excessively. Single codebase: Responsive design typically uses a single set of code that adapts to different screen sizes, simplifying development and maintenance. CSS media queries: A core component of responsive design, media queries are CSS rules that apply different styles based on screen size or other device characteristics.  Additional: "Resolution switching" refers to the practice of dynamically serving different sized versions of the same image to a user based on their device's screen resolution, allowing the browser to choose the most appropriate image size for optimal viewing quality on various displays, typically achieved using HTML attributes like "srcset" and "sizes" within an tag; essentially, providing a higher resolution image for high-resolution screens and a smaller one for lower resolution screens while maintaining the same visual content.  Something is broken on the website Encountering an issue on our website, such as a broken link, a missing image, or a typographical error, can be frustrating. We understand that these imperfections detract from your experience, and we appreciate your diligence in helping us maintain the quality of our online presence. To ensure that these issues are addressed efficiently and directed to the appropriate teams, we kindly request your assistance in reporting them. Our website is a complex ecosystem, with different sections managed by various individuals and specialized teams, each responsible for specific areas. Therefore, sending your report to a centralized point is crucial for proper routing and resolution. Please send an email to info@jesusfilm.org with the following details: A screen capture or a detailed description of the issue. A visual aid, such as a screenshot, is often the most effective way to convey what you are encountering. If a screenshot isn't feasible, please provide a clear and comprehensive description of the problem. The URL (link to the website page) where the issue is located. This is an essential piece of information that allows us to pinpoint the exact location of the problem without guesswork. Once your email is received, our dedicated team at info@jesusfilm.org will log your report. They will review the information provided and forward it to the correct department or individual responsible for that specific area of the website. This streamlined process ensures that your feedback reaches the right hands, facilitating a quicker and more effective resolution. Your active participation in identifying and reporting these issues is invaluable to us. It helps us to continuously improve our website and provide a seamless and engaging experience for all our visitors. Thank you for helping us make our website the best it can be! Web Discovery Questions Jesus Film Project Website Stakeholder Discovery Document Template Purpose of this document This discovery document is designed to help Jesus Film Project  web team gather clear, consistent, and actionable website requirements from internal stakeholders and teams. It is intended for use in stakeholder interviews, intake meetings, workshops, and planning discussions so that website decisions align with ministry goals, audience needs, global realities, and operational constraints. Both stakeholders and PMOs should fill out the ir respective sections Rubric for Website Development Rubric for Website (including webpages and CPT) Development or Feature. Learn more . 1. Stakeholder Overview  Why this matters: This section establishes who is making the request, what team they represent, and what role they play in the success of the initiative. It also helps clarify decision-making authority, influence, and accountability early in the process. Stakeholder details Stakeholder name: Title / role: Team / department: Date: Facilitator: Related initiative / project name: Other involved stakeholders: Level of decision-making authority: Regions / languages / ministries represented: Discovery questions What team or ministry area do you represent? What is your role in this initiative or request? What responsibility does your team have for the website, if any? Who else should be involved in this conversation? Who is the final decision-maker for this request? Which departments, regions, or language teams are affected? Is this request driven by a specific campaign, strategic initiative, ministry need, or operational issue? Has this need been discussed before? If so, what was decided? 2. Ministry and Organization Goals Why this matters: Website requests should support broader ministry and organizational objectives, not just isolated preferences. This section helps connect website needs to mission impact, strategic priorities, and measurable outcomes. Discovery questions What ministry objective is driving this request? What organizational or team goal does this support? Why is this important now? What problem are you trying to solve, or what opportunity are you trying to capture? How does this request support the mission of JFP? How does this request serve evangelism, ministry partnership, resource distribution, or disciple-making? What outcome would make this request successful from your team’s perspective? Is this tied to a larger strategic initiative, annual objective, or leadership priority? What would happen if this request is delayed or not implemented? Is this a short-term need, long-term need, or both? 3. Audience and User Needs Why this matters: Effective website decisions begin with a clear understanding of who the user is and what they are trying to accomplish. This section helps ensure requests are rooted in real audience needs rather than internal assumptions. Primary audiences to consider Decision-makers at other Christian ministries focused on evangelism Individual believers who want to evangelize more effectively Discovery questions Who is the primary audience for this request? Is the audience external, internal, or both? What type of ministry leader, partner, or user are you trying to reach? What does this audience need most from the website? What are they trying to do, learn, find, or accomplish? What are their likely pain points, frustrations, or barriers? What questions do they typically have before taking action? What level of awareness or familiarity do they already have with JFP? Are there audience differences by region, language, ministry maturity, or church context? What might success look like from the user’s point of view? 4. Key Website Pain Points Why this matters: This section surfaces what is currently not working so teams can address root issues rather than symptoms. It also helps distinguish between perceived problems and truly high-impact barriers. Discovery questions What is not working well on the website today? Where are users getting stuck, confused, or dropping off? What complaints, feedback, or recurring questions do you hear from users or internal teams? Are there gaps in content, functionality, navigation, or messaging? Are there parts of the site that feel outdated, unclear, hard to use, or misaligned? What internal processes make it difficult to support this area of the website? What workarounds are teams currently using? What is the biggest pain point you would fix first? Are these issues affecting one audience, multiple audiences, or global users broadly? Which pain points are urgent versus inconvenient? 5. Content and Messaging Needs Why this matters: Content is often the clearest expression of ministry value, clarity, and trust. This section helps identify what content is needed, who it is for, and how messaging should support both ministry impact and user action. Discovery questions What content is needed to support this request? What existing content already exists, and what is missing? Does the current messaging clearly explain the value of this ministry, resource, tool, or initiative? What does the audience most need to understand, trust, or believe before taking action? What specific pages, content types, or assets are needed? Are there key calls to action that need to be strengthened or clarified? Does the content need to serve different audience segments differently? Are there theological, ministry, or brand considerations that need to shape the messaging? Who owns the content strategy, writing, review, translation, and updates? What content should remain evergreen, and what content will require regular maintenance? Are there stories, case studies, testimonies, or field examples that should support this content? What tone should the content reflect for this audience? 6. Language and Localization Considerations Why this matters: Because JFP serves a global audience, language and localization cannot be treated as afterthoughts. This section helps clarify translation needs, regional differences, cultural adaptation, and operational realities across markets. Discovery questions Which languages are needed for this request? Is direct translation sufficient, or does content need cultural adaptation? Are there region-specific user needs, examples, offers, or calls to action? Which markets or countries are most important for this initiative? Are there languages that should be prioritized first? What is the translation and localization workflow today? Who reviews translations for quality, clarity, and theological accuracy? Are there known challenges with multilingual publishing, governance, or maintenance? Will all features and content be available in all languages? How should the site handle language selection, fallback content, and untranslated pages? Are there localization considerations related to imagery, examples, ministries, testimonies, or terminology? What would make this experience feel more locally relevant and useful? 7. Functional and Feature Requirements Why this matters: Stakeholders often express needs in terms of desired features, but the underlying requirement may be different. This section helps clarify what users need to do, what the business needs to support, and what functionality is essential versus optional. Discovery questions What does the user need to be able to do on the website? What feature or capability is needed to support that action? Is this a new feature, improvement to an existing feature, or replacement of a current process? What specific functionality is required? Are forms, downloads, search, filtering, account features, integrations, or content personalization involved? Does this request require different functionality by audience, language, or region? Are there required user journeys or business rules? What systems, teams, or workflows would this feature affect? What does a minimum viable version look like? What is essential on day one, and what could be phased later? Are there accessibility, security, privacy, or compliance considerations? What feature requests are truly necessary versus simply desirable? 8. UX and Journey Considerations Why this matters: A website can have good content and strong functionality but still fail if the user journey is confusing. This section helps identify how users move through the site, what actions matter most, and where better clarity or guidance is needed. Discovery questions What is the ideal user journey for this audience? What are the key entry points into this experience? What action should users take next after landing on the page? Where do users need more clarity, reassurance, or direction? What steps in the journey feel too complicated, long, or unclear? What information does the user need first, second, and third? What questions or objections should the page or experience answer? Are there important journey differences by device, language, or geography? Should the experience drive exploration, conversion, engagement, or relationship-building? What would a better user experience look like in practical terms? Are there known navigation issues affecting this journey? What examples from other sites or experiences feel relevant, useful, or inspiring? 9. Technical / Platform Considerations Why this matters: Even strong ideas can fail without technical feasibility, platform alignment, and realistic implementation planning. This section helps capture constraints, dependencies, and opportunities early enough to plan wisely. Discovery questions Are there technical constraints we need to know about? Does the current platform support this request? Are integrations required with CRM, analytics, DAM, translation systems, forms, email, or partner tools? Does this request affect performance, security, scalability, or maintainability? Are there known issues with the current CMS, templates, or publishing workflows? Does the request require custom development, third-party tools, or vendor support? Are there mobile, browser, or device-specific considerations? Are there accessibility standards this solution must meet? Is there existing technical debt that could affect this request? What internal technical resources are required to support this? Are there data privacy, consent, or regional compliance issues to consider? What technical assumptions need to be validated before moving forward? 10. SEO, Search, Analytics, and Measurement Why this matters: A ministry website still needs to be discoverable, measurable, and optimizable. This section helps ensure requests consider findability, onsite search, performance data, and meaningful success indicators from the start. Discovery questions How should users find this content or experience? Is organic search an important traffic source for this initiative? What search intent is this content or feature meant to serve? Are there important keywords, topics, or questions this should address? How should internal site search support this experience? What analytics are currently available for this area? What data do you already have about user behavior, performance, or demand? What metrics would indicate success? Are conversions clearly defined? Do we need event tracking, funnel tracking, scroll tracking, form tracking, or campaign attribution? Are there SEO risks such as duplication, localization complexity, or weak information architecture? What performance benchmarks or baselines should we compare against? 11. Governance, Approvals, and Ownership Why this matters: Many website issues are not caused by technology, but by unclear ownership and inefficient workflows. This section helps define who is responsible for decisions, content, approvals, updates, and long-term stewardship. Discovery questions Who owns this initiative from a business or ministry perspective? Who owns the content once it is published? Who approves strategy, content, design, theology, and technical implementation? What teams need to review or sign off? What is the current workflow for creating, reviewing, translating, and publishing content? Where do delays usually happen? Who is responsible for ongoing maintenance and updates? How often will this need to be reviewed or refreshed? Are there governance policies or standards that apply? Is there confusion today around roles, approvals, or decision rights? What would make the workflow more efficient and sustainable? Who will be accountable for outcomes after launch? 12. Risks, Blockers, and Dependencies Why this matters: This section helps teams anticipate what could slow down, complicate, or weaken implementation. It brings hidden concerns into the open so they can be addressed before they become project failures. Discovery questions What risks do you see with this request? What could prevent this from succeeding? Are there budget, staffing, timing, or technology constraints? Does this depend on other teams, systems, approvals, or external partners? Are there unresolved strategic questions that need leadership input? Are there theological, brand, legal, or cultural sensitivities involved? Is this request dependent on translation, content creation, or technical infrastructure not yet in place? What assumptions are we making that may not be true? What could cause delays after the work begins? What previous lessons or failed attempts should inform this effort? What is the greatest implementation risk? What would reduce uncertainty before moving ahead? 13. Priority Level and Implementation Readiness Why this matters: Not every request should be treated equally. This section helps distinguish strategic, urgent, and high-impact work from lower-value ideas or requests that are not yet ready for execution. Discovery questions How important is this request relative to other ministry and website priorities? Is this urgent, important, or exploratory? What is driving the timeline? Is there a deadline, event, campaign, launch, or external dependency? What is the cost of not doing this? What is the expected impact if this is implemented? Is the request clearly defined enough to move forward? What information is still missing before this can be scoped? Is content ready, or still being developed? Are stakeholders aligned on the need and desired outcome? Could this be delivered in phases? Is this a must-have, should-have, could-have, or not-now item? Priority assessment Priority level: Business / ministry impact: Audience impact: Urgency: Level of effort: Readiness status: Recommended phase: 14. Summary and Recommendations Why this matters: A discovery process is only useful if it leads to clarity and action. This section captures the most important findings, recommended next steps, and decisions needed to move forward. Summary fields Request / initiative name: Stakeholder / team: Primary audience: Core problem to solve: Desired outcome: Key user need: Key website need: Key risks: Key dependencies: Recommended priority: Recommended next step: Owner: Proposed timeline: Summary questions What is the core need behind this request? What problem are we solving for the audience and the ministry? What requirements are clearly defined? What needs more validation, research, or alignment? What should happen next? Who needs to make a decision? What should be prioritized now, later, or not at all? What recommendation best balances ministry impact, user value, and operational feasibility? WordPress Info, Tips and Helps for using WordPress, including Gutenberg. Featured Image What is a Featured Image and how do I put one on my page? The  Featured Image , which is also called the Post Thumbnail (per the WordPress Codex), is the representative image of a post or page. It is very important to select a featured image for your posts and pages, because this is most often what will show when shared on social media, or texting platforms. Importance of Featured Images: Visual Appeal: They make your site look more appealing and professional. Engagement: They help attract visitors and encourage them to click and read your content. Social Media Sharing: They are used as thumbnails when your posts or pages are shared on social media. Search Engine Optimization (SEO): They can help improve your search engine rankings by providing a visual representation of your content. Branding: They can help establish a consistent visual identity across your site.  How to use Featured Images in Gutenberg: Edit Post/Page: Open the post or page you want to set the featured image for. Access Featured Image Settings: In the right-hand sidebar, find the "Featured Image" section. Select or Upload: Choose an image from the Media Library or upload a new one. Set Featured Image: Click the "Set featured image" button to assign the image. For most WordPress themes, a featured image size of 1200 x 628 pixels is generally recommended. This size works well with a variety of themes and ensures the image looks good when shared on social media platforms. However, the optimal size can vary slightly depending on the specific theme and its layout.  Details video on YouTube WPBeginner.com article Responsive Image Strategy Image Optimization for Devices The website's responsive design generally scales images for different screen sizes. However, specific images may require optimization for mobile, tablet, and desktop displays. Previous Approach Prior to the current method, a custom CSS solution was used to manage image variations across devices. New Method A new and improved method for handling different images for smartphones versus monitors is now available. Training Resource View the instructional video for detailed guidance on implementing the new image optimization method. Please watch the video to see how it's done. WordPress Releases Info on the latest versions https://wordpress.org/news/category/releases/ More info: https://make.wordpress.org/core/ Plugins: Gravity Forms- https://docs.gravityforms.com/gravityforms-change-log/ Rank Math SEO- https://rankmath.com/changelog/free/ WP Popups- https://wppopups.com/docs/changelog/ Copy a Block How do I copy a Block from another page? First, go to the page that has the  Block you want to copy Next, click on the Document Overview at the top left (or Shift+Alt+O ) You will now see a dropdown of the List View of all your Blocks Find the Block you want to copy and click on it In the List View that Block will now be highlighted. Click the three dots for that Block and then click Copy Now go to the page where you want to copy the Block to On that page, click the plus sign where you want to copy that Block Type in the Block name and when it comes up on the page, click the icon and then the Ctrl & V keys You should now see that Block with all the copied data from the other page Bulleted List line-height Is there any way to reduce the line-height of a bulleted list? On the page, highlight the entire list On the right, click the three dots in Typography in the Block section In the dropdown, click Line height Click just outside of dropdown Adjust line height Example: jesusfilm.org/unpacking-parables Test page content to existing page I’m redesigning a page in a test area. How do I move that page when I’m done to replace the old page? First, when in the new design, click on the three dots in the upper right of screen Click the Code editor in the dropdown to switch to code view Copy all the code (Ctrl A and Ctrl C) Go to the page that you will update If you want to keep a copy of the old look, then click duplicate Now on the page that you will update, click to edit If still in the Code editor mode, just hit Ctrl A, then Ctrl V Go back to Visual editor (back in the three dots dropdown) mode and check your work If all is okay, then save and the page will be updated JFP Brand shape for image How do I get my image on a page to have the JFP Brand shape? Go to the page with the image you want to update Click the image On the sidebar on the right, click the Styles tab In the Styles area click the Clip Path button You will see the image change to the JFP Brand shape Update the page and you’re done Example: jesusfilm.org/resources/pray/2025-06-country Make a page not searchable How do I make a page so it’s not searchable when someone does a Google search? First, go to the page In the upper right, click on the Rank Math button In the dropdown, click from General to the Advanced tab You will see the ROBOTS META Click the No Index and Nofollow checkboxes For more info on those choices, click the question mark next to each Update the page to save your work Schedule update to existing page Can I schedule an update to an existing webpage? Yes, it’s called a Revision Find the page you want to update and click Revision (not Edit ) When page opens, click the Publish link on the upper right Add date and time, and close Now edit the page and click purple Save draft button when done You can edit more or even come back later if needed When finished, click Save draft again and then the purple Approve button (do not need to Submit for approval) When you leave the page, you can see the status of your update in the Revisions tab on the left If any further updating is needed to the page before it publishes, open that page in Revisions RACI Matrix What is RACI? In business and project management, a responsibility assignment matrix (RAM), also known as RACI matrix: Responsible Accountable Consulted Informed This model describes the participation by various roles in completing tasks or deliverables for a project or process. RACI is used for clarifying and defining roles and responsibilities in cross-functional or departmental projects and processes. Source: AIHR   Role What it means? Details R: Responsible This refers to the person or role that performs the task or work. They are the ones “doing the work.”\ Who is responsible for getting the work done? This is the individual who executes a task, also known as the ‘hands on’ individual They will generally report to a manager A: Accountable This is the role that has ownership of quality and the end result. They are the ones who delegate work to those responsible and have the authority to make final decisions. Who oversees the task This is the individual who ensures the work gets done properly. They are not hands-on, but rather responsible for managing the people who are executing tasks and ensuring that work is completed on time and at the required quality. C: Consulted These are the people whose input is sought for the task or decision. Their opinions are valued and they contribute to the completion of the work but they do not carry out the task. Who needs to assist the completion of a task with additional information or support? This individual is not directly responsible for a task However, they do provide information that assists the person responsible for a task They are generally consulted for their expertise in a specific area I: Informed These are the stakeholders who need to be kept in the loop about progress and decisions, but they do not have a direct role in the task or decision. They are essentially the recipients of updates and outcomes. Who needs to be kept up to date on the progress of a task or deliverable? This is generally an upper management stakeholder or potentially a client They do not have immediate input on the project but may be the project’s owner                     ASJ Help Scout Website https://secure.helpscout.net/ Manual ASJ Help Scout Manual