Beebox proposes three different types of projects. Each is designed for a specific use case.
| Panel |
|---|
Regular 1. Regular ProjectsLeverages all the linguistic capabilities of Beebox. With each file, Beebox extracts content, segments, pre-translates and optionally machine translates. Only new or changed content down to sentence level are (optionally) forwarded to a translation team. When to use - High volume translation
- High speed translation
- Localization teams
- Game development teams
- Software development teams
- Work reception via FTP / File shares / API
Advantages - Fast and efficient file handling
- Can translate by itself (using memories/machine)
- Makes sure that human teams only get new or changed content
- Link to Wordbee Translator or other TMS (using XLIFF and hotfolders)
- Flexible and customisable workflows
Read more |
| Panel |
|---|
2. CMS ProjectsThe out-of-the-box solution to translate Content Management Systems (CMS). CMS projects work exactly the same way as regular projects but come with a wizard to connect a CMS in a matter of 1 minute. When to use - SiteCore
- Adobe AEM
- WordPress
- Drupal
- Joomla
- Typo 3
- Kentico
- EpiServer
- SharePoint
- SDL LiveContent (coming soon)
- More to come
Advantages - Same features as regular projects
- Supports out-of-the-box CMS connectors
- Develop own CMS connectors (API)
Read more |
| Panel |
|---|
3. Pass-Through ProjectsWith pass-through projects, Beebox sends all new or changed files directly to a TMS (Wordbee Translator). It does not extract content, pre-translate or do other content operations. Advantages - Permits file post-editing workflows in TMS
- Delegates all content extraction to TMS
- Delegates all pre-translation to TMS
When to use - This project type is for niche the special use cases. : For example to connect a document management system such as a Sharepoint and where post-editing of files in the TMS is required.
- You can use PT projects for any content source including FTP, web shares and CMSes.
Read more |
...