Talk:Drupalapps: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Update == | |||
See earlier versions for evolution, working experience with drupal prior to 2019. [[User:Root|Root]] ([[User talk:Root|talk]]) 00:41, 23 December 2018 (UTC) | |||
== moved ¶ == | == moved ¶ == | ||
The prototypical business case for C-六 adaptations is that of a single central metaphor around which the application is designed as in the case of the wireframe app DTBSNS², a geographic info application, etc., the desire to use one or more of the integral packages, a new one using the integration framework, or to migrate and free a preexisting form entanglement in a proprietary SaaS like Ning or Volusion (using some real cases). Of course in general a central widget or single use case does not make a functioning enterprise but concentration on this model will serve to bring some clients, with limited budgets, to their intended system targets and provide a basis for further funding and development. | The prototypical business case for C-六 adaptations is that of a single central metaphor around which the application is designed as in the case of the wireframe app DTBSNS², a geographic info application, etc., the desire to use one or more of the integral packages, a new one using the integration framework, or to migrate and free a preexisting form entanglement in a proprietary SaaS like Ning or Volusion (using some real cases). Of course in general a central widget or single use case does not make a functioning enterprise but concentration on this model will serve to bring some clients, with limited budgets, to their intended system targets and provide a basis for further funding and development. | ||
Latest revision as of 16:41, 22 December 2018
Update
See earlier versions for evolution, working experience with drupal prior to 2019. Root (talk) 00:41, 23 December 2018 (UTC)
moved ¶
The prototypical business case for C-六 adaptations is that of a single central metaphor around which the application is designed as in the case of the wireframe app DTBSNS², a geographic info application, etc., the desire to use one or more of the integral packages, a new one using the integration framework, or to migrate and free a preexisting form entanglement in a proprietary SaaS like Ning or Volusion (using some real cases). Of course in general a central widget or single use case does not make a functioning enterprise but concentration on this model will serve to bring some clients, with limited budgets, to their intended system targets and provide a basis for further funding and development.
Maintenance affecting this area
A main server supporting these domains and in service for a few years had a fs corruption and intrusions on several of the drupal sites so some have been taken offline. The stuff in the main line of CLiu dev will be restored on the new server before April 1. Root (talk) 13:41, 16 February 2015 (UTC)
- The (former) square bracketed links have been decommissioned/removed (some earlier). The broken ones will be fixed per the above, noting that the d7 derivative I'm developing in my day job is the best instance right now, will be addressing performance as main feature with d7/8 bridging in C-Liu later this (Western) year. Root (talk) 14:56, 16 February 2015 (UTC)
