[TYPO3-team-core-v5] Re: GSOC: Neos SiteKickstarter & FluidBuilder

[Jacob Floyd]

Brilliant. I used Templavoila for that same reason.

So, the ideal template builder has these main features so far. I want to the ideal vision in my head, and then we can select which parts are ffeasible for me to do as a GSOC project

* A templavoila-esque html -> fluid template converter (ideally something you can revisit) [for an integrator]
** Import a template that consists of HTML/CSS/Images (provided by a the designer)

** If this is for a new fluid template
*** Provide the templavoila-esque gui to help the user choose which parts should be templates, layouts, or partials
*** Let user replace parts of the template with widgets and other common UI sections/elements (ViewHelpers)

** If you are updating a fluid template that was created with the template builder:
*** provide some kind of diff between new and old to help the integrator focus on what has been updated
*** That way, if it's just one partial that was updated, ask the user if that's the only update
*** If the user would like to rework the division of template/layout/partial, then let them edit at will.
*** This might have something to highlight which partials or layout sections have become orphans in the update

** Then let them drop into some kind of fluid editor

* Provide a wireframe-based template builder if the user doesn't want to upload a ready made template (they're not working with a designer)
** The user could choose a wireframe template based on a set of popular frameworks:
Twitter Bootstrap (fixed of fluid), HTML5 BoilerPlate, and others that could be added by new packages
** The user can drag and drop widgets and common UI elements (ViewHelpers) into their template (eg a Menu or a login box)
** The user could choose some alternate colors (maybe through a form that triggers a less or a sass update)
(bootstrap uses less; we could run less either in the browser or, if the user has installed the right package, on the server side)

So, I would imagine that each set of wireframe-templates would reside in its own package (eg in the Twitter.Bootstrap package, or H5BP.Boilerplate ...). They would also include the appropriate forms for the color editing section, if they are setup to be re-colorable.

I'd also like to see a way to go into some kind of editor-like interface to edit the Fluid, HTML, CSS (LESS, SASS), TypoScript...

Speaking of TypoScript, as we divide a template into the fluid sections, we'll want a way to create the TypoScript that accompanies it. The TypoScript will probably use a set of snippets to create the root typoscript, and then we'll also need to give a user a way to say something should be a TypoScript object instead of a fluid partial. Then, wherever the user can add a widget, they can also renderTypoScript.

How's this looking so far?