26 curated APIs, datasets, fonts, and tools for building trustworthy Islamic products.
26 resources
6 sources
Ground AI agents in verified Quran text, translations, tafsir, search, and morphology through structured tools.
Data comes from Quran Foundation projects; preserve source attribution and never present generated interpretation as sourced scholarship.
Tools for ayahs, surahs, pages, narrations, audio, tajweed, fonts, and mushaf layouts.
The hosted endpoint is api.qurani.ai/gw/mcp; verify reuse terms for each edition, audio file, and font before launch.
Official @quranjs/api client for Quran content and search from Node, Workers, and web applications.
A client_id is always required and client_secret stays server-side. The SDK license does not automatically license every returned content asset.
Verified UTF-8 Quran text in several official text formats for apps and search.
Only verbatim copies are allowed: do not alter the text, and retain the Tanzil attribution, link, and copyright notice.
Word-level morphology, syntax, and treebank data for linguistic search and study tools.
Source attribution, link, and notices are required, and the distributed data file may not be changed under its stated terms.
Generate mushaf page images and glyph bounds for word and ayah highlighting in readers.
The code is GPL, but fonts and pages under res/fonts belong to the King Fahd Complex and require separate rights.
5 sources
A rich search interface across dozens of tafsir, language, rhetoric, and athar works for source discovery and verification.
Use it as a research reference; no public data API or reuse license is stated, so contact Nuqayah before programmatic copying.
Access the manually checked portion of Sunnah.com hadith data, with related open-source projects.
Request a key through GitHub; coverage is partial and expands after manual checks, so confirm data terms before storage or redistribution.
Versioned static JSON across languages and grades that can be pinned or self-hosted.
The repository is Unlicensed, but upstream editions and grading vary; retain source metadata and arrange scholarly review.
Tools to clean, convert, tag, search, and read OpenITI-format Arabic and Islamicate texts.
The library license does not automatically cover every corpus text; inspect edition metadata and licensing per work.
Helps a content owner understand open-license choices and generate a clear, publishable notice.
The tool is not legal advice and grants no rights to third-party content; verify ownership and permissions first.
2 sources
Calculate prayer times, Sunnah night periods, and qibla in browser or server code with TypeScript types.
Let users select calculation method, madhhab, and high-latitude rule, and format in the location timezone rather than device timezone.
Find mosques, prayer rooms, Islamic centres, and accessibility details by location and tags.
Community data may be incomplete; attribute OpenStreetMap, cache responses, and identify your app when using public instances.
3 sources
A mature Arabic Naskh face for long text, books, and Quranic verses, inspired by Bulaq Press.
Suitable for prose and verses but not a substitute for verified mushaf text; test marks, sizing, and line height across devices.
Broad-coverage Naskh and Kufi families for multilingual interfaces and fallback stacks.
The repository contains many families and weights; self-host and subset only what the product needs.
Practical guidance for lang, dir, bdi, dir=auto, and logical CSS properties in mixed-direction content.
Direction is semantic HTML, not merely CSS; test real names, URLs, numbers, and punctuation in mixed content.
4 sources
A testable accessibility baseline covering keyboard use, contrast, reflow, focus, target size, and authentication.
Conformance applies to complete pages and processes and requires human and assistive-technology testing, not automation alone.
Automated accessibility checks in Playwright, browsers, or CI with WCAG 2.2 rules.
It finds about 57% of WCAG issues on average; add manual keyboard, screen-reader, zoom, and Arabic reading-order testing.
Practical guidance for understanding users, defining needs, designing services, measuring success, and running multidisciplinary teams.
Written for UK government services; adapt its principles and controls to the project's community and context.
A tiered set of web-application security requirements that can become concrete pre-launch tasks and tests.
Choose a level proportionate to risk; a checklist does not replace threat modelling or specialist review when needed.
6 sources
Consistent SVG icons with official Astro, React, Vue, Svelte, and Figma packages.
Name meaningful icons, hide decorative ones from assistive tech, and review directional arrows in RTL.
Privacy-focused web and product analytics with events, journeys, dashboards, and self-hosting.
Self-hosting requires PostgreSQL and secure operations; define retention, access controls, and clear user disclosure.
Develop, emulate, and deploy Astro apps on Workers with D1, KV, R2, and local previews.
Pin versions, test against the real Workers runtime, and manage compatibility_date carefully because runtime changes can affect SSR.
Actionable basics for content, links, and metadata so people can discover a product while searching for their need.
Do not promise rankings or traffic; write for users first and measure real reach instead of vanity signals.
Organize issues, tasks, priorities, and status in a board connected directly to the repository and delivery workflow.
Do not create a parallel board without need; give every record one source of truth and an accountable owner.
Guidance for transparent community budgets, expenses, financial contributions, and sponsors through a fiscal host when appropriate.
Availability, fees, and obligations vary by country and host; decide governance and accounting before accepting funds.
Try a broader name or use case.
Submit it to the community library so it can be reviewed before appearing here.