Arabic books and authors platform Client project

Arabookly: a book discovery platform for Arabic readers

Arabookly is a client project built to help Arabic readers find books and authors, explore a growing catalogue, and keep track of what they want to read. The custom WordPress platform connects discovery with reader and author workflows instead of treating books as ordinary blog posts.

Project goal

Create one Arabic-first place where readers can discover books and authors and organise their reading, while the client team can grow the catalogue with structure.

Visit the live website Review the related service

People and decisions

How visitors move through this project

A useful case study starts with the people, the decision they need to make, and the information that helps them take the next step.

The visitor journey

  1. A reader searches by title, author, or category to find relevant books.
  2. They open a book or author page to review details and explore related records.
  3. Readers organise books by reading status, while authors submit work for editorial review.

Who this example is for

  • Arabic book catalogues and content directories.
  • Platforms that need custom content types and connected records.
  • Projects that want WordPress with application-like reader workflows.

The challenge

What the website needed to solve

A book catalogue needs more structure than a standard article archive. Each title has bibliographic details, authors, genres, formats, and related works. Readers need useful search and ways to organize their lists, while authors and editors need a controlled route for submitting and reviewing content. These paths had to work in a clear Arabic RTL experience on mobile.

The solution

How the delivery was structured

The WordPress build models books and authors as separate content types, with taxonomies and custom fields for catalogue details and relationships. Search and archive templates support discovery across the collection. Front-end reader and author areas handle reading lists, ratings, following, and content submissions. Digital titles use controlled download links, and an Arabic assistant can answer from catalogue data.

Implementation

Core parts of the project

Structured books and author catalogue

  • Separate WordPress content types for books and authors
  • Catalogue fields for ISBN, publisher, language, publication date, and page count
  • Genres, series, tags, and author-country classifications
  • Connected book, author, category, and archive pages

Arabic book discovery

  • Search across books and authors
  • Featured, recent, and popular titles alongside notable authors
  • Archive filters for genre, format, and sort order
  • Arabic RTL layouts designed for mobile browsing

Reader and author workflows

  • Reading lists for want to read, currently reading, and finished books
  • Reader ratings and author following
  • Front-end reader profiles and download history
  • Author submissions routed for editorial review

Controlled publishing and delivery

  • Time-limited links for available PDF, EPUB, and MOBI files
  • Download validation, rate limits, and event logging
  • Import tools that record source and image details
  • Arabic book assistant grounded in the catalogue data
WordPressPHP 8MySQLCustom Post TypesCustom TaxonomiesVanilla JavaScriptArabic RTL

Architecture and trade-offs

Why the project took this approach

Key implementation decisions

  • Model books and authors as separate WordPress content types and connect them through fields and taxonomies.
  • Make search, category archives, and related-content links central to discovery.
  • Keep reader and author actions in purpose-built front-end workflows and hold submissions for editorial review.
  • Deliver available digital titles through controlled links with validation and download records.

Constraints to account for

  • A title, its author, genre, format, and related books are connected records, not interchangeable blog posts.
  • Readers need fast mobile discovery while book pages retain useful catalogue details.
  • Editors need a content model that can grow without weakening publishing control.

Delivery ownership

Responsibilities and ownership after delivery

  • Plan the content model for books, authors, categories, and catalogue details.
  • Build the custom WordPress structure and Arabic right-to-left interface.
  • Connect search, archives, reading tools, submissions, and controlled file delivery.
  • Prepare a clear handover so the client can manage the live platform and content.
  • The live project is published at arabookly.com.
  • The domain, hosting, WordPress administration, and reader data remain under the client's management.
  • Digital book availability follows the platform's policies and the rights attached to each title.

Planning a similar platform

What to prepare before a similar build

  • A list of content types and how books, authors, genres, and formats relate.
  • The details readers need on each record, such as publisher, language, ISBN, or publication date.
  • The search, filters, reader actions, and submission flow required for the first release.
  • A publishing plan for editorial review, catalogue imports, file rights, and ongoing updates.

Key lessons

Lessons from this delivery

  • Define relationships between content types before designing catalogue screens.
  • WordPress can support a specialised platform when it is treated as a content system, not just a blog.
  • Discovery and related titles are core journeys for a books platform, not secondary archive features.

The published platform at arabookly.com is the client project discussed here; digital file availability remains subject to the platform's policies and title rights.

Delivered outcome

What changed through the project

  • Books, authors, and categories organized as linked catalogue data
  • Reader discovery connected to search, ratings, following, and reading lists
  • A review path for author submissions that keeps publishing under editorial control
  • An Arabic mobile experience supported by a maintainable WordPress content model

Handover scope

Project deliverables

  • Custom WordPress theme and book-platform templates
  • Book and author content types, fields, and taxonomies
  • Search, archive filters, and related-content paths
  • Reader and author front-end workflows
  • Controlled digital-file delivery and download logging
  • Arabic RTL interface and catalogue assistant

Related delivery evidence

Use the closest example to compare the customer journey, platform, and handover scope.

Related service Review the service scope

Compare deliverables, process, project inputs, and the next step for a similar build.

 النسخة العربية اقرأ دراسة الحالة بالعربية

نفس المشروع والمحتوى في صفحة عربية كاملة باتجاه RTL.

Related scope

Planning a project with similar requirements?

Share the goal, content, languages, integrations, timeline, and ownership requirements for a specific recommendation.

Send the project briefRead the Arabic case study
WhatsApp