Comments

webchick’s picture

Title: {META] Evaluate Drupal Gardens UX improvements for inclusion in Spark » [META] Evaluate Drupal Gardens UX improvements for inclusion in Spark

Damn you, sneaky curly braces.

webchick’s picture

Issue summary: View changes

x

webchick’s picture

Issue summary: View changes

x

webchick’s picture

Issue tags: +Drupal Gardens
webchick’s picture

Issue summary: View changes

x

lightsurge’s picture

Are some of those screenshots then of Gardens? I thought they were mockups...

If you want involvement from the community here, wouldn't it make sense to open source (part of?) Gardens, rather than everyone not in Acquia trying to reverse engineer how a UI like #1586404: Revamped WYSIWYG designs was accomplished and how it could be built upon / improved upon for Spark? Or is there some technical reason Gardens can't be open sourced?

In any case, if tons of UX enhancements have already gone into Gardens that Spark is going to incorporate, there's a sense of it being a bit futile for the community to contribute in certain areas of this project until these enhancements have been published for them to review.

webchick’s picture

Drupal Gardens is basically open source, apart from the theme builder and maybe a small handful of other things. You can export any Drupal Gardens site and get the code + files + database in an archive to host elsewhere if you want: http://www.drupalgardens.com/documentation/site-export

I'm not yet sure how many (if any) of these improvements from Gardens we'll roll into Spark. I just wanted a convenient place to catalog them so it was public knowledge the places where Gardens has improved/iterated on D7's stock UX. In terms of Spark, the issues that are "critical" or "major" in this queue are the places we're focusing on first so are good places for the community to contribute and chime in!

webchick’s picture

Issue summary: View changes

x

webchick’s picture

Version: » 7.x-1.x-dev
Issue summary: View changes
Status: Active » Closed (works as designed)

We're trying to stay as close to core as possible, so that means we're not going to get to this stuff, unfortunately.