CGCS
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    1
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- title: Spiritual Vitality article (NEEDS TITLE) author: Keelan date: 2022.10.28 tags: Keelan, spiritual formation, missions --- When I lived in Africa, I had to draw water from a well. During my time serving overseas as a missionary, I lived in a rural part of West Africa. Rustic doesn't quite describe the living conditions. There was no electricity or running water, and that meant water had to come out of the ground, and it had to do so by hand. When I was in Africa, I used this analogy often. The daily trip to the well is, in many ways, not too different from our spiritual vitality as believers and as churches. On the equator, it gets hot and that water from the well is refreshing. It's more than refreshing; it's essential; it's life-giving. Without water a village cannot exist. The daily trip to the well was a nonnegotiable part of life. The water was, in many ways, the source of vitality in the village. What is more, without a bucket, a person had little chance of gaining access to the water. Wells are deep. My first experiences with drawing water were laughable. You would think it's a cinch, but you would be wrong. I can remember my first trip to the well, bucket in hand. I was the new guy in the village and everyone knew it, so anyone nearby stopped for some entertainment. I'm sure they knew what was about to happen. I walked over to the well, peered down inside, and pitched my bucket into the dark water at the bottom. It hit with a splash, and that's when I discovered an important truth. Here's the dirty little secret: buckets float. You drop a bucket down in a well, and unless you do it right, it just sits on top of the water. Even if the bucket is made out of metal, it still doesn't settle into the water in a way where you can pull it back up full. You must use the right technique. It took someone showing me how to use the tool correctly for me to benefit from it. After multiple failed attempts, one of my neighbors sent over their little girl to instruct me in drawing water. Let that sink in. Here I was the confident adult Westerner being tutored by a seven-year-old in how to do something everyone in the village knew how to do by the time they were three. Of course, it's easy to see how this analogy compares to our spiritual vitality. The life-giving water is Christ, and that bucket becomes our means of access, the tool used to drink of that life-giving water. For the individual, this may be their routines of spiritual discipline, their prayer life and time spent in the Word of God. David Mathis refers to these as habits of grace in his book by that name. The habits or disciplines become the means through which grace is administered and applied to the Christian life. However, this analogy can extend past the individual believer to a whole gospel community, or local church. For the church, these may be programs, systems, and resources used to facilitate the spiritual vitality of the congregation. Corporate worship services, music, preaching, small groups, and curriculum are all buckets used to facilitate that vital relationship between Christ and his church. ## Don't praise the bucket instead of the water. In all my time in Africa, I never once heard someone praise their bucket as though it was the thing that gives them life.This statement is obvious when we're talking about buckets and water, but often not so when we're talking about spiritual vitality. Too often, we're guilty of praising the bucket instead of the water. Simply put, programs don't fix a church's spiritual vitality problem. We must remember that life, spiritual vitality, comes from the source of living water. In John's gospel, Jesus tells us that he came that we may have life, and have it abundantly (John 10:10). He continues a few chapters later by telling his disciples that he is the True Vine and that they are merely branches (John 15:5). The analogy is clear, the vine gives life to the branches so that they may produce fruit. Endless means can be poured into designing the perfect system, perfect service, perfect outreach program, perfect curriculum and it will not refresh the soul. Only Christ himself refreshes the soul. Only Christ satisfies, brings life, and brings passion and drive to the mission of the church. Christ is the water, and the program or process is just the bucket. ## But don't neglect your bucket. However, without a bucket, you can't access the water. I often hear well-meaning exclamations today that the church doesn't need any programs, processes, or procedures. While I understand the heart behind such statements, it is an overreaction to say we do not need any of these things. In fact, it's actually impossible for a group of believers to stay organized as a church without some form of structures and systems in place. If you choose to meet at the same time for worship and fellowship each week, then you have already created a program. We shouldn't lament this reality, as long as we understand the difference between the water and the bucket. In *The Trellis and the Vine*, Collin Marshall and Tony Payne pick up this metaphor in a way that is profoundly helpful for conversations about church ministry. Throughout Scripture, the church is described in organic terms. In this way, Marshall and Payne claim the church is like a vine. It grows and thrives based on the things that nourish life. However, for vines to grow well, they need structures to support them. This is why vine dressers build a trellis for their vines. You want your church to worship together, but that requires (among other things) having a place and time that you all agree upon to meet. You hope that your church members can grow in their understanding of Scripture together, but that requires some structure and guidance in study and facilitation of the conversations where members can do this. You hope that your church would multiply by sending members to be missionaries or church planters, but that requires processes that identify called members who can be equipped and sent. For a vine to grow to its healthiest potential, it needs a support structure, a trellis. Faithful local church ministry requires us to understand this difference. The real trick is not confusing the priority and purpose of the trellis and the vine, or in my analogy the water and the bucket. The church is a vine not a trellis, but it needs structure and tools to support it's life and growth. In the same way, Christ is our source of life, he is our water. These programs and processes are just the bucket. They are our means of accessing that water. If we understand this distinction, then we will praise the right thing and will have a means of measuring the effectiveness of our programs and tools. A bucket is not successful in itself but only when it brings us the water we seek to live from. In fact, a plastic bucket draws as much water as one made out of gold. When we confuse the bucket and the water, we become guilty of being that church that says, "look how nice our bucket is," instead of the church that says, "drink this and you will never thirst again."

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully