Marketing

Global Marketing and Brand Services (GBMS)

Blogs

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
Blogs

Blog Template: Comparisons

 

This is a template for writing "comparisons" for blogs.  Use these section to organize and optimize your blog writing.

Title

Introduction


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

2. Difference 2

3. Difference 3


Feature Comparison

Feature Category 1


[Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences]


Feature Category 2


[Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences]


Feature Category 3


[Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences]


User Experience and Interface


Customer Support and Resources

[Optional: Add image, video, social media embed, or screenshot to illustrate real life reviews and experiences]


Use Cases

When to choose ABC

When to choose XYZ


Alternatives to consider


Final thoughts




 

 

 

Blogs

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


Introduction

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

 

 

 

 

 

 

 

Blogs

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


Introduction


1. [Benefit-Focused List Subheading]

E.g. Capture trending traffic by stealing Top Stories keywords from your rivals

Explanation of the first point.

Include: 


[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]


  1. Step one

  2. Step two

  3. Step three


...

X. [Benefit-Focused List Subheading]


Explanation of the final point in your list



Conclusion/Wrapping up




CTA

Example CTA:

Want to learn more about growing your faith? Check out these related articles:

 

 

 

 

 

 

 

Blogs

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


Introduction


What is [topic] and why is it important?


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]?


Key things to know about [topic]

Best Practice 1

Best Practice 2

Best Practice 3


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]


Helpful resources to learn more


Wrapping up

Summarize and offer a couple of unheard tips, quotes, or insights. Offer some final encouragement, and link to further resources: 


Further Reading




Blogs

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


Introduction


You can also include:


Why You Can Trust Me/Why I Am A Reliable Source

Use the PSP (Problem-Solution-Proof) formula to establish credibility


Step 1: [present tense verb]


Step 2: [present tense verb]


Step 3: [present tense verb]


Final thoughts


Next steps



Blogs

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


Introduction


Outline the current state of things

 

Tease the immediate risk


Outline the problem

[Problem 1] Start building in more tangible evidence


[Problem 2] Start building in more tangible evidence


Dive into the far reaching implications


Suggest the counterintuitive solution/alternative approach


Address objections


Final thoughts


Further Reading

 

Blogs

Blog Writing Guidelines and Checklist

Resources

What makes quality content? - Blog

Blog Writing Templates

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 <h1>
  • <h1> mean "title"
  • <h1> is a title. Like a book, there should only ever be one title for each blog post

Use <h2> for sub headings

There should be several <h2> subheadings for every blog piece

Use <h3> for sub-sub headings

<h3> 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.





Blogs

Guest Post Guidelines for Guest Authors


Your “About the Author” bio

The basics

General content guidelines

Creative

Creative

Creating images for the JFP website

Image File Types and Optimization:

Aspect Ratios and Sizing:

Creative

CONTENT Writing Norms - Drafting, Editing and Revisions

See attachments section for linked guide.

Creative

CONTENT Gathering Norms - Pursuing Leads + Research, Interviewing, Citations

See attachments section for linked guide. 

Creative

Content Gathering Workflow - Mktg Stories

Xnip2026-06-19_11-00-59.jpg

Marketing STORY Process [ Full Canva Presentation]

ALL Slides in PDF format - see attachments section

Creative

Creative & Content Content Development Team - Workflows

View diagrams in Canva Presentation. 

PDF - all workflows in attachments section.

Included workflows:

Creative

Creating Folders & Naming Google Docs (GBMS Writers)

See attached PDF and linked file for GBMS Writers folder naming convention.

Creative/Branding

Creative/PrintShop

Web Experience

Web Experience

Best Practices for File Names and URLs

Further reading:
https://www.woorank.com/en/blog/underscores-in-urls-why-are-they-not-recommended



Web Experience

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.

Web Experience

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:

Web Experience

Google Doc or PDF?

This is the current best practice:

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):

Key reasons why a Google Docs link might not be good on a website: [2, 3, 4]

Better alternatives to using a direct Google Docs link on a website: [2, 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




Web Experience

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.

Landing Page Process Phases.jpg

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

  1. 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.
  2. 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.

  3. 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?
  4. Accept/Reject - Based on what is uncovered in the discovery the team will decide if they can/should continue
  5. 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

  1. 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.
  2. Deliverables - The designers (Web team) will present wireframe (this not a finished design) to Stakeholders for approval and feedback.
  3. 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.
  4. 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

  1. 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.
  2. Functionality - UX (Web team) to collaborate with web developer to communicate desired functionality, aesthetics and expectations of finalized landing page
  3. Development - Web developer will proceed on building out the landing page on a staging site
  4. 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)
  5. 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

5: Updates (Post Launch)

Web Experience

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)?

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:

  1. Influencers (usually with veto power)?

  2. Finances for development, design, marketing, etc.?

  3. Who creates content, form, function, analytics?

  4. Who approves and then signs off on Scope of Project?

  5. Who implements/provides data model, wireframe, etc.?

  6. GBMS team who will develop or approve design, text copy, image assets, etc.

  7. Who leads the delivery of a viable product or service?

  8. Who will manage content, assets, adds, deletes, updating?

  9. Who will market/promote?

  10. Ongoing support or SLA (adding users, onboarding, etc.)? 

  11. 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):

More details may be needed:

Basic UX:

  1. Strategy - User needs, business goals

  2. Scope - Requirements, specifications

  3. Structure - Information Architecture

  4. Skeleton - Navigation and layout (wireframing)

  5. Surface - Visual UI design & coding

When building an inquiry/comment form:
Other:

https://form.asana.com/?k=OeMUzqgwHGrIKlTE5Zz8Eg&d=657768513276

Web Experience

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:

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 <img> 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. 

Web Experience

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:

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 Experience

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

Discovery questions

  1. What team or ministry area do you represent?

  2. What is your role in this initiative or request?

  3. What responsibility does your team have for the website, if any?

  4. Who else should be involved in this conversation?

  5. Who is the final decision-maker for this request?

  6. Which departments, regions, or language teams are affected?

  7. Is this request driven by a specific campaign, strategic initiative, ministry need, or operational issue?

  8. 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

  1. What ministry objective is driving this request?

  2. What organizational or team goal does this support?

  3. Why is this important now?

  4. What problem are you trying to solve, or what opportunity are you trying to capture?

  5. How does this request support the mission of JFP?

  6. How does this request serve evangelism, ministry partnership, resource distribution, or disciple-making?

  7. What outcome would make this request successful from your team’s perspective?

  8. Is this tied to a larger strategic initiative, annual objective, or leadership priority?

  9. What would happen if this request is delayed or not implemented?

  10. 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

Discovery questions

  1. Who is the primary audience for this request?

  2. Is the audience external, internal, or both?

  3. What type of ministry leader, partner, or user are you trying to reach?

  4. What does this audience need most from the website?

  5. What are they trying to do, learn, find, or accomplish?

  6. What are their likely pain points, frustrations, or barriers?

  7. What questions do they typically have before taking action?

  8. What level of awareness or familiarity do they already have with JFP?

  9. Are there audience differences by region, language, ministry maturity, or church context?

  10. 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

  1. What is not working well on the website today?

  2. Where are users getting stuck, confused, or dropping off?

  3. What complaints, feedback, or recurring questions do you hear from users or internal teams?

  4. Are there gaps in content, functionality, navigation, or messaging?

  5. Are there parts of the site that feel outdated, unclear, hard to use, or misaligned?

  6. What internal processes make it difficult to support this area of the website?

  7. What workarounds are teams currently using?

  8. What is the biggest pain point you would fix first?

  9. Are these issues affecting one audience, multiple audiences, or global users broadly?

  10. 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

  1. What content is needed to support this request?

  2. What existing content already exists, and what is missing?

  3. Does the current messaging clearly explain the value of this ministry, resource, tool, or initiative?

  4. What does the audience most need to understand, trust, or believe before taking action?

  5. What specific pages, content types, or assets are needed?

  6. Are there key calls to action that need to be strengthened or clarified?

  7. Does the content need to serve different audience segments differently?

  8. Are there theological, ministry, or brand considerations that need to shape the messaging?

  9. Who owns the content strategy, writing, review, translation, and updates?

  10. What content should remain evergreen, and what content will require regular maintenance?

  11. Are there stories, case studies, testimonies, or field examples that should support this content?

  12. 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

  1. Which languages are needed for this request?

  2. Is direct translation sufficient, or does content need cultural adaptation?

  3. Are there region-specific user needs, examples, offers, or calls to action?

  4. Which markets or countries are most important for this initiative?

  5. Are there languages that should be prioritized first?

  6. What is the translation and localization workflow today?

  7. Who reviews translations for quality, clarity, and theological accuracy?

  8. Are there known challenges with multilingual publishing, governance, or maintenance?

  9. Will all features and content be available in all languages?

  10. How should the site handle language selection, fallback content, and untranslated pages?

  11. Are there localization considerations related to imagery, examples, ministries, testimonies, or terminology?

  12. 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

  1. What does the user need to be able to do on the website?

  2. What feature or capability is needed to support that action?

  3. Is this a new feature, improvement to an existing feature, or replacement of a current process?

  4. What specific functionality is required?

  5. Are forms, downloads, search, filtering, account features, integrations, or content personalization involved?

  6. Does this request require different functionality by audience, language, or region?

  7. Are there required user journeys or business rules?

  8. What systems, teams, or workflows would this feature affect?

  9. What does a minimum viable version look like?

  10. What is essential on day one, and what could be phased later?

  11. Are there accessibility, security, privacy, or compliance considerations?

  12. 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

  1. What is the ideal user journey for this audience?

  2. What are the key entry points into this experience?

  3. What action should users take next after landing on the page?

  4. Where do users need more clarity, reassurance, or direction?

  5. What steps in the journey feel too complicated, long, or unclear?

  6. What information does the user need first, second, and third?

  7. What questions or objections should the page or experience answer?

  8. Are there important journey differences by device, language, or geography?

  9. Should the experience drive exploration, conversion, engagement, or relationship-building?

  10. What would a better user experience look like in practical terms?

  11. Are there known navigation issues affecting this journey?

  12. 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

  1. Are there technical constraints we need to know about?

  2. Does the current platform support this request?

  3. Are integrations required with CRM, analytics, DAM, translation systems, forms, email, or partner tools?

  4. Does this request affect performance, security, scalability, or maintainability?

  5. Are there known issues with the current CMS, templates, or publishing workflows?

  6. Does the request require custom development, third-party tools, or vendor support?

  7. Are there mobile, browser, or device-specific considerations?

  8. Are there accessibility standards this solution must meet?

  9. Is there existing technical debt that could affect this request?

  10. What internal technical resources are required to support this?

  11. Are there data privacy, consent, or regional compliance issues to consider?

  12. 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

  1. How should users find this content or experience?

  2. Is organic search an important traffic source for this initiative?

  3. What search intent is this content or feature meant to serve?

  4. Are there important keywords, topics, or questions this should address?

  5. How should internal site search support this experience?

  6. What analytics are currently available for this area?

  7. What data do you already have about user behavior, performance, or demand?

  8. What metrics would indicate success?

  9. Are conversions clearly defined?

  10. Do we need event tracking, funnel tracking, scroll tracking, form tracking, or campaign attribution?

  11. Are there SEO risks such as duplication, localization complexity, or weak information architecture?

  12. 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

  1. Who owns this initiative from a business or ministry perspective?

  2. Who owns the content once it is published?

  3. Who approves strategy, content, design, theology, and technical implementation?

  4. What teams need to review or sign off?

  5. What is the current workflow for creating, reviewing, translating, and publishing content?

  6. Where do delays usually happen?

  7. Who is responsible for ongoing maintenance and updates?

  8. How often will this need to be reviewed or refreshed?

  9. Are there governance policies or standards that apply?

  10. Is there confusion today around roles, approvals, or decision rights?

  11. What would make the workflow more efficient and sustainable?

  12. 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

  1. What risks do you see with this request?

  2. What could prevent this from succeeding?

  3. Are there budget, staffing, timing, or technology constraints?

  4. Does this depend on other teams, systems, approvals, or external partners?

  5. Are there unresolved strategic questions that need leadership input?

  6. Are there theological, brand, legal, or cultural sensitivities involved?

  7. Is this request dependent on translation, content creation, or technical infrastructure not yet in place?

  8. What assumptions are we making that may not be true?

  9. What could cause delays after the work begins?

  10. What previous lessons or failed attempts should inform this effort?

  11. What is the greatest implementation risk?

  12. 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

  1. How important is this request relative to other ministry and website priorities?

  2. Is this urgent, important, or exploratory?

  3. What is driving the timeline?

  4. Is there a deadline, event, campaign, launch, or external dependency?

  5. What is the cost of not doing this?

  6. What is the expected impact if this is implemented?

  7. Is the request clearly defined enough to move forward?

  8. What information is still missing before this can be scoped?

  9. Is content ready, or still being developed?

  10. Are stakeholders aligned on the need and desired outcome?

  11. Could this be delivered in phases?

  12. Is this a must-have, should-have, could-have, or not-now item?

Priority assessment

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

Summary questions

  1. What is the core need behind this request?

  2. What problem are we solving for the audience and the ministry?

  3. What requirements are clearly defined?

  4. What needs more validation, research, or alignment?

  5. What should happen next?

  6. Who needs to make a decision?

  7. What should be prioritized now, later, or not at all?

  8. What recommendation best balances ministry impact, user value, and operational feasibility?

WordPress

Info, Tips and Helps for using WordPress, including Gutenberg.

WordPress

Featured Image

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:

How to use Featured Images in Gutenberg:

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

WordPress

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

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/

WordPress

Copy a Block

How do I copy a Block from another page?

WordPress

Bulleted List line-height

Is there any way to reduce the line-height of a bulleted list?

Example: jesusfilm.org/unpacking-parables

WordPress

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?

WordPress

JFP Brand shape for image

How do I get my image on a page to have the JFP Brand shape?

Example: jesusfilm.org/resources/pray/2025-06-country

WordPress

Make a page not searchable

How do I make a page so it’s not searchable when someone does a Google search?

WordPress

Schedule update to existing page

Can I schedule an update to an existing webpage?

RACI Matrix

What is RACI?

In business and project management, a responsibility assignment matrix (RAM), also known as RACI matrix:

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.

What-is-a-RACI-Matrix_2.webp

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