Research: wiki-style content model and tagging for moderation #38

New Issue

anas · 2026-10-08T20:54:24Z

anas commented

2026-10-08 20:54:24 +00:00

Owner direction (2026-10-08): content moderation should work like a wiki, with tags and data points that say what a couplet is, what a complete chapter is, what a word is; evaluate integrating an open-source wiki moderation module.

Questions

Markup and tags: how a work is structured (book, chapter/section, poem, stanza, couplet, misra/line, paragraph, word) and annotated (radif, qafiya, takhallus, footnotes, word → dictionary links, variants between editions).
Options to compare:
1. MediaWiki (the Wikisource/Wiktionary engine) with ProofreadPage, <poem> and templates; Semantic MediaWiki or Wikibase for data points. Full wiki (talk pages, history, diffs), but PHP, its own accounts and permissions, separate from Divan's IAM, pipeline and git publishing.
2. Wiki.js or similar (Node, Markdown/git-backed): lighter, git storage, but no poetry structure.
3. Divan's own editor with a standard text model: TEI (Text Encoding Initiative), the standard for tagging literary texts: <lg> line groups (couplets, stanzas), <l> lines, <div type="chapter">, <w> words, <note>; or a wikitext subset compatible with Wikisource so content round-trips with the source.
Fit with what is planned: IAM grants (#29), the L2 → L1 → admin pipeline (#31), git publishing to divan-data (#34), the Urdu editor (#28).
Effect on divan-data's format and the site's rendering (radif/matla/maqta already computed).

Outcome: a recommendation with a small prototype on one ghazal and one prose chapter, before the content editors (#32) are built.

Owner direction (2026-10-08): content moderation should work like a wiki, with tags and data points that say what a couplet is, what a complete chapter is, what a word is; evaluate integrating an open-source wiki moderation module. Questions - Markup and tags: how a work is structured (book, chapter/section, poem, stanza, couplet, misra/line, paragraph, word) and annotated (radif, qafiya, takhallus, footnotes, word → dictionary links, variants between editions). - Options to compare: 1. **MediaWiki** (the Wikisource/Wiktionary engine) with ProofreadPage, `<poem>` and templates; Semantic MediaWiki or Wikibase for data points. Full wiki (talk pages, history, diffs), but PHP, its own accounts and permissions, separate from Divan's IAM, pipeline and git publishing. 2. **Wiki.js** or similar (Node, Markdown/git-backed): lighter, git storage, but no poetry structure. 3. **Divan's own editor with a standard text model**: TEI (Text Encoding Initiative), the standard for tagging literary texts: `<lg>` line groups (couplets, stanzas), `<l>` lines, `<div type="chapter">`, `<w>` words, `<note>`; or a wikitext subset compatible with Wikisource so content round-trips with the source. - Fit with what is planned: IAM grants (#29), the L2 → L1 → admin pipeline (#31), git publishing to divan-data (#34), the Urdu editor (#28). - Effect on divan-data's format and the site's rendering (radif/matla/maqta already computed). Outcome: a recommendation with a small prototype on one ghazal and one prose chapter, before the content editors (#32) are built.

anas added this to the Phase 4: Content moderation (Divan's own copy) milestone 2026-10-08 20:54:24 +00:00

anas referenced this issue from a commit

2026-10-08 22:06:09 +00:00

Research: content model and moderation (#38): no wiki engine embedded; Divan text format prototype

anas referenced a pull request that will close this issue

2026-10-08 22:07:55 +00:00

Research: content model and moderation (no wiki engine embedded; Divan text format) #49

anas closed this issue

2026-10-08 22:16:18 +00:00

Sign in to join this conversation.