RAG ReleaseDigital Publishing Capstone
- Period
- Sep 2024 - Sep 2025
- Project type
- Individual Academic Project
- Role
- Full-Stack Developer & Project Owner (Individual)
- Team
- Solo academic project
A digital-publishing capstone that prototypes a role-oriented manuscript workspace and authentication foundation while documenting a broader marketplace architecture that remains partially implemented.
- Publishing interface foundation
- 28Frontend routesPublishing interface foundation
- Frontend, auth, and book service
- 3RepositoriesFrontend, auth, and book service
- Requirements and architecture
- 80SRS pagesRequirements and architecture
Overview
RAG Release explores a role-oriented digital publishing workflow for authors, reviewers, designers, publication staff, and readers. The audited implementation includes a 28-route Next.js interface and collaborative-editor foundation, plus a working authentication and account-upgrade service. The book service remains a partial controller and code skeleton, so unmounted domain routes are not represented as completed delivery.
Role & context
- Role
- Full-Stack Developer & Project Owner
- Team
- Solo academic project
- Type
- Individual Academic Project3rd year project
- Period
- Sep 2024 - Sep 2025
An individual Level 3 capstone supported by proposal, SRS, and three repositories whose observed commits are attributable to my aliases. I owned the requirements, architecture, frontend, authentication service, and initial book-service work. This case study separates the implemented prototype from the larger publishing, marketplace, storage, and deployment design described in the SRS.
Problem
Authors often combine disconnected tools for drafting, editorial review, design, ISBN handling, publication, and sales. The project investigates a unified workflow while using a staged implementation to validate identity, role-oriented workspaces, and the manuscript experience first.
Approach & architecture
The implemented frontend and authentication service form the prototype core; the book-service and external platform integrations remain partial or planned.
Practices followed
Maintained a formal proposal and SRS alongside implementation evidence
Separated frontend, authentication, and book domains into independently versioned repositories
Implemented access and refresh token flows with account and payment-record foundations
Kept planned architecture visibly separate from source-verified product behavior
Challenges & resolutions
The product vision was much broader than one capstone implementation window.
FixPrioritized the publishing workspace and authentication foundation while recording the larger architecture and incomplete book-service scope explicitly.
Real-time manuscript editing needs conflict handling without a single writer overwriting another.
FixEstablished a TipTap and Yjs collaborative-editor foundation in the frontend prototype.
Outcomes
Built a 28-route Next.js publishing interface and collaborative-editor foundation
Organized the prototype across 3 repositories and implemented a functioning authentication and account-upgrade service with Sequelize models and migrations
Produced a proposal and 80-page SRS covering stakeholders, requirements, external systems, quality targets, and planned architecture
Started the book-service boundary and controller skeleton without presenting unmounted domain routes as complete
Tech stack
Concepts & skills8
- Requirements engineering
- Role-oriented product architecture
- Next.js workspace design
- JWT access and refresh flows
- Sequelize migrations
- Collaborative editor foundations
- Polyrepo service boundaries
- Implementation-scope governance
Links
Expertise demonstrated here
- Full-stack developmentIfham Mohamed builds production web applications across React interfaces, typed APIs, authentication, databases, testing, and deployment.
- React engineeringReact engineering by Ifham Mohamed across design systems, typed state, role-based workflows, testing, performance, and web and mobile products.