Changes between Version 13 and Version 14 of IIRS/SolutionDesign

Timestamp:

08/25/13 17:02:54 (3 years ago)

Author:

jim

Comment:

--

IIRS/SolutionDesign

@@ -28 +28 @@
 
 === 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...
 
@@ -39 +38 @@
 
 === Widget design ===
-The widget is to be a more flexible evolution of the work started in [[Sharing_Engine/Technical_Proposal Project Sharing Engine]]. The plan is to build on this base but turn the it into a clear, clean model based on a set of components that can be added, extended and re-used. Since Drupal 7 is not MVC, and neither is Drupal 8, the proposal is to use the CTools Plugin architecture ([http://ygerasimov.com/ctools-plugins-system example here]) to allow new Widget components to be added/enabled over time.
+The widget is to be a more flexible evolution of the work started in [[Sharing_Engine/Technical_Proposal Project Sharing Engine]]. The plan is to build on this base but turn the it into a clear, clean model based on a set of components that can be added, extended and re-used. Since Drupal 7 is not MVC, and neither is Drupal 8, the proposal is to use the [https://drupal.org/project/ctools CTools] Plugin architecture ([http://ygerasimov.com/ctools-plugins-system example here]) to allow new Widget components to be added/enabled over time.
 
 ==== Widget modules ====
@@ -73 +72 @@
 
 ==== Widget Plugins needed ====
-Leveraging CTools, the following plugins are needed for the IIRS... Note that the code for most of these plugins is already written in Drupal 6. What is required is to convert to a standardised component/plugin architecture:
+Leveraging [https://drupal.org/project/ctools CTools], the following plugins are needed for the IIRS... Note that the code for most of these plugins is already written in Drupal 6. What is required is to convert to a standardised component/plugin architecture:
 * Style plugins:
   * Types: "Full page", "Sidebar", "Button only" = Chrome styles we currently have.
@@ -87 +86 @@
   * "Content Search" = A way of searching for [target] by name and location.
   * "View Content" = A popup to display a single [target] Node. Can also show edit options if user has permission. Used for displaying both the Initiative details, and the 'About' and 'Help' pages.
-  * "Log in/Register" = A unified Login/Register form display with Social Media connect options.
+  * "Social Log in/Register" = A unified Login/Register form display with Social Media connect options.
   * "Create Content" = A form to create [target] content, showing only core/required fields).
-* Workflow plugin: "Registered User Create Content" which takes a user though the displays "Log in/Register" -> "Create Content" (for Initiative target) -> "View Content" ('About' page for Initiative target).
+* Workflow plugin: "Registered User Create Content" which takes a user though the displays "Social Log in/Register" -> "Create Content" (for Initiative target) -> "View Content" ('About' page for Initiative target).
 
 === To do (updated 25 Aug 2013) ===