architectus.dev: Public Learning Platform

Problem

Technical knowledge is siloed:

  • Certification guides - Vendor-specific, narrow focus

  • Blog posts - Scattered, no structure

  • Documentation - Often outdated, incomplete

  • Cross-domain learning - Rare to find Linux + Music + Languages together

Result: Learners bounce between dozens of sources. No unified learning path.

Solution

architectus.dev is a public learning platform covering the full spectrum of a Renaissance engineer:

architectus.dev Ecosystem

Philosophy

The name "Architectus" reflects the classical ideal: a master builder who understands structure, design, and execution across domains.

Modern interpretation:

  • Technical mastery - Linux, Windows, Networking, Security, Cloud

  • Automation skills - Ansible, Python, CI/CD

  • Communication - Technical writing, documentation

  • Culture - Languages, literature, music, mathematics

Content Domains

Technical Skills

Repository Topics

architectus-linux

Shell scripting, systemd, package management, troubleshooting

architectus-windows

PowerShell, Active Directory, Server Core, Group Policy

architectus-networking

CCNA/CCNP concepts, protocols, 802.1X, VLANs, design

architectus-security

Hardening, identity management, PKI, threat detection

DevOps & Cloud

Repository Topics

architectus-automation

Ansible playbooks, Python scripting, CI/CD pipelines, GitOps

architectus-cloud

AWS, Azure, GCP fundamentals, Kubernetes, Terraform

Humanities & Arts

Repository Topics

architectus-literature

Technical writing, documentation strategies

architectus-languages

Spanish (SIELE C1 preparation), Latin

architectus-mathematics

Applied mathematics, statistics for engineers

architectus-music

Violin technique, music theory

Architecture

Same docs-as-code pattern as domus-docs:

architectus-docs/          # Aggregator
├── antora-playbook.yml    # 11 content sources
└── build/                 # Generated site

architectus-*/             # Content repos (11 total)
└── docs/asciidoc/
    └── modules/ROOT/
        ├── pages/
        └── nav.adoc

Multi-Remote Strategy

All repos push to three remotes for redundancy:

architectus-push           # Custom script

# Pushes each repo to:
# - origin (GitHub) - Primary, public
# - gitlab (GitLab) - Backup
# - gitea (self-hosted) - Private mirror

Differentiation from domus-docs

Aspect architectus.dev domus-docs

Visibility

Public

Private (Cloudflare Access)

Purpose

Learning platform

Infrastructure operations

Audience

Anyone learning tech

Personal/team reference

Content

Tutorials, guides

Runbooks, procedures

Repos

11

19

Why Public?

  1. Portfolio - Demonstrates expertise to employers/clients

  2. Teaching - Others benefit from documented knowledge

  3. Accountability - Public commits = visible work ethic

  4. Community - Contributions, feedback, collaboration

Roadmap

Phase Deliverable Status

1.0

Core technical content (Linux, Windows, Networking)

Complete

1.1

Security and Automation tracks

Complete

2.0

Cloud and Kubernetes content

In Progress

2.1

Interactive labs

Planned

3.0

Video content integration

Planned

Links

Document Information

Author

Evan Modestus

Version

1.0

Last Updated

2026-02-22