Writing a community case study
This page is for advocates who want to tell the story of a site built with Exponential: their own, a client's, a nonprofit's, a school's. A case study is the most convincing material there is, and the easiest to get wrong. The full eight-step process is on Writing case studies and content marketing; this page adapts it for volunteers.
Contents
- The three non-negotiables
- Whose story can you tell?
- Interview guide
- The template
- Checking and approval
- Where to publish
The three non-negotiables
- Consent before writing. The organization agrees in writing that you may write about it, before you start (Step 2: ask for consent).
- Every fact checked. Numbers come from the organization, with their permission to publish them.
- Written approval of the final text (Step 6).
No exceptions. A story published without consent can harm the organization, you and the project.
Whose story can you tell?
| Story | Consent needed from |
|---|---|
| Your own personal site | Nobody, but keep other people's data out |
| Your employer's site | Your employer (and your contract may require it) |
| A client's site | The client, in writing |
| A friend's or volunteer project | The project's responsible person |
| "A site I saw" | Do not; write to them first |
People named or quoted need their own consent. Never publish names of staff, users or customers without it (Protecting people's privacy).
Interview guide
CONTEXT
1. What does your organization do? What did the site need to do?
2. What did you use before, and why did you change? (No criticism of other products in the published text.)
CHOICE
3. Why Exponential? Which features mattered? (Map them to sources later.)
4. What worried you, and how was it resolved?
BUILD
5. Who built it, how long did it take, which extensions?
6. What was hard? What would you do differently?
RESULT
7. What changed for editors, visitors, administrators?
8. Which numbers may we publish? (Only theirs, with permission.)
COMMUNITY
9. Did you contribute anything back (fixes, translations, docs)?
10. What would you tell someone choosing a CMS today?The template
# <Organization> <does what> with Exponential
<One-paragraph summary: who, what, result.>
## The challenge
<Their words, approved.>
## Why Exponential
<Features with links to the help pages that describe them.>
## How it was built
<Team, time, extensions, what was hard. Credit people and companies who agreed to be named.>
## Results
<Only approved facts and numbers, with "according to <organization>".>
## Giving back
<Contributions, if any.>
Approved by <organization> on <date>. Written by <you>; <disclosure of your relation>.Checking and approval
- To do: Every feature mentioned links to its help or feature page (Where the facts live).
- To do: Every number is the organization's, with permission, and attributed to them.
- To do: No other product is criticized (Respecting other projects and companies).
- To do: Names are right (Naming rules quick card).
- To do: No personal data, secrets or internal details.
- To do: The final text is approved in writing; keep the approval.
- To do: Your relation is disclosed (Disclosure and conflicts of interest).
If the organization later asks you to remove the story, remove it promptly (Step 8: maintain and withdraw).
Where to publish
- Your own blog or the organization's site.
- Share (blogs, articles) (Publishing on Share and Projects).
- A forum post linking it.
Related pages
- Writing case studies and content marketing
- Protecting people's privacy
- Writing a blog post
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.