IIRS Solution Design

Please refer to the IIRS/ArchitectureOptions and principles therein.

Features overview

The IIRS will be an add-on service with its own Drupal 7 install. This install will provide the means to:

1. Initiatives: A slimline Initiative content type, related views and maps etc that are synced with TN.org D6.
2. Users: Allow users to log in (to their accounts on the current D6 site), or register (with the new account synced back from D7 to D6).
3. Widget: Add, Edit (with correct perms), list/map initiatives and view single initiatives via a widget.
4. Sync: post-moderated (pre-accepted) D7 initiatives back to TN.org D6 via a web service, AND from D6 to D7 as edits happen there.
5. Hub: Store 'National Hub profiles' that facilitate the translation and syncing of the UI and data.

Drupal 6 site changes

1. New content type: "Transition Hub" - represents the key information about the hub and widgets that will provide content in that language. Has language, country, translated intro text, points of contact, and remote (D7) path for services.
2. New Panels layout for "Transition Hub" content type: Shows key (translated) text in panels layout, below which is a full-page widget showing lists and maps of Initiatives, with the option to view them IN A POPUP in the Hub language. This panel should ideally pre-display the widget using variables from the Hub profile.
3. Services for syncing user accounts, Transition Hub and Initiative profiles nodes automatically on edit, delete (unpublish) and 'provision' to get the D7 site the content it needs.

Drupal 7 site features

Distribution, Profile, Frameworks

1. Based on ​Panopoly for an excellent editorial experience out of the box. There is a lot of momentum around Panopoly in the Drupal world.
2. Theme based on Twitter's ​Bootstrap (v2.3.2) framework for a cross-browser, responsive, clean and deeply sexy starting point. There's loads of good resources and tools on the web for Bootstrap.
3. Lots of Drupal themes integrate with Bootstrap, but ​Radix is also gaining a lot of traction with distributions and works great with Panopoly, Open Atrium, Open Outreach and others.
4. [​Debut will provide as much base features as possible, to minimise custom code and get a fast start on key features. For now these are not needed for content types, but standardising around other features will make future development and integration with other Drupal sites easier. Recommended for consideration: ​Membership, ​Location, ​Social, ​WYSIWYG
5. Will create a 'Transition National Hub' Drupal install profile to allow this site to be built easily on the Transition Network server, and indeed on other interested parties systems.

Transition-specific custom Features & modules

@todo convert to table and list if each is able to be re-used for D6, D7 IIRS or D7 TN.org @todo create a diagram to show what features sit where, and what depends on what...

1. Transition Network Core - a feature wrapping all shared dependencies and extras needed to make the site(s) tick.
2. Transition Initiatives - a feature wrapping up a content type, some simple list-style views (user-facing and admin) and panels panes.
3. Transition Initiatives Widget - a module providing the widget (converted from the ​D6 PSE project).
4. Transition Users - a feature wrapping up a basic user account, plus some views (users-facing and admin). Need to decide if this is core D7 accounts, or needs Profile2 etc.
5. Transition * Services [where * is 'intuitive', 'user' etc.] - a feature for each core piece of data that contains relevant services including CRUD, views/lists and probably authentication.
6. Transition National Hub - anything specific to national hubs goes here. Each 'Hub' content represents a national hub and has language(s), name, country, website and other data.
7. Transition Network Sync - a module that uses pluggable services (ini, user, project etc) to sync data back to the 'hub' D6 TN.org site.
8. Transition Translate - a feature/module that helps manage the translation of site content into various languages.
9. ...

Web services

@todo see what the ​Services module does out the box.