10 Repos, Zero Dependencies: A Production PHP/JS Portfolio

Description and use

The author extracted 10 reusable patterns from the production code of The DJ Calendar, creating a separate zero‑dependency repository for each, with CI tests and an MIT license.

Problem

Developers often rely on frameworks, build tools, and package managers, adding complexity and potential security risks.

Outcome

The extraction produced 10 production‑ready, zero‑dependency repos covering audio preview, equalizer visualization, geolocation maps, client‑side search, data pipelines, schema audits, and resume tools, all MIT‑licensed and CI‑tested.

Workflow

• 1. Identify a reusable pattern in the production code.
• 2. Refactor the pattern into a standalone repo with zero dependencies.
• 3. Add documentation, tests, and CI pipeline to prove functionality.
• 4. Publish the repo on GitHub and optionally host a live demo on GitHub Pages.
• 5. Repeat for each pattern.

Evidence

I run The DJ Calendar — a real‑time EDM tour date platform that's been in production since 2015. It's a single PHP + vanilla JS codebase with zero frameworks, zero build tools, and zero package managers.

Source

Over the past few weeks, I went through the codebase and extracted every reusable pattern into its own open-source repo. Not tutorials. Not simplified examples. The actual production code, cleaned, documented, and pushed.

Source

Every repo shares the same rules: Zero dependencies. No npm install. No Composer. No build step. Clone it and open index.html, or include the file.

Source

If it runs in the browser, there's a GitHub Pages demo. If it's backend, there's a CI pipeline proving it works.

Source

The search index handles real queries from real users. The tour pipeline processes real API responses with real edge cases (missing fields, rate limits, encoding quirks). The CSRF wrapper protects real endpoints.

Source