10 | | ''Delivers a D7 Panopoly-based site based on TN's own new distribution, with component/plugabble (initiative) widget system, internationalisation capabilities.'' |
| 7 | === Research tasks === |
| 8 | * UNDERWAY: Investigate I18n & related language/internationalisation modules & best practice -- see https://drupal.org/node/133977 |
| 9 | * POSTPONED: Resolve tension/shortcoming in nested Drush Makefiles causing module dupes between /profiles/modules and /sites/all/modules - https://drupal.org/node/1006620 |
| 10 | * DISCOVER: If a module or interface exists for handling multi pages with workflow type progresssions -- CTools has part of this already. |
| 11 | * DECISION (Jim): Establish whether to use existing, standard Panels renderer or customise new one for working with Widgets. |
| 12 | * DECISION (Jim): Use current page manager or extend based around Widget Instance and Framework concepts. |
12 | | === Progress === |
| 14 | === Plan === |
| 15 | Estimated time in hours in brackets. |
| 16 | |
| 17 | 1. (2) Build stub code for the CTools content types (panes, workflows) needed to behave as template/documentation source. |
| 18 | 1. (1) Create wireframe panes to test workflow progression though pages. |
| 19 | 1. (4) Create views panes (search, listing, display, about). |
| 20 | 1. (1) Expose Widget Instance entity to Panels/CTools as a context. |
| 21 | 1. (3) Create panel from panes and instances created so far. Add placeholder strings and deliver to Ed to get sign off and translated into Portuguese. |
| 22 | 1. (4) Build stub Widget Instance entity and part of related UI for viewing/managing them. |
| 23 | 1. (1) Convert and update Drupal Features and modules. |
| 24 | 1. (2) Set up test site on Jim's server -- allows us to set up Hybrid Auth social media login |
| 25 | 1. (3) Create very simple Bootstrap-based theme (little/no customisations) |
| 26 | |
| 27 | === Other key tasks === |
| 28 | 1. Convert code so far into better structure (core, initiative, registration etc), reusing PSE widget code where possible |
| 29 | |
| 30 | 1. [8] Begin/convert new Widget modules (core, initiative, registration etc) -- see |
| 31 | 1. [8] Enable French language and translate some key bits with Google Translate. |
| 32 | 1. [32] Convert D6 widget modules & features to D7 per [[IIRS/SolutionDesign]] |
| 33 | 1. [4] Create 'Hub Profile' on clone (STG?) of D6 TN.org containins basic text, country, language and widget displays. |
| 34 | 1. [8] (Ben?) Update widget HTML/CSS/theme as needed. |
| 35 | 1. [2] Add Services related modules as needed |
| 36 | 1. [8] Update all views, panels, features to handle language context. |
| 37 | |
| 38 | === Nice to haves === |
| 39 | These are a secondary goals that are nice to haves, but the IIRS widget with internationalisation and associated (syncing) directory is the primary goal... To do if we have time, Ed to prioritise as needed. |
| 40 | 1. [4] Debug & improve Hub install profile. -- |
| 41 | |
| 42 | '''Expected total: 12.25 +/- 5''' (= 98 - 140 hrs) |
| 43 | |
| 44 | == Beta (? October) == |
| 45 | |
| 46 | ''Delivers a cleaned/tweaked up system and some web services connections back to the D6 site, plus an installed and integrated beta website.'' |
| 47 | |
| 48 | 1. [12] Fix bugs/do tweaks |
| 49 | 1. [32] Add Services to sync between D6 <--> D7 sites (and future hub sites) with resilient queuing, plugable architecture |
| 50 | 1. [12] Test, tweak, prep Beta, install, integrate |
| 51 | |
| 52 | ''Subtotal: 6.5 +/- 3 days'' (= 52 - 76 hrs) |
| 53 | |
| 54 | '''Total: 18.75 +/- 8 days''' (= 150 - 216 hrs) |
| 55 | |
| 56 | NB: from Ed - Jim - your '''total''' time budget is 150 hrs. This gives us 3 days with a second programmer in beta phase (agreed as good idea). Bear this in mind! |
| 57 | |
| 58 | |
| 59 | |
| 60 | == Development Log == |
| 61 | ==== Notes ==== |
| 62 | * Hours in [square brackets] is an estimate, (hours in normal brackets) on done items is time actually spent. |
| 63 | * '''21.5 hours''' already spent on design, meetings and documentation |
| 64 | |
62 | | * UNDERWAY Investigate I18n & related language/internationalisation modules & best practice -- see https://drupal.org/node/133977 |
63 | | * UNDERWAY Resolve tension/shortcoming in nested Drush Makefiles causing module dupes between /profiles/modules and /sites/all/modules - https://drupal.org/node/1006620 |
64 | | |
65 | | |
66 | | |
67 | | === To Do === |
68 | | |
69 | | 1. [8] Begin/convert new Widget modules (core, initiative, registration etc) -- TO BREAK DOWN ONCE UNDEWAY |
70 | | 1. [4] Debug & improve Hub install profile. |
71 | | 1. [1] Set up test site on Jim's server -- allows: |
72 | | a. [3] R&D Add & set up Social media login/integration, convert basics to feature. |
73 | | 1. [3] Create very simple Bootstrap-based theme (little/no customisations) |
74 | | 1. [8] Begin/convert new Widget modules (core, initiative, registration etc) -- see |
75 | | 1. [8] Enable French language and translate some key bits with Google Translate. |
76 | | 1. [32] Convert D6 widget modules & features to D7 per [[IIRS/SolutionDesign]] |
77 | | 1. [4] Create 'Hub Profile' on clone (STG?) of D6 TN.org containins basic text, country, language and widget displays. |
78 | | 1. [8] (Ben?) Update widget HTML/CSS/theme as needed. |
79 | | 1. [2] Add Services related modules as needed |
80 | | 1. [8] Update all views, panels, features to handle language context. |
81 | | |
82 | | '''Expected total: 12.25 +/- 5''' (= 98 - 140 hrs) |
83 | | |
84 | | == Beta (? October) == |
85 | | |
86 | | ''Delivers a cleaned/tweaked up system and some web services connections back to the D6 site, plus an installed and integrated beta website.'' |
87 | | |
88 | | 1. [12] Fix bugs/do tweaks |
89 | | 1. [32] Add Services to sync between D6 <--> D7 sites (and future hub sites) with resilient queuing, plugable architecture |
90 | | 1. [12] Test, tweak, prep Beta, install, integrate |
91 | | |
92 | | ''Subtotal: 6.5 +/- 3 days'' (= 52 - 76 hrs) |
93 | | |
94 | | '''Total: 18.75 +/- 8 days''' (= 150 - 216 hrs) |
95 | | |
96 | | NB: from Ed - Jim - your '''total''' time budget is 150 hrs. This gives us 3 days with a second programmer in beta phase (agreed as good idea). Bear this in mind! |
| 117 | * Decision taken to not include panopoly |