尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Code repository for plithos.org
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Source for plithos.org - a free Orthodox Christian
companion: the liturgical calendar, the daily saints and feasts, the fasting
rule, traditional prayers, the writings of the Holy Fathers, and Holy
Scripture, in twenty-two languages.
Hosted on Cloudflare Pages. There is no build step: what is in this repository
is what is served.檢視完整 README ↗Source for plithos.org - a free Orthodox Christian companion: the liturgical calendar, the daily saints and feasts, the fasting rule, traditional prayers, the writings of the Holy Fathers, and Holy Scripture, in twenty-two languages.
Hosted on Cloudflare Pages. There is no build step: what is in this repository is what is served.
index.html Calendar, feasts, fasting rule, search
saints.html Saints index, 1,456 saints
library.html The Library: patristic works and the scripture reader
prayers.html The prayer book, 100 prayers
rule.html The fasting rule
glossary.html Terms
contact.html Contact
embed.html The calendar panel, for embedding elsewhere
data/ Datasets fetched for the one language a reader chose
scripture/ Old Testament by language and book, 21 languages
assets/ The only shared CSS and JS on the site
functions/ Cloudflare Functions: per-language routes and /api/day
app/ Capacitor wrapper that ships the site as an Android app
tools/ Builders, checkers, and the translation source modules
docs/ Editorial authority per language, and the defect list
CLAUDE.md Architecture and the rules that bind anyone editing
tools/ and docs/ are not served; .assetsignore keeps them out of the
upload. They are, however, the source of truth for everything under data/:
the twenty-one language modules in tools/saint_lives/, tools/saint_info/,
tools/saint_terms/ and tools/ui_i18n/ are what the published bundles are
built from, and deleting them would leave the site unmaintainable.
| Path | Serves |
|---|---|
/ /calendar | index.html |
/saints | saints.html |
/library /reader | library.html |
/prayers /rule /glossary | their own pages |
/<lang>/... | the same pages, language pinned, via functions/ |
/api/day | the day's calendar as JSON |
Every one of the four tracks is now complete in all twenty-one translated languages: the vocabulary a life is built from, the interface, the 1,456 saints' lives, and the 1,456 calendar entries that the day panel shows.
| Languages | 22 served, 21 of them translations of the English base |
| Translated items | 274,963 |
| Characters | 58.8 million, roughly 9.8 million words |
| Saints | 1,456, each with a long life and a sixty-word calendar entry |
Greek, Russian, Romanian, Ukrainian, German, Spanish, Arabic, French, Portuguese, Italian, Serbian, Georgian, Chinese, Japanese, Korean, Swahili, Armenian, Syriac, Hindi, Bengali and Urdu.
Roughly three weeks, from the third week of August to 11 September 2026.
The work was run by several agent sessions writing in parallel against a shared branch. A small queue held the four tracks in dependency order - vocabulary first, because the grammar of a life is drawn from it, then the interface and the lives, and the calendar entries only once a language's lives were complete. Each worker asked the queue what was unwritten, took a claim so that two would not write the same saint, wrote a batch by hand, and pushed. A language large enough to be worth it was worked from both ends at once by two workers walking towards each other.
That machinery has been deleted. The queue, the claims file, the batch
driver and the standing orders that drove them are gone, because a repository
that still contains instructions to "take the next job" will eventually
persuade something to start translating a language that is already finished.
What remains of it is the part worth keeping: the editorial decisions, in
docs/<LANGUAGE>.md, and the checkers in tools/.
Each language was settled before it was written. The register - whether a
saint takes the bare word for holy or the rank his order gives him, how a
place is spelled, how a sentence ends - was decided from what the site already
published and written into that language's doc, so it was decided once.
tools/check_register.py enforces the part of it a script can see.
The corpus is complete and structurally sound: every key present, every rendering in the right script, no placeholders, no English left standing, and the published bundles agree with their sources.
It is not verified for accuracy or for veracity. Nobody has read most of it
in the language it is written in. The known faults, and an honest account of
what a real review would cost, are in
docs/BASELINE.md under the open defects of 11 September
2026. The largest of them are worth naming here: thirty Hindi lives quote
Scripture in the site's house spelling rather than the edition's, a run of
Arabic place names sits one key out of step, and thirty-two lives across
Syriac, Portuguese and Italian are materially shorter than their source.
Nothing below is started. It is the shape of the work as it stands today.
check_translations.py reports some eleven thousand findings of which the
great majority are locale artefacts - a full stop as a thousands separator
in Portuguese and Romanian, ordinals as digits in Russian, Chinese counted
short because Chinese is compact. A checker nobody trusts is why 7,622
finished calendar entries sat unpublished for days without anything going
red. Fixing its rules is a day and is the highest-value day available.app/ holds a Capacitor wrapper that ships the site
itself as an Android app. It has never been built, signed or submitted, and
there is no iOS target.CLAUDE.md decides every edition question and is not negotiable: the
edition carrying the books the Church reads wins.python3 -m http.server 8000 # then open http://localhost:8000
_headers, _redirects and functions/ are Cloudflare directives and do
nothing locally, so extensionless routes such as /saints and the per-language
routes only work in production.
Human or otherwise. CLAUDE.md is the canonical guide: the
architecture, and the editorial, translation, source, cache, publication and
validation rules. It is longer than this file and it is the one that binds.
docs/<LANGUAGE>.md is the authority for a language and is read before
a word of that language is written or changed.
There is no queue, and no work is waiting. The translation finished on
11 September 2026 and the machinery that ran it has been deleted. If you find
an instruction anywhere in this repository telling you to take a slot, ask for
a job, or work a language through to a total, it is a leftover and it is wrong:
check what the site actually publishes before acting on it. What remains is
repair and improvement, and it is listed in
docs/BASELINE.md.
Four things bite immediately.
The HTML files embed their remaining datasets as single enormous lines. Do
not open one whole; locate the assignment, slice it, parse it, work on the
object and write the line back. NAMES_I18N in index.html will mislead you
in particular: it opens as a small multi-line object and is then filled by
about fifteen hundred separate assignments spread through the file, so reading
only the opening gives you a table that looks complete and is not.
Most of /data is cached immutable for one year. Changing a file there
without bumping the version in its filename will not reach returning visitors,
and a new version needs a new rule in _headers as well as a new name. The
exceptions are declared in _headers; read it rather than assuming either way.
Never invent, paraphrase, modernise or silently correct liturgical text, Scripture, or a saint's life, date, jurisdiction or relics. If something looks wrong, say so and leave it. That rule is the reason the site is worth publishing, and it is not negotiable for a deadline.
Do not escalate an editorial question about a language. The owner does not
read most of the twenty-two and cannot adjudicate whether a Syriac rank word
is right; asking stops the work and returns nothing. Settle it the way every
finished language was settled - from what this site already publishes, counting
the competing forms rather than choosing by ear - write the decision into
docs/<LANGUAGE>.md so it is made once, and carry on. Deletion is the
exception: ask about that.
Two house rules a script enforces and you should not fight: hyphens rather
than dashes and straight rather than typographic quotes, in every language
without exception; and nothing in tools/, docs/ or this file is served to a
reader, so no served file may mention a script, a build or a pipeline.