The latest articles on DEV Community by aurorawrites189-eng (@aurorawrites). https://dev.to/aurorawrites https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4178733%2Fb1b7c343-d75f-4b46-a048-09ce84539f5e.png https://dev.to/aurorawrites en aurorawrites189-eng Mon, 12 Oct 2026 09:00:39 +0000 https://dev.to/aurorawrites/i-built-a-free-multilingual-urdu-english-writing-platform-heres-what-i-learned-5136 https://dev.to/aurorawrites/i-built-a-free-multilingual-urdu-english-writing-platform-heres-what-i-learned-5136 <p>I wanted a place where people could read and publish stories, articles and essays in <strong>Urdu and English</strong> — without a paywall, without an English-only bias, and without needing a laptop to get started. So I built <a href="https://nazmhub.pages.dev" rel="noopener noreferrer">NazmHub</a>: a free writing and storytelling community platform.</p> <p>Here's what the build taught me.</p> <h2> 1. Bilingual from the ground up, not bolted on </h2> <p>Most multilingual sites treat the second language as an afterthought — a Google Translate widget slapped on top. NazmHub routes everything through language prefixes (<code>/en/...</code>, <code>/ur/...</code>), with separate i18n dictionaries, an Urdu-friendly font stack, and RTL-aware layouts. The lesson: if a language matters to your users, it has to live in your routing, your design system, and your content model — not just in a translate dropdown.</p> <h2> 2. Next.js + Supabase is a great solo-founder stack </h2> <p>The whole platform — auth, posts, comments, a kids' story library, episode-wise novel serials, and an admin moderation queue — runs on Next.js (App Router, edge runtime on Cloudflare Pages) with Supabase as the database and auth layer. One person can genuinely ship and operate this. The trickiest real-world bug I hit wasn't code at all: a misconfigured Supabase URL (an extra <code>/rest/v1/</code> suffix in the env var) made every database query fail silently-ish. Environment config deserves the same review rigor as code.</p> <h2> 3. Teaser gating beats hard paywalls for growth </h2> <p>One feature I'm proud of: logged-out readers see a ~80-word excerpt of each story, and the full piece unlocks on free signup — while the Kids' Corner stays completely open. It converts casual readers into community members without punishing anyone. If you're building a content platform, think of your paywall (or signup wall) as a conversion funnel, not a fence.</p> <h2> 4. Content moderation is a product feature, not an afterthought </h2> <p>Writers can create their own novel series and submit episodes, but nothing goes live without admin approval. Building the moderation queue early — before any stranger could publish — saved me from the classic "launch now, moderate never" trap. Trust and safety is a feature you ship on day one.</p> <h2> 5. Free hosting is genuinely enough to start </h2> <p>The whole thing runs on free tiers (Cloudflare Pages + Supabase free plan). Total hosting cost: $0. The site is live at <a href="https://nazmhub.pages.dev" rel="noopener noreferrer">nazmhub.pages.dev</a>, serves real readers, and I haven't paid a cent for infrastructure. Don't let "I need money to start" stop you from shipping.</p> <p>If you read or write in Urdu or English and want a home for your stories, come say hi: <a href="https://nazmhub.pages.dev" rel="noopener noreferrer">NazmHub</a>. And if you're building something similar, I'd love to hear what stack choices worked for you — drop a comment.</p> webdev nextjs supabase opensource