Project Overview

OZEAON is the web application behind the OZEAON ocean conservation platform. Organisations, projects and individuals publish and discuss conservation work in one place. It is a single Next.js App Router app running on Cloudflare Workers, with Supabase for data and auth, and Cloudflare R2 for files.

Features

• Accounts: sign up, sign in, email verification, password reset, profile settings, switching between a personal account and an organisation account, and account deletion. See Auth Flows and Account Switching & Active Account.
• Organisations: public profiles, members and roles, invitations and join requests, and organisation deletion. See Organisation Profiles, Membership & Roles.
• Projects: multi-section project pages, drafts and publishing, My Projects, and deletion. See Project Lifecycle & Discovery.
• Articles: a Tiptap-based editor, publishing, My Articles and a reader view. See Article Authoring & Publishing and Article Reader Experience.
• Posts: a community feed with image attachments and reposts. See Posts.
• Comments on posts, projects and articles, and likes on posts and comments. See Comments & Reactions.
• Search: name and title search across organisations, projects, articles and people. See Search & Discovery.
• Automated moderation: content is checked with the OpenAI moderation API before it publishes. See Content Moderation Pipeline.
• Founding-member (alpha) badges for users and organisations created before the alpha cutoff. See Founding Member Badges.
• UN SDG tagging on projects and articles.

In progress: notifications (behind the NEXT_PUBLIC_FEATURE_NOTIFICATIONS flag), legal pages, and in-feed filters on the article and project feeds.

Roadmap

Planned work includes:

• pods and DAO governance
• a token reward system
• project funding, donations and tipping
• an educational resources hub with quizzes
• events
• messaging
• notes and bookmarks
• connections and blocking
• search across every content type

The database schema already contains tables for several of these, such as pods, dao_proposals, token_transactions, educational_resources, events, bookmark_folders and open_calls. These tables have no application features behind them yet. A few API routes also exist with no UI calling them: /api/connections, /api/blocks and /api/events. Data Model & Database Schema lists the placeholder tables.

Architecture

flowchart TD
    Browser["Web browser"]

    subgraph sg_App["Next.js App Router on Cloudflare Workers"]
        Pages["Server Components<br/>public and signed-in pages"]
        Actions["Server Actions"]
        Api["API routes"]
    end

    subgraph sg_Lib["Platform libraries"]
        Clients["lib/supabase<br/>server, browser, admin, public clients"]
        Storage["lib/storage<br/>StorageAdapter"]
    end

    Supabase[("Supabase Postgres<br/>RLS, triggers, auth")]
    R2[("Cloudflare R2")]

    Browser --> Pages
    Browser --> Api
    Pages --> Actions
    Pages --> Clients
    Actions --> Clients
    Api --> Clients
    Actions --> Storage
    Api --> Storage
    Clients --> Supabase
    Storage --> R2

The decisions that shape the codebase:

• The Supabase client decides how a route renders. Public pages that use only createPublicClient() prerender statically. Anything that calls await createClient() reads cookies and renders dynamically. Rendering is never set with dynamic/revalidate exports. See SSR, Rendering & Caching and Supabase Client Patterns.
• Postgres does the deterministic work. Row-Level Security handles authorization, and triggers maintain counters, audit timestamps and cascades. See Data Model & Database Schema.
• Types are derived from the generated Supabase types. See Type System & Generated Types.
• All file access goes through StorageAdapter, not the raw R2 binding. See Storage Abstraction & R2 Integration.
• It deploys to Cloudflare Workers through OpenNext. Every PR gets its own preview Worker and Supabase branch. See Cloudflare Deployment and CI/CD Workflows.

Where to Go Next

• Getting Started & Local Setup: run the app locally.
• Technology Stack & Scripts: the libraries in use and the pnpm scripts.
• Coding Conventions & Linting Rules: the rules contributors follow.
• Adding a New Feature End-to-End: a worked path through the layers.

Related Links

• README.md: product vision and live environments.
• CLAUDE.md: engineering conventions and commands.
• docs/: in-repo deep dives on deployment, R2, the component library and the design system.
• Live: ozeaon.com (landing), app.ozeaon.com (production), app.ozeaon.dev (staging).