Skip to content

Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy

BookReading live preview
All projects

BookReading

Read translated web novels with names and terms kept consistent across chapters.

Machine-translated fan novels spelled the same names and terms differently across chapters, and lacked basic reading-app features.

Tech Domain · Book Dev|Published|Evidence: Prototype|Next.js, TypeScript, Go, Python, FastAPI, PostgreSQL, Docker

A public prototype demonstrates the interaction; scope and data are intentionally limited.

Case Study

Before

Machine-translated web novels and manga had inconsistent terminology between chapters and no reading progress, bookmarks or library.

After

The code covers scraping, translation, a novel and manga reader, progress, bookmarks and offline reading; the frontend tests pass, the full stack needs real infrastructure and API keys.

How it's solved

Built a Next.js reader with a Go backend (PostgreSQL, JWT auth, rate limiting) and a Python FastAPI service that scrapes source chapters and translates them with OpenAI/Gemini, using glossaries for consistent terms and a review queue.

Trade-offs

The full stack has not been verified end to end in production.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev