Skip to content

Latest commit

 

History

3 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Oikolab

Note: this repo holds designs, docs, and issue tracking — the implementation lives in the private multi-app monorepo (async Django 6 + uvicorn with FastAPI-style pydantic views, Vue 3 + TypeScript + Vite, minimal dependencies). Reference issues from there as Spider2298/oikolab#N.

A content-marketing operations dashboard built on a garden/ecosystem metaphor (UI in Turkish). Content items ("Tohum" / seeds) grow through a 5-layer funnel (K1 Farkındalık → K5 Çoğalma) across 3 age-based audience segments (Habitat A/B/C). At the core is an event-scoring engine: platform interactions become weighted OikosEvents, rolled up into scores, vitality indexes, and threshold-based alerts (bottleneck / decay / pruning / re-engagement).

Repository guide

Path Contents
mvp-breakdown.md MVP scoping, work packages, dependency graph, open questions — read first
docs/design/ Figma screen exports (producer panel, admin panel, modals, states)
design-tokens/ Color/radius tokens exported from Figma — CSS vars, Tailwind config, TS, JSON. Single source of truth for colors. Dark theme is default.
docs/ The three handoff documents (PDF, Turkish): 01 Metaphor Dictionary · 02 Business Logic & Formulas · 03 Data Model & API

Key concepts (metaphor → reality)

  • Tohum (Seed) = a content item; status flow Ekiliyor → Kök Salıyor → Filizleniyor
  • Katman (K1–K5) = funnel stage; Habitat A/B/C = audience segment (18-24 / 25-34 / 35-40)
  • Oikos Puanı = Σ(interaction count × depth weight), weights 0.1–20
  • PH (0.0–1.0) = audience openness (Çekingen / Nötr / Meraklı) — drives content tone
  • Kırmızı Vana / Kuraklık / Çürüme / Budama / Can Suyu = alert types from threshold rules
  • Roles: Tohum Ekici (creator, K1–K3) · Bahçıvan (gardener, K4–K5) · Ekosistem Lideri (admin)

Fonts: Playfair Display (headings), DM Sans (UI), DM Mono (data).

Work is tracked in GitHub issues — each pre-MVP issue is a self-contained implementation brief with design references and acceptance criteria.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages