dev.mn

Mongolian builders and their work scatter across social posts, personal networks, repositories, and launch announcements that drop out of view within days.

dev.mn is a curated record instead: who is building, what they shipped, how the work changed, and where somebody else can learn from it or contribute. Builders get a public profile, a place to launch a project, a devlog, practical engineering guides, and a free dev.mn subdomain for the project itself.

The product rule is Build > Talk. A working project, a useful write-up, or an honest devlog carries more weight than personal-brand activity.

It is deliberately not a social network, an engagement feed, a course marketplace, or an open submission directory with no quality bar.

Project identity starts in the subdomain registry: a reviewed JSON record connecting a builder, a project, its domain, its repository, and its destination URL. That record lives in git, so who claimed which name — and why it was approved — stays inspectable.

The application database holds what a registry should not own: votes, featured state, profile customisation, devlogs and replies, activity streaks, and richer launch presentation.

The same split governs content. Long-form articles use MDX and pull-request review because they should stay curated and attributable. Devlogs live in the database, because a daily progress note should not require a branch and a pull request.

A deliberately small full-stack boundary: Next.js App Router with Server Components and Server Actions, Better Auth with GitHub OAuth, Drizzle ORM, and PostgreSQL on Neon.

GitHub OAuth is not incidental. If the platform's premise is that shipped work counts more than activity, the identity it verifies should be the one where the work lives.