main-display

IGMC Dashboard

Config-first dashboard shell for calendar, tasks, notes, notifications, and ambient feeds. This first pass is wired to repository contracts and mock data so layout and control behavior can be settled before the live adapters are added.

Default page

overview

Theme

slate

Refresh

300s

Page set

Yearly Project

2026 yearly project

Monetize or publish every meaningful private repo

This page is the narrative skeleton for the yearly challenge: break the habit of hiding work until it feels perfect. Every repository should either earn its keep through a real offer, or become public with an honest README and a forgiving license.

Jan

completed

Inventory every private repository and tag it as publish, monetize, archive, or merge.

Feb

completed

Pick the first repos with the clearest path to a landing page, demo, or paid package.

Mar

completed

Define audience, value proposition, and one honest release standard for each candidate.

Apr

active

Build the public-facing dashboard and release pipeline that lowers the friction to ship.

May

planned

Ship one monetization trial: template pack, hosted tool, paid asset, or support offer.

Jun

planned

Prepare docs, screenshots, README polish, and first public demo loops for candidate repos.

Jul

planned

Publish at least one repository publicly with a forgiving license if monetization is still weak.

Aug

planned

Convert one project into a repeatable offer with pricing, delivery, and update policy.

Sep

planned

Reduce backlog fear by scheduling release weeks for repos that are good enough, not perfect.

Oct

planned

Run a visibility push: devlogs, changelogs, social proof, or case-study style writeups.

Nov

planned

Finalize year-end candidates and lock publish-or-monetize decisions repo by repo.

Dec

boss

Make every remaining candidate public under MIT or similarly forgiving terms if not monetized.

Release rules

  • Incomplete is acceptable if the README is honest and the scope is bounded.
  • Private by default is no longer neutral if it blocks learning, reuse, or revenue.
  • If a repo does not justify paid positioning by year end, publish it under MIT or similar.
  • The goal is momentum and exposure, not perfection theater.

Repo lanes

Monetize first

Repos with a direct product angle, service wrapper, template pack, or supportable niche.

Publish now

Repos that already teach something useful and only need honest framing, docs, and a license.

Needs one unlock

Repos blocked by a landing page, setup docs, screenshots, or a trimmed demo path.