PUBLIC · CEVHER DOGAN
A Human“Kind” Earthling · public workbench · never-same learning cycle

An endless river of public experiments.

Not a repository dump. A living, searchable map of things built, explored, forked, learned, shared, connected and still becoming.

Project Atlas

Search by meaning, not just name.

Original work and learning forks are deliberately distinguished. Public availability is provenance; it is not a claim of authorship over upstream projects.
Discovery funnel

Discover → Understand → Try → Collaborate → Extend → Stay

01 Discover

Search the public atlas.

02 Understand

Read context and provenance.

03 Try

Open code, demos or patterns.

04 Collaborate

Bring a problem or idea.

05 Extend

Adapt into a governed system.

06 Stay

Follow releases and new work.

Access architecture

Public first. Deeper paths when useful.

The public atlas remains open. Membership is designed for saved collections, release alerts, collaboration workspaces and implementation—not to hide public-source work behind a paywall.

PUBLIC
$0

Browse, search, filter, open GitHub and share public project links.

MEMBER
Configurable

Account, saved collections, release digest and deeper project notes. Stripe/Auth ready; price stays environment-controlled.

COLLABORATOR
Scoped

Private workspace, intake, source permissions, project framing and implementation collaboration.

Start a conversation
SPONSOR
Custom

Support public-interest work, themed collections or governed open-source initiatives.

Explore sponsorship
Connect

Bring a project, a question, or a useful disagreement.

This site is designed as a front door to public work—not a replacement for GitHub. Collaboration can begin with context, then move toward the right project, service or shared experiment.

Static-safe fallback: opens your email client. A server endpoint can replace this without changing the form contract.

Member flow preview

Identity belongs on the server.

This prototype intentionally does not pretend localStorage is secure authentication. Production hooks are reserved for a server-side auth provider + Stripe customer/subscription mapping.

Expected production states: visitor → verified user → member → collaborator/sponsor entitlement → cancellation/grace period → public fallback.