gooism.org

Status update — 2026-05-08

Two days after v0.1 was authored, here's what's actually live + the design decisions that landed.

• DNS migrated — gooism.org nameservers flipped from GoDaddy to Cloudflare. Zone Active, parking IPs cleared, www CNAME in place.
• Pages project deployed — gooism-org Cloudflare Pages live at https://gooism.org and gooism-org.pages.dev.
• HTTPS hardened — Always Use HTTPS on, HSTS enabled (max-age 6 months, includeSubDomains), No-Sniff header on. SSL/TLS mode "Full (strict)".
• Hero approach proposed — prototype went with the animated wordmark/G hero family (was Option A in v0.1). Specifically: pixel-sampled particle G mark with mouse repulsion, fixed to viewport so it stays in place as the page scrolls. What Jack is putting forward for review — open to alternative directions if the collective wants something different. Details in §03 below.
• Color schema proposed — monochrome neon (white-on-black) + cyan #58e1ff as the sole accent for action / focus / interactive feedback. Proposed direction — aligns with brand-report Option C — Mono + Functional Color. This is what we’re prototyping for review with the collective; not yet a collective-locked decision. Details in §03b below.
• Mailing list backend — POST /api/subscribe Pages Function deployed as a v0 stub (validates email, returns success, doesn't yet persist). Resend + D1 wiring is the next concrete task — see §04.
• Pending — Resend domain verification + DNS records, D1 table, Turnstile bot protection, welcome email template. Estimated 2–3 hr of work to flip the form from stub to real.

Everything below this section was authored in v0.1 — the strategy is unchanged, only the hero and color sections have been updated to reflect what shipped instead of options.

Why "small landing" is the right v1

The temptation with a fresh domain is to ship the whole vision. We're not going to.

GPortal — the directory + planner + match engine — already exists at gportal.wallspace.studio. It works. People are using it. It is the incubator. Moving it to gooism.org before the collective has aligned on curation criteria, brand migration, and access policy would import a lot of half-finished decisions onto a brand-new front door.

Instead, gooism.org launches as a single confident landing page + a mailing list. That gives us:

• A canonical home for the new Gooism brand identity (where the monochrome neon system lives at full size, free of WallSpace cyan/pink legacy)
• A signup mechanism so collective announcements have a destination — not just social
• A clean place to point press, partners, and prospective members now, without exposing the in-progress portal
• Time for the collective to settle Q.01–Q.06 from the brand report before anything load-bearing ships

Once those decisions are made and GPortal v0.5 has cut, we run the portal migration as a deliberate, scheduled event — not a default of "well, we own the domain now."

DNS + hosting + HTTPS — done

All the operational plumbing is in place. No collective input was needed for this phase — pure infrastructure.

• Domain — gooism.org nameservers moved from GoDaddy to Cloudflare. Zone Active, parking IPs cleared.
• Hosting — Cloudflare Pages project gooism-org deployed; gooism.org and www.gooism.org both bound to it.
• HTTPS — Always Use HTTPS + HSTS (6-month max-age, includeSubDomains) + No-Sniff header. SSL/TLS mode "Full (strict)". Cert auto-issued.

Technical step-by-step (DNS records, deploy commands, secret management) lives in the gooism-org repo README — not relevant for this review document.

A homepage that does one thing well

Full-viewport hero, the GOOISM wordmark living in its native habitat (perspective grid, neon line, pure black), one short statement, one email signup, one button. Below the fold: a quiet manifesto, the founders, a footer pointing to the incubator. Nothing else for v1.

Visual direction (proposed — was Option A in v0.1, prototyped for review)

Reference target: y.co — full-viewport cinematic quiet. The hero is the page. No nav. No tabs. No scroll-jacking. Just the wordmark, the G mark, signup, and a soft fade as you scroll.

• Centered + optically balanced — particles' centroid (visual mass) sits at viewport center, not the bounding-box center, correcting for the G's open-curve asymmetry.
• Scales to widescreen — G size = max(viewport-width, viewport-height) × 1.0. Full-bleed corner-to-corner on landscape monitors.
• Reduced-motion respect — the canvas is hidden under prefers-reduced-motion: reduce. Below 720px viewport too (mobile gets clean static hero).
• Bandwidth — single PNG (~1.2MB), no video, no library JS. All animation is ~80 lines of vanilla JS inline in the page.

Option B (cinematic VJ-set video loop) was deferred and remains a candidate for v2 if the collective wants more "what we do" forward energy. For v1 the brand mark is the centerpiece.

§ 03b · Color schema (proposed — brand-report Option C, pending collective review)

What's being prototyped: monochrome neon + one functional accent. This is the proposal Jack is putting forward; the collective hasn't formally signed off yet.

• Black #000000 — page surface, always pure black (never charcoal).
• White #ffffff — primary copy, the GOOISM wordmark, the JOIN THE LIST button (primary CTA stays white for highest contrast).
• Grays — #b0b0b0 secondary, #707070 muted, #444444 faint (footer chrome, sublabels, version tags).
• Cyan #58e1ff — the sole action accent. Used for: input focus border, link hovers, success-feedback messages, founder name hovers, footer link hovers. Never used for primary CTAs (those stay white).

Why cyan specifically:

• Continuity story — same cyan as WallSpace's primary. Reading the two brands together: WallSpace = full multicolor (cyan/pink/purple/orange), Gooism = monochrome + cyan. Cyan threads them together as a related family without making them identical.
• Functional, not decorative — pure monochrome is gorgeous in marketing surfaces but operationally cold. One accent gives signal value. Where do I click? Cyan. What's selected? Cyan. Did the form succeed? Cyan.
• Native to the medium — cyan is the color of CRT phosphor at startup, of broadcast test signals, of monitor "glow." Reads as native to the VJ/video world.

This is what Jack proposes — pending collective review. The recommendation aligns with brand-report Option C — Mono + Functional Color. If the collective concurs, future palette decisions (including GPortal migration) default to this hierarchy: white = primary CTA, cyan = interactive, mono everywhere else. Open for discussion in the next sync.

Copy (proposed v1)

[GOOISM wordmark — large, animated]

A collective for VJs and visual artists.

[ email field ]                [ Join the list ]

—

We send maybe one email a month. Open work, recorded
sets, the occasional manifesto. Process is community,
community is process.

—

[ founder strip — 4 small avatars + names ]

—

Incubating at gportal.wallspace.studio →

Tone: spare, confident, technical-poetic. No "supercharge your VJ career." No "the future of." No exclamation points. Treat the reader as smart and busy.

Stack at a glance: Cloudflare Pages (hosting) + minimal HTML/CSS/JS (no framework needed for v1) + Cloudflare Web Analytics (privacy-respecting, no cookie banner) + Cloudflare Turnstile (bot protection on signup). Implementation details in the gooism-org repo README.

How signups will work

Currently the form on gooism.org accepts an email and shows success — but nothing's persisted yet. Wiring the real backend is the last v1 task. ~2-3 hours of work; no collective decision required.

What it does, in plain English

• Visitor types email, hits Join the list.
• Form posts to a small server function (/api/subscribe) running on Cloudflare's edge.
• Function checks it's a real human (Cloudflare Turnstile — invisible bot protection, no captcha images).
• Email gets stored in a small Cloudflare-hosted database we own.
• Email gets added to a mailing-list audience on Resend (the email-sending provider).
• Visitor receives a one-line welcome email confirming they're on the list.
• Every future broadcast we send through Resend includes a working unsubscribe link.

What we collect

• Email address. That's the meaningful data.
• Subscribed timestamp (so we know who's been on the list how long).
• A salted hash of the visitor's IP — used only for rate limiting and fraud prevention; can't be reversed back to an IP.
• Source tag (e.g. gooism.org/hero) so we can tell apart future signup surfaces.

No name, no location, no device fingerprint, no analytics tracking on the form. We own the data — it lives in our Cloudflare D1 database, not in a third-party email provider's silo. Resend has a copy of the email address (because they need it to send) but the relationship is ours.

Why this stack

• Cloudflare Pages + D1 — same infrastructure as wallspace.studio + GPortal. One bill, one dashboard, one mental model. Cost: $0 for v1 traffic.
• Resend — modern email provider, reliable deliverability, clean API, generous free tier (3,000 emails/mo). Better than rolling SMTP ourselves.
• Turnstile — Cloudflare's invisible bot check. No "click all the buses" images. Free.

Welcome email — current draft

This goes out automatically on every new signup. Single-opt-in for v1; we can upgrade to double-opt-in later if needed.

Sent from hello@gooism.org via Resend. Plain-text fallback included. Reply prompt invites the same fields the old Google Form collected (name, location, practice) — reframed as a reply rather than a structured form, which felt more Gooism-shaped.

Inbound replies — needs collective decision

The welcome email's "From" address is hello@gooism.org, so replies route there. Right now hello@gooism.org isn't a real mailbox — replies bounce silently or get routed wherever Resend's catch-all sends them (which currently lands in Jack's gmail because his gmail owns the Resend account).

@gooism.org email addresses — for collective discussion

To handle replies properly + give the collective real name@gooism.org addresses (which we'll want for outreach, booking conversations, press contact, etc.), we need to pick an email provider. Three realistic options:

1. Google Workspace — full Gmail + Drive + Calendar + Meet under @gooism.org. Most familiar, integrates with everyone's existing Google logins.
   • Business Starter: $6/user/month (~$72/user/year). 4 founders = ~$288/year.
   • Business Standard: $12/user/month (~$144/user/year). 4 founders = ~$576/year. Adds Meet recordings + more storage.
   • Recommended tier: Starter. We don't need the heavier features yet.
   • Free for verified non-profits. Google for Nonprofits gives Workspace Business Starter at $0/user/month for verified 501(c)(3) organizations. Once Gooism completes nonprofit setup (see Cece's strategy report linked below), the recurring cost goes to zero — making Workspace the obvious long-term answer.
2. Cloudflare Email Routing (free) — inbound only. Forwards hello@gooism.org, jack@, fetz@, etc. to existing personal addresses. Works today, costs $0. Limitation: outbound email from @gooism.org needs a separate solution (Resend already covers transactional like welcome emails; replies and outreach would still come from personal addresses).
3. Zoho Mail / Fastmail / Proton — middle ground. Zoho has a free tier for up to 5 users on a custom domain; Fastmail and Proton are paid (~$3-5/user/month). Less familiar than Gmail, owned by smaller companies — pros and cons either way.

Open questions for the collective:

• Which provider? Recommendation: Google Workspace Starter. Familiar, reliable, integrates with what everyone already uses. ~$288/year now → $0/year once we're a verified non-profit.
• Who covers the cost in the meantime? Options: split evenly across founders (~$72/founder/year), Neem LLC covers it as Gooism overhead, treated as collective dues, or we sponsor one founder's seat at a time as people opt in. Bridge cost only — drops to zero once nonprofit status lands.
• Which addresses to provision? Likely: hello@ (shared/forwarding inbox for general inquiries), one address per active founder (jack@, fetz@, kevin@, andrew@), and maybe bookings@ as a future shared inbox.
• Reply distribution for hello@: forward to all founders by default? Round-robin? One designated point person rotating monthly? Anything but routing every reply to Jack alone.

Implementation reference (database schema, Pages Function code, step-by-step Resend domain verification, etc.) lives in the gooism-org repo README under "Phase 1.5 wire-up." Not included here — this doc is for review, not engineering.

"Gooism Recommended" subset

Once v1 is live and the collective is set on inclusion criteria, gooism.org grows a curated wing. This is the focused initial product the collective discussed.

What it is

A curated subset of the GPortal VJ directory. Not everyone in GPortal — only those the collective has formally recommended. Page lives at gooism.org/vjs (or gooism.org/recommended). Each profile is a thoughtful, full-page treatment, not a card-grid entry. Quality over quantity.

Inclusion criteria (proposed — collective decides)

• Has an active GPortal profile with all required fields filled
• Has at least one published Signal Plan in the planner
• Has performed at a Gooism-listed venue at least once (verified)
• Has been recommended by ≥2 founders (or ≥1 founder + 2 existing recommended members)
• Reviewed and approved in a quarterly curation pass

Curation workflow

Lightweight in v1 of this phase: a private Notion or Linear board + a quarterly sync. Heavier later: a curation queue inside GPortal itself, with vote/approval state, exported to gooism.org. The MVP doesn't need software for this — humans + a spreadsheet works for the first 20 members.

Tech

Curated profiles are served from gooism.org but read from the same GPortal D1 (cross-domain via the Cloudflare bindings or via a public read-only API). The "recommended" boolean lives on the GPortal profile and is set by an admin. gooism.org filters to recommended = true.

Brand: full Gooism monochrome system. No shared chrome with GPortal product UI — these are marketing profiles, not operational profiles.

Move GPortal to gooism.org

After: brand decisions made, curated wing live, GPortal v0.5+ shipped, collective consensus that the time is right.

What changes

• Primary URL moves: gportal.wallspace.studio → gooism.org/portal or portal.gooism.org
• Old subdomain becomes a permanent 301 redirect for ~6 months, then sunsets
• GPortal palette migrates per brand report §06 (Option A / B / C)
• Auth: cross-subdomain cookie strategy extends to .gooism.org (currently .wallspace.studio only)
• WallSpace.Studio's relationship to GPortal becomes formalized — wallspace.studio retains a separate role (Neem product surface, recorded experiences, beta-guide, scope docs)

What does NOT change

• The codebase. Same Next.js + OpenNext + xyflow stack. No rewrite.
• The data. Same D1 databases (GPORTAL_DB, AUTH_DB, MEDIA_BUCKET).
• Existing accounts and content. Members keep their profiles, packages, signal plans.

Sequence (when the time comes)

1. Add gooism.org/portal as a Cloudflare Worker route → existing OpenNext deployment
2. Update GPortal's auth cookie domain from .wallspace.studio to .gooism.org (members re-authenticate once)
3. Push a redirect from gportal.wallspace.studio/* → gooism.org/portal/* (301)
4. Update outbound links in all comms, docs, social bios
5. After 6 months of stable redirect traffic, sunset the wallspace subdomain

What's resolved, what's still open

v0.1 listed risks looking forward. v0.2 marks which ones landed clean and which are still active.

Resolved since v0.1

Still open

v1 progress — what's shipped, what's left

Status update against the v0.1 effort table. Most of v1 is done; what remains is the real email capture path.

Where we are, what's left

Original plan: get DNS done first, then ship Phase 1 after brand sign-off. Reality: Phase 0 + most of Phase 1 ran in parallel and are live for review. Final wiring and collective input remain.

1. ✓ Phase 0 — DNS migration: complete. gooism.org nameservers active on Cloudflare. HTTPS hardened. No collective input was needed for this — pure infrastructure.
2. ✓ Phase 1a — site + brand prototype: live for review. gooism.org serves the particle G hero, signup form (stub), manifesto, founders, and footer. Same particle engine and cyan accents are now applied to this launch plan and the brand report — so the collective can see the proposed system in three places before signing off.
3. ○ Pending — collective review on the brand-report's Q.01–Q.06. Particularly Q.02 (migration option). The prototype implements Jack's proposed direction (Option C); the collective hasn't formally weighed in yet. Read the brand report, react in the next sync, push back or concur. Outcome shapes whether any redo is needed (small if so — most cyan is in CSS vars).
4. ○ Pending — Phase 1b: Resend wiring. Real email capture needs ~2–3 hours: Jack signs up at resend.com + verifies gooism.org as sender domain, Claude adds the DNS records to Cloudflare, replaces the v0 stub in functions/api/subscribe.ts with real persistence (D1 + Resend audiences + welcome email), and adds Cloudflare Turnstile to the form for bot protection. No collective input needed — operational.
5. ◦ Phase 2 — curated VJ wing: still paper. Blocked on the collective agreeing on inclusion criteria for "Gooism Recommended" VJs. Doesn't gate v1 — gooism.org keeps running as landing-only until criteria + curation workflow exist.
6. ◦ Phase 3 — full GPortal migration to gooism.org: still paper. Blocked on Phase 2 being live and the collective deciding GPortal's brand direction (depends on Q.02 outcome).

Bottom line: the v1 surface (gooism.org) is live for review, infrastructure is complete, and the only remaining v1 work is wiring the email backend. Phase 2 + 3 wait on collective decisions, not on infrastructure.