Toura/mulberry — Issue #192: Mulberry scaffold should support creation of an empty project or one from the "Toura" template
Author: MattRogish
Created: 2011-12-11 21:51:23+00:00
State: open

It seems Mulberry should support scaffolding (nb: doesn't have to be under "scaffold" command, this is used just for familiarity and does not specify any particular implementation) an "empty" app (no template, theme, components, routes, etc.) or one that closely matches the "Toura" look-and-feel, components, themes, etc.

The "Toura" look and feel should be copied into their project in such a way that would allow users to tweak/modify them as necessary.

It would also need to support "upgrading" to new releases of Mulberry, much like you have to run `rake rails:update ` in rails apps to upgrade.

This upgrade would have to support both empty and 'toura' apps; rails update works in such a way that prompts you to overwrite files; it's up to you to use something like git to do a diff and make sure it didn't break anything. If the app is a "Toura" app, it would replace the contents of files with new ones (nb: what happens if we delete a default file?); if the app is a non-toura it should "know" and do the right thing.

This would probably mean that themes, components, templates, routings, etc. are stripped from Mulberry core and instead placed in some sort of neutral "project" (nb: hate the overloading) directory, to be copied into an app at the appropriate time.

This would also imply that the theme update rake task would go away, merged into the one uber upgrade task.