PRD of WeBuddhist Study Platform

Owning Group WeBuddhist Core Team
Status Draft
GitHub Project WeBuddhist WG · GitHub
Last Updated 2025-09-22

1. Overview

WeBuddhist Study Platform is a comprehensive, open-source web application designed to be a one-stop solution for the study of Buddhist scriptures. Inspired by the interconnected text platform Sefaria.org, WeBuddhist Study Platform provides users with a rich, multi-layered library of Buddhist canonical texts, translations, and commentaries.

It solves a critical problem for Buddhist scholars, monastics, dedicated practitioners, and students: the fragmentation of resources. Currently, students must navigate multiple websites or books of varying quality for original texts, translations, dictionaries, and scholarly materials. There is no single, integrated environment that links these resources at a granular level or provides tools for personal study and insight sharing. WeBuddhist Study Platform addresses this by creating an interconnected digital library with built-in tools for deep reading, annotation, and content creation.


2. Goals & Success Metrics

The primary goal of WeBuddhist is to become the definitive platform for deep, interconnected study of Buddhist texts online.

Goal Key Performance Indicators (KPIs) & Success Metrics
1. Create a Rich, Centralized Library - Content Growth: Increase the number of texts in the library by 20% per quarter. - Breadth of Collection: Successfully onboard at least one major text from each of the three main Buddhist traditions (Theravāda, Mahāyāna, Vajrayāna) within the first year.
2. Foster Deep User Engagement - Monthly Active Users (MAU): Achieve 1,000 MAU within 6 months of public launch. - Average Session Duration: Target an average session duration of over 15 minutes. - User Retention: Achieve a 30-day user retention rate of 15%.
3. Empower User-Generated Insights - “Story” Creation Rate: At least 10% of active users create one or more “Stories” within their first month. - Public Sharing: 20% of all created “Stories” are made public, indicating community contribution.
4. Build a Sustainable Open Source Project - Community Contributors: Onboard 5 external contributors to the codebase or content library on GitHub within the first year. - API Adoption: Have at least one external digital humanities project utilize the WeBuddhist API (post-launch).

3. Timeline & Quarterly Milestones

A high-level schedule for the project, updated to reflect progress as of Q3 2025.

  • Q1 2025: Foundation & Design

    • [x] Finalized core data schema for all platform features.

    • [x] Created and approved complete Figma mockups for the web application.

  • Q2 2025: Core Functionality - Users & Library

    • [x] Implemented user authentication (backend and frontend).

    • [x] Integrated social login (e.g., Google, Apple).

    • [x] Developed the Library interface and backend architecture.

  • Q3 2025: Content Creation & Initial Testing

    • [x] Implemented the “Story” feature (backend and frontend).

    • [x] Successfully uploaded the Bodhicharyāvatāra as the first live test text.

    • [x] Conducted internal testing of the end-to-end user flow.

  • Q4 2025: Feature Enrichment & Alpha Testing

    • [ ] Integrate the dictionary lookup on keywords.

    • [ ] Expand the library with 10 additional core texts (e.g., the Dhammapada, key suttas).

    • [ ] Refine UI/UX based on feedback from the Bodhicharyāvatāra implementation.

    • [ ] Begin closed alpha testing with a select group of scholars and practitioners.

  • Target Launch (Public Beta): Q1 2026


4. Scope & Features

IN SCOPE (For Public Beta Launch)

  • Text Study Interface:

    • Side-by-side and top/bottom views for original texts and their translations.

    • Clickable text segments (verse, paragraph) that are permalinkable.

    • A resource panel showing linked commentaries for a selected segment.

  • Library:

    • Initial focus on the Pāli Canon (Theravāda), with a selection of foundational Mahāyāna sūtras.

    • Clear sourcing information for all texts and translations.

  • Dictionary Lookup:

    • On-hover or on-click pop-up dictionary for Pāli and Sanskrit terms.

    • Provides concise definitions and grammatical information.

  • “Story” Feature:

    • A simple, robust editor for users to create sheets of content.

    • Ability to easily add scripture segments from the library into a “Story.”

    • Users can add their own prose, headers, and basic formatting.

    • Ability to save “Stories” as private or share them via a public link.

  • User Accounts:

    • Basic user registration and profile to save “Stories” and user preferences.

OUT OF SCOPE (For Future Releases)

  • Advanced social features (e.g., commenting on public “Stories,” discussion forums).

  • Real-time collaborative editing of “Stories.”

  • User-submitted translations or commentaries.

  • Extensive support for Tibetan, Chinese, or Pali canons beyond a few representative texts.


5. Dependencies

  • Content & Data Partners:.

    • Buddhist Digital Resource Center (BDRC): Potential partner for sourcing scanned texts and metadata.
  • Technical Dependencies:

    • Pecha AI studio WG: depend on their open-source tools

    • Pecha Server and API WG: depend on standards for formatting and parsing Tibetan e-texts.

    • Wiktionary and Other opensource Dictionary APIs: Dependency on external APIs for the dictionary lookup feature.


6. Acceptance Criteria

The project will be considered “done” for the Public Beta launch when a new user can successfully complete the following user flow without critical bugs:

  1. A user can successfully create an account and log in.

  2. The user can navigate the library and open the Dhammapada.

  3. The user can view the Tibetan text alongside an English translation.

  4. The user can click on a Tibetan word and see its English definition in a pop-up.

  5. The user can select three different verses and add them to a new “Story.”

  6. In the “Story” editor, the user can write at least two paragraphs of their own commentary.

  7. The user can save the “Story” to their private account.

  8. The user can then change the “Story’s” status to public and share the generated URL with another person, who can view the content without being logged in.