Skip to content
This repository has been archived by the owner on Sep 9, 2019. It is now read-only.

Demo site #24

Open
fureigh opened this issue Dec 7, 2015 · 5 comments
Open

Demo site #24

fureigh opened this issue Dec 7, 2015 · 5 comments

Comments

@fureigh
Copy link
Contributor

fureigh commented Dec 7, 2015

Capturing @iris-i's suggestion that a demo site could be helpful for developers and otherwise. @iris-i, are you game to fill in a user story and any other info here?

@iris-i
Copy link

iris-i commented Dec 14, 2015

Sure!

  1. As a developer and potential end user, I would like to see a demo site built with the theme, so I can try out the USWDS components in drupal before downloading.
  2. As a non-technical (government) end user, I would like to see a demo site, so I can confirm that the themes adhere to accessibility standards, before adopting either one for my project.

I wondered if a simplytest.me link would do in lieu of a demo site, but I feel like the web standards will be better showcased with relevant content.

@fureigh
Copy link
Contributor Author

fureigh commented Dec 14, 2015

Excellent, thanks for writing those out!

I second your conclusion that a demo site is probably more suitable than a simplytest.me link. By default the simplytest sandboxes last only 24 hours, and it seems contrary to the intent of the site to request an indefinite extension for purposes of demoing rather than testing per se. Furthermore, I suspect end users who aren't as comfortable with Drupal site administration will be much more comfortable being able to see a "finished product." Perhaps we can suggest simplytest.me in the documentation or on the project page, though, so developers who are more comfortable know they can easily give it a test run.

@kevwalsh
Copy link

@fureigh hey Fureigh do you have an idea about hosting options for this? CivicActions could host temporarily, or even long term. We might set something up for this week.

@kevwalsh
Copy link

this is a big enough task that it might merit an issue queue label and a number of different issues. Perhaps this issue can be an epic, with sub issues?

We've taken the basic user stories written by @iris-i in #24 (comment) and blown them up into a user story map, see attached.

We've also drafted some content. https://docs.google.com/document/d/1Z-x5IjeDq3bHK_DVPkvv3XcFZzuLNHHiRWG4nUAcz6E/edit

And chuck is mocking up a demo site.

I'm working on some of the site building tasks right now.

uswds_theme_and_demo_site_storymap_-_storiesonboard

@fureigh fureigh added the epic label Dec 17, 2015
@fureigh
Copy link
Contributor Author

fureigh commented Dec 17, 2015

@kevwalsh This all looks great!

Feel free to go ahead and host the demo site on at least a temporary basis. Thanks!

I created and applied an epic label per your suggestion. Subissues will be linked here automatically and can be organized

  • with
  • checkboxes
  • if you'd like.

Everyone should have access to create issues in this repo. If that's not the case, or if you have any questions, let me know.

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

No branches or pull requests

3 participants