Content Quality Checklist

Every lesson on CodingEasily goes through this checklist before it is published or updated. It explains what you can expect from our pages and how we decide that a page is ready. It works together with our editorial policy.

1. Code and output

• Every code block is run before publishing – Python with Python 3, C with gcc using -Wall -Wextra, Java with javac, SQL on a real MySQL/MariaDB server, JavaScript in a browser.
• The output shown on the page is the real output of that run, not typed by hand. When a program uses input(), the sample input is shown.
• Error examples show the actual compiler or interpreter message, so learners recognise it on their own screen.
• Charts and screenshots in data-science lessons are generated by the code shown on the page.
• Code is checked for older environments common in schools and shared hosting where relevant.

2. Accuracy of steps and facts

• App menu paths (Google, Microsoft, Android, iPhone) are written for the current version, and we mention when names differ by device.
• Numbers such as limits, helplines and legal rules are checked against the official source (for example RBI, cybercrime.gov.in, CBSE).
• Spreadsheet examples (Goal Seek, scenarios, formulas) are recalculated in a real spreadsheet before publishing.
• If something changes often, the page says so instead of giving a fixed figure that will go stale.

3. Learning value

• The page answers a real learner question and states the purpose in the first paragraph.
• Concepts are explained with Indian, everyday examples – marksheets, fees, UPI, school records – not abstract foo/bar data.
• Each lesson includes common mistakes, a practice task and FAQs with direct answers.
• Day-wise courses end with a project that uses everything learned, so learners can show real work.
• No two pages repeat the same template text; each page must add something specific to its topic.

4. Hindi and English versions

• Both versions carry the same meaning and the same examples; Hindi uses Devanagari with technical terms kept in English where learners see them on screen.
• Code, outputs and menu names stay identical in both languages.

5. Reading experience

• Pages are checked at phone width (360–390 px) for horizontal scrolling, readable code blocks and tap-friendly links.
• Internal links are tested so they do not lead to missing pages.
• Ads, when shown, must not push the lesson content below the first screen or interrupt code examples.

6. Corrections and updates

• Reported mistakes are re-tested and fixed; the corrected code is run again before publishing.
• Old pages that were replaced by a better lesson are permanently redirected to the new page instead of being left as duplicates.
• Found an error? Send the page link and the exact line through the contact page.