Reading and Writing Books

Project Description:
This website aims to offer readers and writers seamless access to a vibrant online book community where they can engage in reading and writing, connect with fellow book lovers, and share ideas. Users will first identify themselves as either "Readers" or "Writers," each with distinct interfaces and functionalities. Readers can add books to their personal library, participate in book discussions, categorize their collections, and manage their books by editing or deleting entries. Writers, on the other hand, can publish their works, interact with readers through comments on their books, organize book events, and manage their published content by uploading, editing, or deleting their books.

Requirements

User Types and CRUD Operations

1. The website will have separate functionalities for writers and readers.
2. Each user will be able to do CRUD operations
   

Writer Permissions:

• Create, edit, and delete their own books and content. • Respond to comments on their books. • Organize and manage book events and challenges. • Access analytics related to their own books (e.g., views, comments).

Access Controls:

• Writers can only manage their own content and events. • They cannot access or modify other users' content or data.

Reader Permissions:

• Browse and read books available on the platform. • Add books to their personal library. • Write, edit, and delete their own comments on books. • Participate in discussions and book events. • Customize Access Controls: their profile and manage • Readers can only modify their own profile and content. • They cannot publish Implementation of Access Controls

1. Role-Based Access Control (RBAC) books or their managed personal site-wide library. events. • Implement a role-based access control system to assign roles to users upon registration.
   

• Define permissions for each role within the system, ensuring that only users with the appropriate role can access specific features.

3. User Interface Customization
   • Customize the user interface based on the user's role. For example, writers should see options for publishing and managing their books, while readers will see book selection, book clubs, and events.

5. Permissions Checks
• Implement permissions checks in your codebase to verify that users have the appropriate permissions before allowing them to perform actions like creating, editing, or deleting content.

User Interface and Page Responsiveness

1. The website will be user-friendly, designed according to the target audience's preferences and interests, and also engaging and fun to use.
2. The website will utilize Bootstrap to create an engaging and visually appealing user interface. Notifications and Alerts
3. The application will send reminder notifications or alerts for events, book challenges, and activities.
   

About Us Functinalities

1. Include a system for user support, such as a help center or FAQ section.
2. Provide a way for users to give feedback on the platform and suggest improvements

Home Page:

Untitled.video.-.Made.with.Clipchamp.1.mp4

About Us Page:

Untitled.video.-.Made.with.Clipchamp.2.mp4

Sign In Page:

short demo:

Untitled.video.-.Made.with.Clipchamp.6.mp4

Sign Up Page:

short demo:

Untitled.video.-.Made.with.Clipchamp.3.mp4

Writer side: Create and Delete Book demo:

Untitled.video.-.Made.with.Clipchamp.7.mp4

Reader Side home page and profile:

Untitled.video.-.Made.with.Clipchamp.10.mp4