Basic Requirements

[cloudiirain]

Contributors

• [x] A visitor should be able to register for the site as a contributor
• [x] A contributor should be able to log in
• [x] A contributor should be able to add/edit a novel series (novelupdates or mangaupdates fields might be a good reference)
  • [ ] A supervisor should be able to delete a novel series
  • [ ] A supervisor should be able to lock a licensed novel series or specific chapters
  • [ ] A contributor should be able to reorder the list of chapters associated with a series
  • [ ] A complete history (diff) should be kept for all revisions
• [ ] A contributor should be able to add the raw text for a chapter, associated with a series
  • [ ] HTML support?
  • [ ] Support for a references tag, similar to what is on Baka-Tsuki
  • [ ] Support for furigana (ruby tags)
  • [ ] Support for drafts/Works-In-Progress?
  • [ ] Contributor should be able to indicate whether their translation is public, private, or shared with a set of other users
• [ ] A contributor should be able to edit/delete a chapter they have permissions for
  • [ ] A complete history (diff) should be kept for all revisions
  • [ ] Changes by another user should notify the original author

Web Visitors

• [ ] A visitor should be able to search (with suggestions) for a novel title
• [x] A visitor should be able to view detail pages for series
• [x] A visitor should be able read translations (if applicable)
  • [ ] User-defined styles (e.g. black/white background, font-size, etc)

Mobile Visitors

• [x] API endpoint to allow mobile applications GET access to anything relevant
• [ ] Allow bulk downloads of entire series for offline reading

Administrators

• [ ] Moderate users, manage permissions
• [ ] Moderation queue
• [ ] Recent changes page (similar to Baka-Tsuki)

[cloudiirain]

Discussion Point 1: Web Novels?

• I think it's worthwhile to open this up to web novels, largely because the fan base is larger and there is no "Baka-Tsuki for web novels" (more demand).
• If the app is marketed as a web novel host, we are not limited to published light novels, meaning there would be a stronger defense against site-wide DMCAs (because some web novels are translated with full permissions with rights, etc)

Discussion Point 2: Organization by Volumes?

• If WN are included, organization of chapters by volume should be optional.
• I left out volume-based organization of chapters in this set of requirements because it's a complexity that doesn't return that much benefit. It's entirely possible to do what the manga aggregators do and just have a long linear list of chapters.

Discussion Point 3: Can contributors specify that their translation be mobile-only?

• Some translators may not be willing to have their translations hosted somewhere else on the Internet, since they receive ad revenue on their personal sites. However, they may be more amenable to a service that delivers their translations on a mobile app/offline.
• Taking series off the web and making it mobile-only is another way that a translation can escape visibility from the spider crawlers on the web... just saying it's an option.

Discussion Point 4: What happens if there is more than one version of a chapter, by multiple translation groups?

• Just posing the question. From a mobile app perspective, it's nice to be able to click "Next Chapter", but how do we define this if the chapters are all not linear?

[cloudiirain]

Discussion Point 5: What is the long term vision?

• For instance, do you imagine this being more of a host (where translators post finished translations) or more of a collaboration software (translators/editors use the app as a form of Google Docs, and keep drafts/WIPs)?
• If it's the former, then this set of requirements is probably sufficient
• If it's the latter, then I can expand on a larger set of ideas on what would make a translation/collaboration community nice/great

[Fuyukai]

smh >not even using labels to pretend youre a serious project