Talk:Drupalapps: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
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. | ||
