Why we are starting OnlyTranslate product updates
OnlyTranslate has always documented releases on GitHub, but a release note usually answers only “what changed.” It rarely has enough room for “why.” Product updates fill that gap and create a clearer bridge between development and real-world use.
What we will publish
Product updates will focus on three kinds of stories:
- Feature guides explain how capabilities such as Smart webpage translation, bilingual video subtitles, and local EPUB reading work—and which problems they are designed to solve.
- Development notes share the decisions, implementation work, and trade-offs behind an experience, including the parts that remain unresolved.
- Major releases add context and migration guidance when a release materially changes how the product is used.
This will not be a feed of every commit, and we will not publish simply to meet a schedule. We will write when a change is worth understanding.
How this differs from release notes
GitHub Releases remains the source for packages, change lists, and release history. Product updates focus on the experience: why a feature exists, what it can currently do, and where it may not work.
If an article ever differs from the extension itself, the current extension, user guide, and public source code take precedence. We will correct the article as well.
Feedback should return to development
Every update offers two feedback paths: send a private note through the website or discuss it publicly on GitHub. We are not hosting public comments on the site for now, so feedback stays in channels that can be maintained and followed through.
These posts should be more than one-way announcements. They should help readers understand what OnlyTranslate is trying to solve and bring real reading scenarios back into the next development cycle.