Skip to content
Digital Nestby Ulises Jeremias

Community · shared workshop

Community — shared workshop that connects every world

The shared workshop connected to every project world. The bench where drafts, reviews, and small PRs become documentation — with Discord for live help and GitHub for the trail.

Workshop narrative

A workshop, not a feed

The Digital Nest is built like a hornero nest — stick by stick, with reviewable joints. Community is where that work is visible before it is finished.

The shared workshop — connected to every world

Community is the shared workshop that connects every world in the Digital Nest — dotfiles, workstation, toolkit, V, and Create Awesome. It is not a broadcast channel: it is a bench where questions, drafts, and fixes circulate before they become documentation.

The principle is simple: work in the open, link the evidence, and leave a path for the next person. Every pattern in this site has a provenance — a PR, a discussion, or a commit you can open. If you cannot verify it, it is not on the page.

Who this is for — and who it is not

For builders who keep their system reproducible, their CLIs composable, and their AI assistance auditable. You may be tuning a Hyprland rice, adding an addon to cna-templates, or reviewing a VSL numerical method — the workshop welcomes the same rigor at any scale.

It is not a support desk for proprietary tooling or employer-sponsored work. NaNLABS and other work contexts are mentioned for transparency only; the community has its own Code of Conduct, moderation, and privacy expectations (see below).

How we work — small boards, clear edges

We favor small, reversible contributions with typed boundaries: a docs fix with a Zod-validated frontmatter, a template addon with a test, a shell script with set -euo pipefail. Weekly triage surfaces labeled issues — good first issue, documentation, templates — so you can pick a board that matches your time and depth.

Design and content decisions are recorded near the code (ADRs, PR descriptions, route tables). If a choice matters for more than one world, it is written down before it ships.

Principles you can check

  • Evidence over claims — every pattern links to a commit, PR, or doc.
  • Typed boundaries — Zod at the edge, static HTML by default, islands only when justified.
  • One concern per PR — small boards that a single reviewer can hold in mind.

Community is distinct from employer (NaNLABS) — participation is voluntary and moderated independently.

Discord · workshop live

Join the shared workshop

The Create-Awesome Discord is where templates, rices, and V libraries get discussed before they ship. One invite, all families — Node, Python, and V.

Create-Awesome Discord

Verified invite · ask in #help · share a draft · pick a labeled issue together. Blurple is used only for this call-to-action — no vanity member counts without an authoritative source.

Invite: discord.gg/bR5VyATgka · community distinct from employer

Join Discord

Opens in a new tab · free, no account required to preview

Blurple #5865F2 is used only as an accent for this Discord CTA. No member counts or activity metrics are shown without a refreshable authoritative source.

Project families

Three families, one composition model

Choose a template, add addons, and ship files you own. Weekly triage keeps the boards fresh — check the labeled issues rather than relying on announcements.

Node

Create Awesome — Node

Templates + addons for frontend, backend, and full-stack. Compose files, not black boxes.

TypeScriptNode

npm create awesome-node-app@latest my-app -- --template react-vite-starter

Templates → (opens in new tab)
Python

Create Awesome — Python

FastAPI, Django, CLI, Celery with uv. Same composition model, Python idioms.

Pythonuv

uvx create-awesome-python-app@latest my-app --template fastapi-starter

Templates → (opens in new tab)
V

Create Awesome — V

Native, fast scaffolding for the V ecosystem — experimental, typed, and reviewable.

V

create-vlang-app my-app --template web-server

Templates → (opens in new tab)

Weekly contribution opportunities

Triage runs weekly. Look for these labels; each issue has scope and the file it touches.

Good first issuesDocs, copy, and small template addons with tests — ideal for a first PR.good first issuedocumentationTemplates & addonsNew templates or addons that compose cleanly with existing stacks.templatesaddonsDocumentationClarify an ADR, fix a workflow, or expand a guide — verified docs matter as much as code.documentationenhancement

Contribution pathways

Two trails, same workshop

Pick the trail that matches your time and depth. Both end with a reviewed, reviewable PR — not with a badge.

🌱 Beginner

Beginner — first contribution in an afternoon

Start small, ship with tests, and learn the review rhythm. No setup magic required.

Audience: New to the workshop or short on time

  1. Seven lines that set the tone: be kind, be precise, stay on topic.Code of Conduct → (opens in new tab)
  2. Filter by good first issue or documentation. Each has scope, expected file, and review checklist.Browse issues → (opens in new tab)
  3. Use the matching CLI (Node / Python / V) to generate a test app and reproduce the change.
  4. One concern per PR, typed at the edge (Zod), with a clear title following Conventional Commits.
Find a good first issue → (opens in new tab)
🛠️ Experienced

Experienced — shape the scaffolding

Design templates, CLI composition, and pipelines that survive a major version.

Audience: Comfortable with Astro, CLIs, or scientific libraries

  1. Read docs/PROJECT_STRUCTURE.md and docs/STATE_MANAGEMENT.md — feature-based, thin pages, content-first.Project structure → (opens in new tab)
  2. Propose the file map, config surface, and test plan. Templates are static HTML until an island is justified.
  3. Astro check, ESLint, Vitest, and build must pass. Zod at the boundary, no hidden client state.
  4. Review a beginner pathway PR with actionable, kind comments. The workshop scales when reviews teach.
Open a template proposal → (opens in new tab)

Both pathways follow Conventional Commits, pnpm type-check, and pnpm build — the same gates that protect main.

Support & agreement

Where to ask, what to expect

The workshop is async by default. Prefer the surface that leaves a linkable trail — GitHub first, Discord for live drafts.

(opens in new tab) (opens in new tab) (opens in new tab) (opens in new tab)

Code of Conduct & support

By participating you agree to the Code of Conduct (opens in new tab) — our seven-line agreement on kindness, precision, and staying on topic. For broader guidance, see the support wiki (opens in new tab).

Enforcement is documented and proportionate, with a private first warning. See moderation below.

Moderation & privacy

Guardrails for a calm workshop

Moderation is documented, privacy is minimal, and metrics are honest — or they are not shown at all.

Scope and independence

Community spaces are not employer channels. Moderation decisions are made by community moderators, documented in PRs and issues, and appealable via the Code of Conduct process.

Privacy — minimize retention

Discord handles and GitHub profiles are public by participation. No private analytics, no member counts without an authoritative refreshable source, and no tracking beyond what GitHub and Discord provide by default.

Enforcement — graduated, documented

Warnings are private and specific. Repeat or severe violations lead to temporary or permanent restrictions, always with a written rationale referencing the Code of Conduct.

Accessibility — participate without Discord

Every onboarding path, template decision, and weekly opportunity is also reachable via GitHub issues and docs. Discord is a convenience, not a gate.

Metrics policy

No member counts or vanity metrics are shown without an authoritative, refreshable source. Counts are omitted by design.

If a count appears in the future, it will state its source, timestamp, and refresh cadence — and link to the query that produces it. Until then, the workshop is measured by merged PRs and closed issues, not by headcounts.

Bring a question, leave a link

Whether you fix a typo, add an addon, or review a VSL method — the workshop is open. Start with a labeled issue or ask in #help.

Join Discord → (opens in new tab)Open an issue →Read field notes →

All links verified 2026-08-07 · Invite discord.gg/bR5VyATgka · Code of Conduct →