DevCentr

Welcome to the DevCentr documentation.

Overview

This site documents the DevCentr app (developer tooling, workflows, and project management), the Dev Center Knowledge Base (practices and reference material), and related publishing and contribution guides. Use the links below to jump to a section or start with the Knowledge Base for onboarding and how-tos.

DevCentr is a developer tooling application that provides:

  • Developer tool setup

  • Environment management

  • Project modeling and visualization

  • Repository management and connections

  • CI/CD workflow management

  • Central secrets registry (Secrets Manager) for .env-aware key storage and optional injection

We have coined a new term for our kind of software: we call this a Development Orchestration Suite (DOS).

Templates & Standardization

DevCentr integrates tightly with the Standard Project Templates library. It acts as the local engine for:

  • Automatic Tech-Stack recognition: Identifying the languages and frameworks used in your projects.

  • Template Installation: One-click setup for standardized .vscode settings and workspace configurations.

  • Update Management: Keeping your project configurations in sync with organization-wide standards.

Why Does This Documentation Exist?

How much does the typical programmer know about the overall tooling they use — from Git’s intricacies and configuration, to GitHub CI/CD, to GitLab CI/CD, to package manager implementation details? I feel like I’m constantly learning and relearning all of these config settings in an effort to master it.

— A frustrated developer

The honest answer: most programmers operate on a "good enough to unblock myself" level with most of their tooling.

The Knowledge Distribution

Level ~% of Devs What it looks like

Copy-paste survivor

40%

Googles error messages, copies Stack Overflow answers, doesn’t know why it works

Functional user

40%

Knows common commands, has a mental model that’s 60% accurate, can troubleshoot basics

Confident practitioner

15%

Understands the underlying model, can configure from scratch, teaches others

Deep expert

5%

Reads source code, knows edge cases, writes the Stack Overflow answers

Why This Happens

  1. The surface area is insane. Git alone has 150+ commands. Then there’s GitHub Actions, GitLab CI, Docker, Kubernetes, npm/pnpm/yarn, pip/uv/poetry, cargo, webpack/vite/esbuild, ESLint, Prettier, TypeScript config, shell scripting, SSH, GPG…​ Nobody masters all of it.

  2. The docs assume prior knowledge. Git’s man pages are famously written for people who already understand Git. Most tooling docs explain what without explaining why or when.

  3. Tribal knowledge dominates. Teams pass down incantations. "Just run this script." "Copy this CI file." The why gets lost.

  4. It’s not rewarded. Shipping features gets you promoted. Understanding core.autocrlf doesn’t. So people rationally optimize for output, not depth.

  5. Teachers often don’t know either. Academia lags industry by 5-10 years. Many CS professors have never used CI/CD professionally.

The Uncomfortable Truth

Most production software runs on configurations that someone copy-pasted from a blog post years ago, nobody fully understands anymore, and everyone’s afraid to touch. It works, so nobody questions it.

The Purpose of This Knowledge Base

This documentation exists to bridge the gap — to provide the reference material that should exist but doesn’t, because the people who understand tooling deeply rarely document it, and the people who document it rarely understand it deeply.

If you’re bothered by not understanding your tools — if you want to master your tooling rather than just survive it — you’re in the right place.

Documentation Structure

This documentation site mixes two ways of grouping content and this section explains how they fit together.

Two Organization Philosophies in This Site

The DevCentr docs currently mix two ways of grouping content:

  1. Product/feature modules — ROOT (overview, vision), specifications (component specs), secrets-manager (one product area), publishing (release/distribution), upstream-contributions. Each module is tied to a thing or workflow.

  2. Intent-based (Diátaxis) module — general-knowledge. Content is grouped by user intent: tutorials, how-to, reference, explanation. It is topic-agnostic and acts as shared "best practices and reference" for the whole ecosystem.

So: everything in the docs is documentation; not everything is in the knowledge-base module. The knowledge-base is the shared, intent-first content that doesn’t belong to a single product.

Quick Links

Features:

Related Products:

  • Secrets Manager — Central registry for keys, .env copy/inject, and Docker

Knowledge-base:

  • General Knowledge — Tutorials, how-tos, reference, and explanations of common development tools and practices (Diátaxis-organized)