Writing karaha.org's roadmap with a five-year horizon
2026-05-08 ／ Vol. 4 ／ draft at time of publishing
It's been about a day since Vol. 3, "Auditing 3 sites and clearing 24 items in a single day", went up.
That day I wrote, "everything except the Astro migration is done." But there was actually more to do.
Of the three sites, today became a day to focus on karaha.org (Toujisha kara hajimeyou) and tighten things up one more layer.
I did both the publishable "site polishing" and the not-publishable "operational groundwork." This article is just the former.
Becoming the side that gets searched by brand name — "karaha", "Yorimichi Cafe Kawasaki", "Mizonokuchi"
karaha.org is the official site of "Toujisha kara hajimeyou."
Among core members, however, it's long been called by short forms — "karaha" / "カラハ".
The flagship program is "Yorimichi Cafe Kawasaki"; the operations name is "Yorimichi Guild".
One organization. Four names.
By Vol. 3, brand-name search for "Toujisha kara hajimeyou" was covered. But the other three were holes. For example, when you searched "カラハ", the body text contained the standalone word 0 times. It wasn't in the JSON-LD alternateName field either.
I worked through them in order:
・Expanded JSON-LD alternateName to ["からは", "カラハ", "よりみちギルド", "よりみちカフェ川崎"]
・Embedded "(also: からは / カラハ)" into meta description and og:description
・Added a subtext directly below the home page h1: "also: からは／カラハ ／ run by: Yorimichi Guild ／ monthly: Yorimichi Cafe Kawasaki"
・Added a "Names, and what we run" section to the about page
Now even short nicknames like "カラハ" reach Google as "alternative names for the same organization."
"This place is inside Marui" — being explicit about the activity location
Alongside brand names, I want to be findable by region too.
"Kawasaki community group", "Kawasaki peer support", "Mizonokuchi safe space" — when someone searches around there, I want karaha.org to show up.
But looking back at the site, the location info was scattered. "Kanagawa Prefecture, Kawasaki City" was written, but the next layer down — "Takatsu Civic Hall", "Marui / Nocty 2 11F" — wasn't visible.
I added a simple block to the home Contact section:
📍 Main activity location Takatsu Civic Hall (Marui / Nocty 2, 11F) 〒213-0001 1-4-1 Mizoguchi, Takatsu-ku, Kawasaki, Kanagawa Right by Tokyu Mizonokuchi station / JR Musashi-Mizonokuchi station
I also scattered the three Japanese spellings of the place name — "溝の口", "溝ノ口", "溝口" — across the site.
JR uses 武蔵溝ノ口, Tokyu uses 溝の口, the town name is 溝口. I align with the natural variations to catch search queries.
Adding structured data so Google knows "this is an Event"
From here it gets a bit more technical.
karaha.org's event pages (each Yorimichi Cafe Kawasaki) had meta tags and og:image, but didn't explicitly mark "this is an Event, on this date, at this venue" with structured data (schema.org's Event).
Written in JSON-LD, Google can show rich card results. Things like "May 27 2026, 14:00–" with date, venue, and fee in the search snippet.
I added Event JSON-LD to all 9 event pages. In the same flow, FAQPage on the events hub, and BreadcrumbList on each subpage (21 pages total).
I also added geo coordinates (GeoCoordinates: 35.6005, 139.6112) so it's easier to surface in map and nearby searches.
Now Google receives the structured signal "karaha.org's events are at Takatsu Civic Hall in Mizoguchi, Takatsu-ku, Kawasaki, monthly at this date and time."
Suddenly remembered the faces of the core members
In the afternoon, I noticed something.
karaha.org has core members. From the start, peer staff, mental health welfare workers, care welfare workers, an EC operator — different roles, all working together.
"Sustainable operation" — there's a limit to what I can think through alone. To build a structure that lasts, I need to share direction with the team.
And there it switched. The context that had been "site polishing" flipped to "operational groundwork".
Writing "where do we want to be in 5 years" with Claude
I threw this at Claude:
I want to maximize what karaha.org can do, with sustainable operations as the base, and incorporation as the eventual form. Please write a comprehensive roadmap.
Claude came back with a 5-year strategy document.
・Where we want to go (vision)
・Where we are now (current state)
・Phased breakdown
・Grants and subsidies usable per phase
・Milestones for organizational structure
・Foreseeable risks and countermeasures
・Six-month review checkpoints
The fragmented intentions I held — "I want to incorporate eventually," "I want to expand what we can do with grants" — turned into a structured document for the first time.
The act of writing it down was itself important. The moment you write, "what's missing" and "what's at hand" both become visible.
The piece I'm currently missing is the team — putting into words, with all core members, what we need to keep going.
The roadmap content itself hasn't been shared with members yet. So I won't write the details here either. The "process of becoming decided" gets written after it's decided.
Even as a voluntary group, there's a lot you can do
Realization while writing the roadmap: even when "NPO incorporation" looks like the goal, before getting there, there's quite a lot you can do as a voluntary group.
For instance, Kawasaki has public grant programs for citizen activity groups. Voluntary groups can apply too, and while the scale is small, it's enough as "a first step." Building a record of receiving grants opens the next stage.
Some private foundations also accept voluntary groups.
NPO incorporation is significant for tax and credibility reasons. But it's not "set up an entity, all problems solved" — it's "incorporation gains meaning because we've built up to here."
The order matters.
The line between what can be made public and what can't
Writing the roadmap, I noticed something again.
Even on rooo.pro — which I started by deciding to "publish the process itself" build-in-public — the operational details of karaha.org (individual stories of core members, financial figures, the path of internal decisions) are published in a different place.
For a community handling sensitive information, that information itself is the foundation of trust members and participants give.
The line in karaha.org's privacy policy — "Sensitive information such as life stories, history, or diagnoses obtained via inquiries will not be diverted to other uses without consent" — applies to me, the operator, too.
"Site polishing" and "operational groundwork" can happen on the same day. But when writing about them, separate them.
That's why this article only covers "site polishing."
Continuing a "non-business group" with AI
I've used Claude as a partner: esynet.jp as the corporate site, rooo.pro as the personal medium.
karaha.org is different from those two. It made me consciously aware of Claude as a tool for community operations, not for a business.
For a business, "revenue", "KPI", "customers" are clear indicators.
A community group is different. "Participant experience", "accumulated trust", "the fact of continuing" become indicators. They're hard to measure with numbers.
When I asked Claude for the roadmap, Claude properly drew the line: "this is the user's call," "this needs team agreement."
I think this is the most important piece of using AI for non-business groups.
It's not "without numbers, you can't trust AI" — it's "precisely because numbers aren't there, AI makes the territory humans should decide explicit." That's reassuring.
What's next
The site polishing for karaha.org is settled here.
What follows is outside the site — time spent talking with the core members.
In parallel, more rooo.pro work is coming up (Astro migration, tags, how to show diff between past versions).
Vol. 5 will be written when something moves after sharing the roadmap with the members.
Probably around a month from now.