About NAPOH

NAPOH publishes free, book-style courses in English, programming, mathematics, and chip design. Lessons connect direct explanation to worked evidence, named failure boundaries, independent practice, correction, and the next prerequisite.

Publisher and responsibility

The NAPOH Editorial Team is the publication identity responsible for curriculum selection, lesson structure, maintenance, and corrections. NAPOH is an independent educational publisher, not an accredited school, degree program, standards body, certification provider, or claim of independent peer review. Course completion records learning activity on the reader’s device; it is not a diploma or professional certification.

Why these courses and topics were selected

The catalog is a dependency map of durable software capabilities, not a ranking of job-market popularity and not a collection of every fashionable tool. A subject enters the programming curriculum only when it owns a distinct layer that learners must understand, can be reached from stated earlier knowledge, and can end in observable transfer evidence.

Begin from one shared mental model. Computing & Programming Foundations is the only zero-prerequisite course. Languages and specialties reuse its file, process, program, debugging, test, and version-control vocabulary.
Cover durable layers, not brand lists. The map includes language semantics, algorithms, Web documents and behavior, APIs, data, operating systems, security, delivery, reliability, applications, and AI. A vendor or framework receives its own course only when it introduces a substantial model that cannot be taught honestly as a small adapter.
Add a course only when its boundary is distinct. Every title must name what it owns, what comes before it, what it deliberately does not prove, and which later layer consumes its results. Overlapping syntax, transient libraries, and renamed versions stay inside the course that owns the underlying concept.
Select chapter topics by dependency and failure. A topic appears before the first example, project, or claim that needs it. Each chapter must explain the mechanism, show an observable result, expose a boundary or common failure, require independent practice, and connect to cumulative work.
Require transfer, not coverage alone. A complete course needs a multi-stage capstone or Project Lab target that another learner can reproduce, challenge, and extend. A long list of headings is not evidence that a subject deserves publication.
Publish only after the whole learning loop exists. A route is not labeled textbook-ready until every chapter has developed exposition, prediction-first examples, reasoned solutions, retrieval checks, graded practice, and a final integration boundary.

What the map does not claim. It is not a promise that every learner needs all 43 courses, that one framework is permanent, or that chapter completion proves professional experience. Begin with Foundations, choose one path after its entry checkpoint, and use current-edition exercises and transfer evidence to decide when to continue.

Inspect the complete course catalog → · Inspect the eight learning paths → · Inspect the transfer projects →

Editorial method and principles

A lesson is prepared by bounding its goal and prerequisites, explaining the mechanism, showing worked evidence and a failure boundary, and requiring an independent attempt with correction guidance. Publication counts include only material available on the live site.

Explain mechanisms. A chapter should explain why behavior occurs, not merely list syntax or commands.
State prerequisites and boundaries. Readers should know what a chapter assumes, where a technique applies, and where it fails.
Use inspectable examples. Examples should expose inputs, operations, results, failure paths, and relevant operational consequences.
Separate fact from judgment. Standards, language behavior, and protocol rules are distinguished from design recommendations and tradeoffs.
Prefer primary sources. Version-sensitive technical claims should be checked against official specifications, language documentation, or original project documentation.
Keep titles truthful. Every Academy entry must map to one distinct tutorial whose contents match the displayed title.
Revise when evidence changes. Tutorials are updated when platforms, stable language behavior, security guidance, or supported tools materially change.

Course structure

Each tutorial is organized as a technical book. Its table of contents links to chapter overviews, concepts and key ideas, examples and walkthroughs, and common pitfalls. Language tutorials progress from setup and core semantics through libraries, testing, concurrency, performance, security, delivery, and a final integrated system. Engineering tutorials connect architecture to reliability, recovery, and operational evidence.

Automated quality checks

The site checks every published course route for unique mapping, required fields, substantive explanation and walkthrough length, usable examples, multiple common pitfalls, and truthful chapter counts. Automation prevents obvious regressions; it does not replace technical review.

Sources, software assistance, and originality

Version-sensitive claims should be checked against primary specifications, official documentation, standards, or original research where a lesson names them. Sources establish factual boundaries; copied documentation, translated source text, embedded material, or a list of links is not treated as an original lesson.

Software assistance and automated checks may support drafting, formatting, cross-link validation, count verification, and regression testing. Automation does not establish truth or expertise. Published material must still present a coherent teaching route, distinguish evidence from recommendation, and remain open to revision.

Copyright and third-party material

Unless a page identifies another source or license, NAPOH’s lesson prose, original examples, exercises, diagrams, and interface text are NAPOH material, © 2026. Links, citations, software names, and factual references do not transfer ownership of the linked works or third-party marks. Openly licensed or public-domain material is identified with its source and applicable terms; those terms control that material.

Vocabulary data, licensing, and reuse

The vocabulary catalog combines NAPOH-written interface text and edited seed entries with openly licensed lexical data. The downloadable four-language dataset, including NAPOH’s selection and arrangement, is offered under the Creative Commons Attribution-ShareAlike 4.0 International License. This license applies to that adapted dataset, not automatically to unrelated NAPOH lessons, branding, or site software. Source projects do not sponsor or endorse NAPOH.

The 11,100-family foundation follows the estimate reported by Brysbaert, Stevens, Mandera, and Keuleers (2016) of roughly 42,000 lemmas derived from 11,100 word families for an average 20-year-old native speaker of American English. The catalog extends that foundation to 14,386 distinct families for advanced academic and literary recognition; this is a catalog-size target, not a claim that every entry is mastered.

Definitions, examples, relations, and localized meanings where present: contributors to English Wiktionary, German Wiktionary, and Japanese Wiktionary, under CC BY-SA 4.0, using machine-readable extracts produced by Kaikki.org.
Aligned examples and Japanese and German meanings: Open English WordNet 2020 under CC BY 4.0; WordNet 3.0, copyright © 2006 Princeton University; Japanese WordNet, copyright © 2009 National Institute of Information and Communications Technology; and OdeNet 1.4 under CC BY-SA 4.0.
Translation-gap assistance: Argos Translate, licensed under MIT and CC0, was run locally only where aligned Japanese or German lexical data was unavailable. These fallbacks do not replace existing human-aligned meanings.
Additional context sentences: only the Tatoeba sentences_CC0 export, which Tatoeba identifies as CC0. The attribution-requiring full Tatoeba sentence collection is not used.

Changes made by NAPOH on 13 August 2026: source strings were Unicode-normalized; unsafe markup and unsuitable examples were rejected; the first concise glosses were selected and length-limited; parts of speech and WordNet concepts were aligned; duplicates were removed; ECDICT inflection metadata was grouped around a headword; sentence examples were matched to exact word forms; and records were ordered into a fixed 14,386-entry study catalog. These changes can omit senses or introduce alignment errors, so the catalog is a study aid rather than an authoritative dictionary.

Excluded data: FreeDict, JMdict/EDICT, third-party dictionary audio, and the attribution-requiring Tatoeba full collection are not included in the current build. Pronunciation buttons call a voice supplied by the reader’s browser or operating system; NAPOH does not distribute those voice recordings.

The data file begins with the applicable MIT, ISC, Princeton WordNet, Japanese WordNet, and CC BY-SA notices so that the notices remain attached when the file is downloaded or copied. Reusers must preserve those notices, credit the named projects, link the CC BY-SA 4.0 license, identify further changes, and apply CC BY-SA 4.0 to adaptations of the share-alike material.

Corrections and revision

Technical material can contain mistakes or become outdated. When a problem is identified, it is checked against the lesson’s stated scope and its dependent explanations, examples, answers, diagrams, and links. A material correction should update every affected part rather than silently patching one sentence out of context.

A useful correction record identifies the exact URL and heading, the questionable statement or behavior, the expected result, the relevant version, and a primary source or reproducible case when available. Rights or attribution concerns additionally identify the affected material, original source or rights record, and requested action. Passwords, private records, API keys, student data, and unrelated personal information should never be included.

Funding

NAPOH is free to learners and is supported by Google AdSense on selected adult-oriented, content-rich pages. Catalog, policy, contact, and English-learning pages do not load the AdSense ad script. Advertising must remain distinct from lessons and navigation and is evaluated against reading quality, accessibility, privacy, and site performance.