| 11 | | 2. New work will be in Drupal 7 as unfortunately Drupal 8 is not stable at present. |
| 12 | | 3. The current D6 site will still be the 'king', but this work will be designed to grease the wheels of move to D7 sometime in the next year (or two). |
| 13 | | 4. There will be a web service connection between the current D6 and the new, slim D7 site. |
| 14 | | 5. Adding new code to an already big Drupal 6 site should be kept to a minimum, and service connectections should be lean and 'gentle'. |
| 15 | | 6. We will create a new, slimline Initiative content type to store the data from the widgets. |
| 16 | | 7. We will re-use/retool/refactor the D6 Projet Widget code to get a quick jump on the core widget features. This is essentially a cleanup and conversion from D6 to D7. |
| 17 | | 8. Internationalisation is a BIG part of this, as is facilitating the translation of TN-specific parts of the UI and content. |
| 18 | | 9. These are not the only principles, more to follow... |
| | 11 | 1. New work will be in Drupal 7 as unfortunately Drupal 8 is not stable at present. |
| | 12 | 1. The current D6 site will still be the 'king', but this work will be designed to grease the wheels of move to D7 sometime in the next year (or two). |
| | 13 | 1. There will be a web service connection between the current D6 and the new, slim D7 site. |
| | 14 | 1. Adding new code to an already big Drupal 6 site should be kept to a minimum, and service connectections should be lean and 'gentle'. |
| | 15 | 1. We will create a new, slimline Initiative content type to store the data from the widgets. |
| | 16 | 1. We will re-use/retool/refactor the D6 Projet Widget code to get a quick jump on the core widget features. This is essentially a cleanup and conversion from D6 to D7. |
| | 17 | 1. Internationalisation is a BIG part of this, as is facilitating the translation of TN-specific parts of the UI and content. |
| | 18 | 1. These are not the only principles, more to follow... |
| | 19 | |
| | 20 | == Scary questions == |
| | 21 | 1. What will the experience be for each type of user on each environment... |
| | 22 | ||= =||= TN.org D6 =||= D7 widget =||= D7 site user =|| |
| | 23 | || Widget user || || || || |
| | 24 | || Widget/ini moderator || || || || |
| | 25 | || Widget translator || || || || |
| | 26 | || Visitor UK (English) || || || || |
| | 27 | || Visitor France (French) || || || || |
| | 28 | || Visitor Canadian (French or English) || || || || |
| | 29 | || Visitor Botswanian (Setswana, example of no translation) || || || || |
| | 30 | || TN admin/editor || || || || |
| | 31 | || National hub admin/editor || || || || |
| | 32 | || Translators || || || || |
| | 33 | |
| | 34 | 2. How will translated content get back to the D6 site [assumes it's done on D7, which is the best place for editors if not the system]... It's one thing to make templates and panels layouts, but how is that edited? |
| | 35 | 3. |
