Talk:Drupalapps: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== status == | |||
I've pretty much written off d8, clients may commission work with it, but should the notion of going beyond d7 be worked to completion it will be with d9 or greater. | |||
C-Liu is refocused to just be straight d7 for DS plus the current module sets for general/interactive and e-commerce, respectively. | |||
[[User:Root|Root]] ([[User talk:Root|talk]]) 10:00, 24 March 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. | ||
