ESP32-S3 Bench Guide
ESP32‑S3 N16R8 벤치 가이드: 실시간 핀아웃, 강의, 시뮬레이터 및 벤치 로그
현대 좌파를 형성한 사상·사상가·텍스트·경향·논쟁과 그 관계를 보여주는 살아있는 사회주의 지도
A living map of socialist thought — the ideas, thinkers, texts, tendencies and debates that shaped the modern left, and the relationships between them.
교육TypeScript · CSSGitHub @Gregely온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A living map of socialist thought — ideas, thinkers, texts, tendencies, debates, and the relationships between them.
This repository holds the public site, a relational content model in which relationships and sources are first-class
data, the Atlas Editorial Desk — a multi-user publishing system with roles, review workflow, revisions, rich text,
sources and media — and a small set of clearly marked sample records that demonstrate the system. It is built as a
machine for holding the theory, not yet as the theory itself.README 전문 보기 ↗A living map of socialist thought — ideas, thinkers, texts, tendencies, debates, and the relationships between them.
This repository holds the public site, a relational content model in which relationships and sources are first-class data, the Atlas Editorial Desk — a multi-user publishing system with roles, review workflow, revisions, rich text, sources and media — and a small set of clearly marked sample records that demonstrate the system. It is built as a machine for holding the theory, not yet as the theory itself.
npm install
npm run dev # migrates + seeds data/atlas.db on first run, then starts http://localhost:3000
npm run corpus -- setup # optional: load the committed research corpora (Initial Marx Corpus, Guided journeys)
data/*.db is not in Git, so a new checkout starts with the sample records only. npm run corpus -- setup imports
the corpora committed under corpus/ into your database, for review in the desk: it applies migrations, imports
each corpus that is not there yet (prerequisites first), submits it for review and publishes nothing. It leaves a
corpus that is already present untouched, so it is safe to run again. See docs/CORPUS.md.
npm run dev creates four demo accounts, one per role —
[email protected], [email protected], [email protected], [email protected] — all with the password
atlas-demo-2026. They are never created in production; create real accounts with npm run user:create.| Command | What it does |
|---|---|
npm run dev / build / start | Next.js (each ensures the database exists first) |
npm run typecheck | TypeScript, no emit |
npm run test:e2e | Playwright suite (public site, editorial workflow, desk, mobile) against a throwaway data/test.db |
npm run db:reset | Delete the local database, migrate and re-seed the samples |
npm run db:migrate / db:seed / db:reindex | Individual database tasks |
npm run corpus -- setup | Import the committed research corpora that this database does not have yet (unpublished, submitted for review) |
npm run db:generate | Generate a migration after editing src/lib/db/schema.ts |
npm run user:create -- --email … --name … --role admin | Create a desk account (prints a generated password once unless --password is given) |
npm run user:list | List desk accounts |
Copy .env.example to .env.local to configure the database URL and the media folder.
DATABASE_URL (and DATABASE_AUTH_TOKEN for libSQL/Turso) and MEDIA_DIR (a persistent folder for uploads).npm run build && npm start — migrations run automatically before both.npm run user:create -- --email [email protected] --name "Your Name" --role admin.
Administrators then manage everyone else from People in the desk.| Area | Route | Notes |
|---|---|---|
| Home | / | What the site is, a prominent search, Guided beside it with other ways in; the collection as a table of contents (every section at equal weight); concepts at three depths; open debates; texts and lives; Guided journeys and learning paths; the Theory Map as a plate; historical moments; method |
| Library | /explore | Thinkers, concepts, tendencies, debates, texts and periods, each with its own visual treatment |
| Theory Map | /map | The relationship map as an atlas plate: by time or by affinity, thinkers alone or with concepts or tendencies; a key and the most-connected entries |
| Geography | /geography | A world map of where the tradition lived and worked: birthplaces, residence, exile, political activity, where texts were written and published, events and regional influence; filters by kind of entry, kind of association and period; select a place, or trace an entry's places in order |
| Thinkers | /thinkers, /thinkers/[slug] | Lifespan index with tendency filters; entry with ideas, network graph, works, influences, disagreements, legacy, timeline |
| Concepts | /concepts, /concepts/[slug] | A–Z glossary; entry with a descending depth reader (30 seconds → 5 minutes → deep dive), primary texts, debates, related-concept constellation |
| Debates | /debates, /debates/[slug] | Positions side by side; compare two or more to see shared and divergent stances; arguments and counterarguments |
| Timeline | /timeline, /timeline/[slug] | Zoomable (century / half-century / decade) multi-lane timeline with contextual panel; vertical list on phones |
| Texts, tendencies | /texts…, /tendencies… | Catalogue and traditions |
| Guided | /guided, /guided/[slug]?step=n | Curated journeys through existing entries, one step at a time: where you are, the idea (with its depth reader), why it matters, a source excerpt, and where it leads; progress and Continue kept in the browser, and a line under the masthead leads back to the route from anywhere else on the site |
DATABASE_URL can point at a libSQL/Turso server with no code change. The schema is relational and portable to Postgres (see docs/DATA_MODEL.md).docs/ARCHITECTURE.md — layers, data access, rendering, design system, scalingdocs/DATA_MODEL.md — entities, relationship types, sources and citations, debates, pathsdocs/EDITORIAL.md — the editorial desk: roles, workflow, revisions, rich text, sources, media; the sample-content policydocs/CORPUS.md — research corpora: format, verification, import and review (npm run corpus)docs/corpus/initial-marx-review.md — the review queue for the Initial Marx CorpusThe Initial Marx Corpus (corpus/initial-marx/) is a researched introduction to Marx, his predecessors and the
Marxism of 1890–1919. Load it with npm run corpus -- import after seeding; every entry it touches stays unpublished
and awaits human review (see docs/CORPUS.md).
All seeded entries are flagged sample (is_sample) and labelled as such on the site. Summaries are brief and conventional.
Only a handful of very widely reproduced quotations are included, each tied to a cited edition and flagged
unverified until checked; elsewhere excerpts are references to passages, not invented text. Debate stances are
editorial readings, presented descriptively.
| Learning paths | /paths, /paths/[slug]?step=n | A route through ideas with next / back / explore and detours; progress kept in the browser |
| Search | overlay (/ or ⌘K) and /search | SQLite FTS5 full-text search grouped by entity type, with related entries |
| Sources | /sources, /sources/[id] | Bibliography; every citation and excerpt points here |
| Bookmarks | /bookmarks | Per-browser reading list |
| Editorial desk | /admin | Roles, review workflow, revisions, rich-text editor, relationship builder, sources, excerpts, media library, previews, audit log — see docs/EDITORIAL.md |