Developer shares guide to contributing Spanish translations for MDN Web Docs

·1 views

A developer has spent three weeks translating MDN Web Docs into Spanish, aiming to update documentation that had fallen significantly behind its English counterpart. As part of their open-source journey, they documented the contribution process to help future Spanish-language contributors. Key rules include never translating file paths or slugs, converting internal links from /en-US/ to /es/, and translating only visible link text and image alt text. Front matter must retain only specific fields such as title, slug, and source commit, while callout tags like [!NOTE] remain untouched. The guide serves as a practical reference for anyone looking to contribute to MDN's Spanish localization effort.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How a Bootstrapped Filipino Wedding SaaS Reached 1,000 Users via Hyper-Local SEO

WedPlanner, a bootstrapped wedding planning SaaS targeting Filipino couples, grew from zero to 1,000 registered users over 18 months without any advertising budget or influencer partnerships. The founders identified that Filipino couples were searching Google for highly specific, locally relevant wedding planning questions that established platforms like The Knot or Zola were not addressing. Their strategy centred on three pillars: hyper-local SEO, long-tail keyword targeting, and Answer Engine Optimization (AEO), which structures content to directly answer user queries and capture featured snippets. Each article followed a strict format — leading with a direct answer, adding context, providing an actionable framework, and then introducing WedPlanner as a practical tool. Their best-performing piece, a wedding budget breakdown for the Philippines, now ranks for 47 related keywords and generates around 340 organic sessions per month.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Voice Models Passed QC With Hidden Defects That Speech-to-Text Could Not Detect

A developer conducting quality control on text-to-speech (TTS) models initially reported a 100% pass rate after using Whisper for transcription-based inspection across 12 AI voices. A later review revealed that 4 of the 12 models contained audio defects — brief, unscripted utterances of 0.1 to 0.3 seconds occurring after roughly half a second of silence at the end of phrases. These artifacts were traced to training corpus contamination, where short filler sounds slipped past the quality gate and became verbal tics in the model output. Because Whisper either dropped or misread these short sounds, the transcription-based method created a blind spot that masked the defects entirely. The developer subsequently developed a waveform-analysis approach using RMS envelope segmentation to detect voiced blocks that fall outside the expected script structure.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How ~/.ssh/config Simplifies Multi-Server SSH Management for Developers

Managing SSH connections across multiple servers often means repeatedly typing long commands with key paths, ports, and usernames, which is error-prone. The OpenSSH client's ~/.ssh/config file allows developers to store per-host settings as named aliases, reducing each connection to a simple 'ssh hostname' command. The IdentitiesOnly yes directive is recommended to prevent the client from offering unintended keys, which can trigger authentication failures or IP blocks on secured servers. Wildcard patterns let users apply shared settings across groups of similar hosts, while OpenSSH reads the file top-to-bottom, giving priority to whichever matching block appears first. For larger setups, the Include directive, available since OpenSSH 7.3, allows the configuration to be split into separate files per project, making organisation and cleanup more manageable.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Free open API lets AI agents check if a recommended store is a scam

A developer has released a free, no-authentication domain reputation API designed to help AI agents verify whether a recommended store or URL is potentially fraudulent. The tool, called the UTA Scam Checker, applies transparent heuristics including typosquatting detection, suspicious TLD flagging, punycode homograph analysis, and URL shortener identification. Unlike paid commercial alternatives such as WHOISXML or IPQualityScore, it requires no API key or registration and exposes the full reasoning behind every risk decision. The API returns a structured JSON response with a trust decision — TRUSTED, CAUTION, or SUSPICIOUS — along with the specific checks that triggered the result. The project is open source and positioned as a lightweight first-pass safety layer for AI agents that recommend products, stores, or affiliate links.

0 comments Read more at DEV Community