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.
content
8 new exercise categories and 13 new profession pages
Built out 8 exercise categories that were on the roadmap but never shipped: Containers & Virtualization, Cryptography & PKI, Developer Hiring, Game Engine Language, Networking Language, Product Design, Testing & QA, and UX Research — several had partially-built pages sitting unlinked from earlier work, so this pass also reconnected them properly instead of duplicating content. Added 13 new profession pages under /topics/: iOS/Swift, Android/Kotlin, React/Next.js, Python, Go, TypeScript, Linux sysadmin, computer vision, NLP, health IT, SAP/ERP, robotics/ROS, and technical educator. Also closed out the FAQ rollout from earlier this week on its last 2 remaining exercise categories, so every exercise, vocabulary, and glossary page on the site now has one consistently.
seo
FAQ answers added to every exercise, vocabulary, and glossary page
Extended the FAQ-schema work from earlier this week beyond blog posts: every exercise category page, every vocabulary deep-dive page (1,400+), every glossary term, tag page, and Word of the Day entry now shows a real "Frequently Asked Questions" section with answers grounded in that specific page's own content, not generic filler. Also fixed a visual bug from rolling this out in parallel across ~170 page templates at once: a naming mismatch meant some of those new FAQ headings weren't picking up their intended styling — now consistent site-wide.
content
~150 new pages across 11 categories, a real 404 bug fixed, and thin-content cleanup
Worked through 100 open backlog items in parallel: new exercise pages for mentoring, open-source, sprint-demo, word-formation, cross-cultural, log-reading, certification-prep, startup-language, abbreviations, ai-prompting, incident-response, debugging-language, documentation-types, estimation, and code-comments; new listening/reading sub-categories (executive briefings, security-audit reports, academic papers, investor documents); new meetings and presentations pages; 13 new profession pages; FAQ schema added to all blog posts; and download tracking plus PDF-thumbnail preview images added to every cheatsheet. Also found and fixed a real bug: 5 vocabulary links pointing at pages that never existed, and one more case of the March 2026 TypeScript-shipped-as-broken-JavaScript bug (this time on the vocabulary hub's progress-tracking script). Finally, expanded 60 thin profession pages with real cross-links to related articles and exercises, and grew 3 undersized glossary topics (programming paradigms, regex flags, error types) to 20 terms each.
content
Glossary and phrasebook expansion plan complete: 9/9 verticals, 6/6 scenarios
Finished the content-architecture plan from TODO_next_content_architecture_2026_07.md items #11-#12: added the final 3 glossary verticals — Accessibility Vocabulary (WCAG, ARIA, screen readers), NoSQL Vocabulary (document/key-value/wide-column/graph databases), and Linux Shell Vocabulary (pipes, permissions, processes, scripting) — plus the final phrasebook scenario, Postmortem Writing (blameless language, root cause analysis, action items). The glossary now covers all 9 newly planned verticals (18 topics total) and the phrasebook covers all 6 newly planned scenarios (14 total), on top of fixing an 8-page orphan-link bug found along the way.
content
2 more glossary verticals & 2 more phrasebook scenarios
Continued yesterday's content-architecture work: added Networking Vocabulary and Web Performance Vocabulary (Core Web Vitals — LCP, INP, CLS) to the glossary, plus Client Calls and Performance Review to the phrasebook. That brings the glossary to 6 of the 9 planned new verticals and the phrasebook to 5 of 6 new scenarios (see TODO_next_content_architecture_2026_07.md items #11-#12) — only accessibility, NoSQL, and Linux-shell vocabulary, plus a postmortem-writing scenario, remain.
content
New glossary verticals & phrasebook scenarios; fixed an 8-page orphan-link bug
Added 4 new glossary verticals — Software Testing Vocabulary, API Design Vocabulary, React Hooks Vocabulary, and CI/CD Pipeline Vocabulary — plus 3 new phrasebook scenarios: Onboarding to a New Job, Salary Negotiation, and Open Source Contribution. While building the phrasebook additions, found and fixed a real bug: phrasebook/index.astro never linked to any of its 8 existing deep-dive scenario pages (bug reports, code review, incidents, sprint, emails, interviews, technical discussions) — they were only reachable by guessing the URL. Added an "In-Depth Scenario Guides" grid linking to all 11 scenario pages, and registered every new page in the site search index.
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.