Study Notes

These notes provide original explanations for how Maqor presents source texts and supporting data. They are intentionally written as crawlable public content, not hidden inside the interactive app.

How to use these notes

The notes are not meant to replace the interactive app. They explain what the app is doing so that users can judge the output more carefully. A reader who sees a compact morphology code in the app should be able to return here and understand why the code is compact, what the popup expands, and why the original word remains the primary evidence.

These articles are also part of the site's public content layer. They give search engines, reviewers, and new users a way to understand Maqor without running the JavaScript application. That matters for accessibility, indexing, and AdSense review, but it also matters for users who want a stable explanation they can cite or share.

Planned note categories

Future notes can cover source texts, morphology conventions, IPA rule changes, individual passage walkthroughs, translation alignment issues, and corrections to generated data. When the future forum-style layer is added, these notes should provide the stable methodological background that keeps discussion grounded in the source text rather than only in opinion.

Why notes are public

Keeping the notes public serves two purposes. First, it helps users understand the tool before they rely on it. Second, it makes the project easier to evaluate from outside the app. Search engines, reviewers, teachers, and potential contributors can read the reasoning without creating an account or loading the interactive interface. That is important for transparency and for long-term trust.

How notes should grow

Each future note should answer a concrete question. For example: why does a Hebrew word keep its prefix attached, why does a Greek diphthong receive a certain IPA value, why does a Syriac transliteration map one letter differently from another, or why does a translation line fail to match English word order exactly. Notes should remain tied to examples rather than becoming generic essays.

What makes a useful note

A useful note should identify the passage or language feature, explain the problem in plain language, show why the issue matters, and connect the explanation back to the interactive app. For example, a note about Hebrew prefixes should not only define a prefix. It should explain why the prefix remains attached in the source word, how the popup can expand the prefix data, and why a translation may represent that prefix with a separate English word.

This format is also important for future discussion features. If Maqor later hosts academic, interdenominational, institutional, public-domain, and lay-reader comments, the study notes can act as stable reference material. A user debate about a verse should be able to point to a note that explains the underlying method before the discussion moves into interpretation.

Editorial expectations

Study notes should be specific, source-aware, and modest in their claims. They should not pretend that a compact interlinear field settles every translation question. They should help readers see the difference between a textual observation, a grammatical description, a lexical suggestion, and an interpretive conclusion.