Surahs in this vault
Arabic–English surah files live under Graphe/Quran/Surahs/ (one .md per surah); see Surahs folder note for how that directory relates to Ayah and Juz notes. Each ayah block includes an audio link pointing at OpenFurqan — a free Quran reader and study web app (OpenFurqan) where you can read by surah, juz, or page, use study mode, and keep daily plans, bookmarks, and notes tied to specific ayat. The links here use OpenFurqan’s URL pattern (surah + ayah) so you can jump from a verse in Obsidian straight to the same passage for listening or deeper study.
Ayah and Juz layers
- Ayah index — one stub per verse (
Ayah SSS-AAA.md) with tags and![[…#ayah-n|Ayah n]]transclusion from the surah file. - Juz index — thirty parts (
Juz 01–Juz 30) that![[embed]]those ayah notes in mushaf order, plus navigation and short reading glosses. Boundaries come from the Quran.com API (verse_mapping).
Text and translation in the .md files are produced with .dev/scripts/fetch_quran.py from the Quran.com API; OpenFurqan is the audio / reader front-end referenced in those exports, not the API source for the Arabic and English text.
How the chapters are organized
Order in the mushaf (this vault’s default)
The Quran has 114 surahs (chapters). Their canonical order is the compilation order of the written mushaf — not the order in which verses were revealed. Shorter surahs from the end of the book often belong to earlier periods of revelation; long Medinan surahs such as Al-Baqarah sit near the front. That is why “chapter number” is a liturgical and reference order, while “Meccan” vs “Medinan” describes setting of revelation (roughly: before vs after the migration to Medina). Overviews: Meccan surah, Medinan surah.
Literary structures (macro)
Beyond “what it says,” readers and scholars often track how a surah is built: ring or mirroring layout, sajʿ (rhymed prose), parallelism, recurring roots, oaths as section markers, and surah-level unity from opening to closure. Summary with external references: Literary structures overview.
Subdivisions used for reading and memorization
| Division | Role |
|---|---|
| Surah | Named chapter; variable length (from a few ayat to hundreds). |
| Ayah | Smallest numbered unit of revelation in the mushaf. |
| Juzʾ (30 parts) | Roughly equal eighths of the text for monthly reading; each juz spans parts of one or more surahs. Apps like OpenFurqan expose Surah / Juz / Page so you can navigate the same text different ways. |
| Page | Fixed pagination (e.g. Madinah mushaf page numbers) for print and tajwīd layout — independent of surah boundaries. |
So: surah + ayah is the usual semantic address; juz and page are reading and print grids laid over the same text.
Ways to “categorize” surahs or ayat (search & study)
These are the main non-mutually-exclusive lenses people and tools use. None replaces the fixed mushaf order; they help search, curriculum, and tafsīr.
-
Revelation setting (macro) — Meccan vs Medinan surahs (themes often differ: e.g. emphasis on tawḥīd, narrative, and hereafter vs. community, law, and treaty). Scholarly discussion refines boundary cases; Wikipedia’s summaries are a practical entry: Meccan surah, Medinan surah.
-
Structural / opening type (macro) — Some academic typologies group surahs by how they begin (e.g. disjointed letters ḥurūf muqaṭṭaʿa, narrative opener, oath, direct address). That is a literary category, not a different book order.
-
Thematic tags (micro to meso) — Indexes and apps tag topics (e.g. prayer, fasting, prophets, divorce) at ayah or passage level. Those tags are interpretive and vary by database; they complement surah boundaries.
-
Formal genre (legal, narrative, etc.) — Ayat are often read in units of discourse (story, legislation, consolation) inside a surah; cross-reference systems in study apps and mufaṣṣirūn track those rhetorical breaks.
-
Refuge and protection (three surahs) — Al-Ikhlāṣ, Al-Falaq, and An-Nās are frequently grouped as the three qul surahs / refuge chapters (short, devotional use); see also the atlas hub Quran Atlas.
For search: use OpenFurqan’s surah / juz / page modes, your vault’s filenames (Surah NNN - Name.md), and per-ayah headings (### Ayah k). For classification metadata (Meccan/Medinan, juz, page), prefer a dedicated dataset or API if you later automate frontmatter — the English Wikipedia pages above cite standard reference works.
See also
- Literary structures overview — ring composition, sajʿ, parallelism, leitwörter, oaths, surah unity
- Juz — literary overview — ajzāʾ as reading grid vs surah-level rhetoric; ḥizb/maqraʾ; Juz ʿAmma
- RESEARCH — full pipeline plan (fetch → Atlas → Quartz)
- Surahs folder · Ayah index · Juz index
- Books (surahs) in Quran Atlas
- Quran Atlas —
ayah_header_linestooling for large surah files - OpenFurqan — reader, study mode, bookmarks, notes
- Quran.com API — source for fetched Arabic and translation in this vault