Fanar: Admin Panel layout (content ops focus)

Objective: Content Ops Admin Layout · Quarter: Q2 1448 · Size: M · Priority: High Roadmap: Fanar 1448 Q1 & Q2 Roadmap

Context

The current admin layout lacks a dedicated content ops focus, making navigation between Recitations, Datasets, Audio Slicing, and Verification pipelines disjointed.

Why

Streamlines administrative operations by restructuring the sidebar navigation, layout headers, and content workspace containers.

Acceptance criteria

• New Content Ops layout hierarchy with collapsable sidebar navigation.
• Preserves existing Fanar asset gallery while adding dedicated operational routes.
• Responsive navigation supporting desktop, tablet, and mobile viewports.
• i18n support (Arabic RTL / English LTR).

🛠️ Implementation & Technical Guidance

Target File Paths

• cms-frontend/src/app/features/admin/layout/
  • admin-layout.component.ts
  • admin-sidebar.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.