Coders Lingo is under continuous, active development. This page tracks the major content additions,
structural fixes, and site improvements as they ship — so you always know the site is current and
actively maintained, not a static archive.
fix
Critical fix: broken exercise interactivity restored across 630 pages
Found and fixed a bug where `<script lang="ts">` tags — used across 630 files — were silently shipping raw, un-compiled TypeScript straight to the browser instead of plain JavaScript, causing a syntax error that quietly disabled answer-checking, scoring, and progress bars on a large share of exercise pages. Also restored real interactivity to 22 exercise pages that had no working click handlers at all, and fixed 57 stale internal links (mostly outdated blog/interview cross-references on role pages).
content
New: AI/ML, Security, Data Platform & SRE vocabulary hubs
Added four new hub pages that tie together previously scattered exercise categories: AI/ML Vocabulary (10 categories), Security Vocabulary (11 categories), Data Platform & Analytics Vocabulary (9 categories), and SRE & Reliability Vocabulary (5 categories) — each with cross-links back and forth so related topics are easy to discover. Also added a Technical Writer role guide and learn path, a Security Engineer learn path, 5 new "reading real error messages" exercises (Docker, Git, AWS CLI, Terraform), PMP and ISTQB certification vocabulary, 9 new comparison pages, and 15 downloadable cheatsheet PDFs.
seo
Faster pages: self-hosted fonts, smaller JS, real social-share previews
Removed the Google Fonts CDN dependency in favor of self-hosted font files (a small speed and privacy win), made the search library load only when search is actually used, and switched every social-share preview image (Open Graph / Twitter Card) from SVG to PNG — most platforms like Facebook, Slack, and LinkedIn do not render SVG previews, so shared links were showing no image at all until now.
i18n
Full UI translation coverage across all 20 languages
Closed a gap where 9 whole sections of site UI — the topics hub, blog, glossary, vocabulary hub, phrasebook, resources, contact form, accessibility labels, and Word of the Day — were silently falling back to English on 19 of our 20 supported languages. Every locale (Arabic, Bengali, German, Spanish, Persian, French, Hindi, Indonesian, Italian, Japanese, Korean, Malay, Polish, Portuguese, Thai, Turkish, Ukrainian, Vietnamese, Chinese) now has complete, natively-translated UI copy with zero missing keys against the English source of truth.
9 further content passes across two days added new vocabulary deep-dive batches (data structures, algorithms, distributed systems, AI/ML infrastructure), collocation batches (HR, workplace, and vendor-management English), and pronunciation drills (consumer-tech brand names), plus 75 new blog posts, 31 new grammar pages, and 30 new interview-role pages. Site totals reached 1,358 blog posts, 459 grammar pages, and 502 interview-prep role pages.
content
Content Pass 50–51: blog reaches 1,157 posts
Two more passes of vocabulary, collocation, and pronunciation batches, plus 50 new blog posts (1,107 → 1,157), 22 new grammar pages, and 20 new interview-role pages, continuing to steer into fresher workplace-English and technical-writing scenarios as earlier angles (standups, postmortems, RFCs) saturated.
A routine orphan-page audit found that vocabulary/index.astro's hand-maintained registry array was missing 843 already-published deep-dive vocabulary pages — they existed, built, and were indexed in the sitemap, but had zero internal links from any hub page. Fixed by re-syncing the registry from each batch's real metadata. This is now tracked as a structural fix to invest in (see the content-collections migration item on our roadmap) so future batches can't silently repeat it.
content
Content Pass 42–49: blog grows from 907 to 1,107 posts
FAQ blocks and JSON-LD added across exercise category hubs
Added a standardised 10-question FAQ block (3 open + 7 collapsed) with FAQPage schema markup to 112 exercise category index pages, improving rich-result eligibility and answering the most common learner questions directly on category hubs.
Something out of date or missing?
If you spot an error, a stale reference, or a gap in coverage, we want to know.