Changes between Version 7 and Version 8 of IIRS/ArchitectureOptions

Timestamp:

08/21/13 14:03:36 (3 years ago)

Author:

ed

Comment:

--

IIRS/ArchitectureOptions

@@ -8 +8 @@
 
 == Principles ==
-1. We must focus on the [[IIRS/widgetPurpose]]: Collecting and displaying initiatives in multiple languages.
+1. We must focus on the [[IIRS/widgetPurpose]]: Collecting and displaying initiatives in multiple languages in an internationalised view
 1. Each additional language is a separate sub-project.
 1. New work will be in Drupal 7 as unfortunately Drupal 8 is not stable at present.
 1. All pages in the new language context will be served from a new D7 site.
-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).
+1. The current D6 site will still be the 'master', but this work will be designed to grease the wheels of move to D7 sometime in the next year (or two).
 1. There will be a web service connection between the current D6 and the new, slim D7 site.
-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'.
+1. Adding new code to an already big Drupal 6 site should be kept to a minimum, and service connections should be lean and 'gentle'.
 1. We will create a new, slimline Initiative content type to store the data from the widgets.
-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 clean-up and conversion from D6 to D7, plus internationalisation and the addition of a new 'view Initiative details' popup.
+1. We will re-use/retool/refactor the D6 Project Widget code to get a quick jump on the core widget features. This is essentially a clean-up and conversion from D6 to D7, plus internationalisation and the addition of a new 'view Initiative details' popup.
 1. Internationalisation is a BIG part of this, as is facilitating the translation of TN-specific parts of the UI and content -- this happens only in D7 though.
+1. Translating elements of the current D6 site is a furtherance of its 'colonial' origins. It is better to focus on core functionality and ensure that is inter-dependently available and local-isable and manage-able by National Hub administrators.
+
+== Assumptions ==
+
+1. That this is a prototype of a complex service offering for an organsiational process, targeted to a specific audience (National Hub people) as part of a growing internationalisation strategy. It is a learning journey and can be scrapped if it does not work, or does not prove desirable for the National Hubs. It is not a finished product. 
+1. One country = one language - for the purposes of 1 and 2 above
+1. That we are working towards a 'shared global directory' of initiatives - NOT trying to aggregate lists of initiatives from different sources
+1. A widget offers a complete 'service cycle' (add/edit/unpublish) for an Initiative and its related User in that language
+1. The context of the web visit defines the language - ie if a French TI item is seen via the French widget, the surrounding language will be French. If a French TI item is seen via the TN.org English site, the surrounding language will be English
+
 
 == Scary questions ==