Posted by sylvain_a on September 14, 2011 at 3:44pm
4 followers
Jump to:
| Project: | Documentation |
| Component: | Missing documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | pixelite |
| Status: | active |
| Issue tags: | D8MI |
Issue Summary
Within the Working with languages handbook, there is a guide dedicated to i18n.
http://drupal.org/node/133977
Since a lot of submodules are involved, we should have a page for each.
I know this is documented in the Help section, but we should focus on a user perspective, with one or two user case per module.
In my opinion, this should answer the user question "What submodules of i18n should we activate?"
Comments
#1
Added the D8MI tag to link this to other tasks related to the Multilingual Sprint currently happening in Montreal (of which Documentation is a sub-team)
#2
The submodules are:
- block translation
- field translation
- Multilingual select
- path translation
- string translation
- synchronize translations
- Multilingual content
- multilingual forum
- contact translation
- translation redirect
- translation sets
#3
I've added all subpages except:
- multilingual forum
- contact translation
- translation redirect
- translation sets
I've marked some as incomplete and some as 'Needs Technical Review'. So far, I didn't touch the Multilingual Taxonomy or Menu Translation pages, which need some attention as well.
#4
While I think having some page to document a list of submodules with a better description of what each of them provides is fine, I'm not that sure we should document the functionality module per module.
I'd rather have pages like 'Translate your taxonomy' 1. Enable the module 'Taxonomy translation'... (which btw is not on the list)
I think for user documentation we should focus on functionality and features better than modules. Modules come up eventually when we tell the user which modules are needed for this and that feature.
While for the taxonomy case the mapping is quite straight there are some others that are not like i.e. 'Translate labels and descriptions' (fields, menus, i18n_node, etc...)
#5
The 'Menu Translation' and 'Multilingual Taxonomy' pages were already there, but do need updating. I'll think about how to reorganize these pages to make them more feature-focused rather than module-focused. Maybe this could involve renaming 'Submodules' to 'Features' and then rewriting the less feature-driven submodule pages like 'Multilingual Select', 'Multilingual Content' and 'String Translation'.
#6
Ok but in any case I don't think we need the Modules/Features grouping. This doesn't allow people to see what's available at first sight.
#7
suscribing
#8
OK, at this point in time only translation sets is missing from pixelite's list in #3