Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runnable Instance 520 Error #72

Open
SamHasler opened this issue Dec 9, 2015 · 2 comments
Open

Runnable Instance 520 Error #72

SamHasler opened this issue Dec 9, 2015 · 2 comments

Comments

@SamHasler
Copy link

The runnable instance link in the readme shows a 520 error. Could it be replaced with a simpler demo using static files hosted on github?

@cburgmer
Copy link
Owner

cburgmer commented Dec 9, 2015

Good point, I was thinking about something similar today. Technically we want to offer a quick glimpse into the main principle of the library, give the user a feeling what the tool is about. The static site so far demos the UI, but after accepting all test cases there's no way to play around and "fail" a test. We would want to offer the user a way of meddling with the HTML.

One solution for handling this in-page could be by maybe storing the edited HTML into local storage for the test page to pick up?

Any other ideas? Do you feel you have time to come up with something small?

@SamHasler
Copy link
Author

Local storage sounds like a good idea. I think having buttons to put it in
various states with a live editable view of the HTML/CSS would be good.

I may be able to look at this before the new year.
On Dec 9, 2015 4:47 PM, "Christoph Burgmer" notifications@github.com
wrote:

Good point, I was thinking about something similar today. Technically we
want to offer a quick glimpse into the main principle of the library, give
the user a feeling what the tool is about. The static site so far demos the
UI, but after accepting all test cases there's no way to play around and
"fail" a test. We would want to offer the user a way of meddling with the
HTML.

One solution for handling this in-page could be by maybe storing the
edited HTML into local storage for the test page to pick up?

Any other ideas? Do you feel you have time to come up with something small?


Reply to this email directly or view it on GitHub
#72 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants