Itqan-community/cms-frontend

Fanar: Surah → Ayah → Word hierarchy manager (drill-down/tree)

Open

#214 opened on Aug 5, 2026

 (0 comments) (0 reactions) (0 assignees)TypeScript (22 forks)auto 404
FeatureFrontendHelp Wantedhardhigh-priorityroadmap: 1448

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Objective: Mushaf Data Hierarchy Manager · Quarter: Q2 1448 · Size: L · Priority: High Roadmap: Fanar 1448 Q1 & Q2 Roadmap

Context

Managing dataset entities requires a visual tree and drill-down interface to navigate from Surah down to Ayah, Word, and Letter levels.

Why

Provides an intuitive hierarchical inspection surface for Quranic datasets, allowing maintainers to search and verify word-level segments and timing offsets.

Acceptance criteria

  • Tree/drill-down UI with search input and breadcrumb navigation path.
  • Supports lazy loading for large datasets (114 Surahs, 6236 Ayahs, word tokens).
  • Keyboard navigation support (ArrowUp, ArrowDown, Enter, Escape).
  • Integrated with backend hierarchy endpoints (/api/v1/hierarchy/).

🛠️ Implementation & Technical Guidance

Target File Paths

  • cms-frontend/src/app/features/admin/hierarchy/
    • hierarchy-manager.component.ts
    • hierarchy-tree-node.component.ts

🤝 Before you pick this up

Fanar is an open-source, community-maintained project. For it to outlive any one of us, the people contributing need to genuinely understand how it works internally — that understanding is the thing we're actually building.

We all have AI subscriptions. Using AI to help you work is fine and expected. But if you copy this issue into an agent, paste back whatever it produces, and open a PR you haven't read, you're taking more from this project than you're giving it. Reviewing code that its own author never read or ran costs the maintainers more than writing it would have.

So before you open a PR, please make sure you:

  • understand the code you're submitting, well enough to explain why it works
  • ran it on your own machine and saw it behave correctly
  • tested it — including the cases you expect to fail

If you're not planning to do that on this one, please leave it for someone who will. And if you're stuck partway, say so in the comments — a half-finished PR you understand is far more welcome than a complete one you don't.

Contributor guide