ojitoss/blogs

Purpose and Entry Points

This is a static personal blog repository, not an executable application. The primary entry point is README.md, which indexes blog series and links readers into each series’ own README.md.

Content Packaging Model

Each blog is isolated in a top-level directory containing its landing post, numbered sections, and optional media. This folder-per-blog boundary allows series to evolve independently without shared runtime code:

• autag-the-good-parts/

• things-i-regretted-about-autag/

• things-i-regretted-about-autag/assets

Blog Series: Autag Retrospective

The completed series documents lessons from “Autag,” described as the author’s first boilerplate-generating CLI and its later failure modes. Its reader flow begins at the series overview and proceeds through ten ordered Markdown chapters:

• things-i-regretted-about-autag/README.md

• things-i-regretted-about-autag/1.md

• things-i-regretted-about-autag/10.md

Blog Series: Positive Follow-up

A separate, work-in-progress series captures successful decisions from the same project. Its current boundary is a standalone series document rather than a numbered chapter set:

• autag-the-good-parts/README.md

Navigation and Control Flow

Navigation is link-driven and static: repository index → series landing page → numbered section pages. Ordering is represented by numeric filenames in the retrospective series, while the root table of contents establishes cross-series ordering and publication state:

• README.md

• things-i-regretted-about-autag/README.md

• autag-the-good-parts/README.md

Runtime, Infrastructure, and External Services

No application runtime, build pipeline, deployment configuration, package manifest, or external service integration is present in the supplied tree. Markdown files and local assets are the repository’s deployable content surface; rendering is delegated to whatever Git hosting or static-document viewer consumes the repository.