Demo Environment Needed

I second mgifford on that!

+1!

Regards

+1 I would like to assess the accessibility of the inline edit

Yeah, now that there's starting to be stuff to show, we should prioritize this.

Next week I'm supposed to be on vacation, so I'll try and get to it the week after.

Ok, as of this sprint, we should have some stuff coming together. Escalating this to major.

Tracking this in OP-7494 in Acquia's tracker.

http://sparks.network.acquia-sites.com/ ... working on getting user accounts set up and a deployment process.

@webchick, thanks. Can you please also see if any test cases currently exist, or should I create a new issue for that?

Test cases for Spark-related things won't exist, because it's primarily front-end/JS stuff and we don't have a way of testing that with SimpleTest/testbot. :(

Postponing on #1718532: Roll a Spark alpha4 release.

Alpha3 has been released, setting back to active.

This is now a critical issue, but we need to roll one more release first: #1718532-3: Roll a Spark alpha4 release. I'm really hoping this can be done by beginning of next week.

This is happening very soon now — hurray :)

@Webchick

I was more thinking manual functional test cases, e.g.

Test inline edit
1. Install the profile
2. Create a node of type page
3. Add some information and save the node
4. View the node
5. Do foo expect bar

Oh, gotcha. Like a demo script. I need to make one of these anyway for Munich so I'll just post it in the issue when I'm done.

Got a new fancy domain name! :D wiring thins up and throwing alpha4 on there is officially on my to-do list tonight.

:)

OKAY!!

Demo site at http://demo.sparkdrupal.com/

Testing instructions at http://drupal.org/node/1728848

I did my best to describe how things are positioned and what they look like for your benefit, Everett. Some things I know for a fact won't work, like the responsive layout builder (but the way it was constructed we can easily have an alternate interface where someone could enter raw values). If you find other areas that are inaccessible or have suggestions on how to make things more accessible, please let us know!!

Marking fixed. WHEW. Sorry for the delay.

Where (if anywhere) do you want feedback of the demo site in particular (as opposed to edit/layout)?
For example, it strikes me the login block position could use some work.

EDIT:
Okay, a lot of things seem heavily broken. I'll give a bit more fiddle time before critiquing.

I'd say: all components of Spark, so: Edit (including WYSIWYG), layout stuff (which currently spans many modules: gridbuilder, layout …), Ember and hopefully soon also a new toolbar that's compatible with mobile devices.

Hm. That's a good question. I guess a disadvantage to a public demo server is now everyone and their dog is going to play with it and make a mess. ;) So we'd really only be interested in bugs that are about Spark alpha4 "proper" and not "someone put a dirty limmerick on the demo site." :)

But when in doubt, go ahead and report it to the Spark queue, and we can triage and move it to the proper queue as needed. Thanks for testing!

FYI, the demo server was updated to the alpha5 release tonight. Enjoy!

Er, The demo site is nice and all. But how does one log in? I applied for an account, but shouldn't there be an open account like demo/demo?

The user/pass is on the testing instructiosn at http://drupal.org/node/1728848. As part of #1738384: Demo site should look less broken for first time visitors I'll look into adding a block or something with this information on the demo site itself.