Examples of things we'd like MakeDrive to be able to support:
* MVP User Story: creating and editing an AppMaker component. Luke wants to create a Button component. He creates a new project, ''button-component'' and the following files:
<pre>
component-button/
component.html
README.md
style.css
</pre>
He works until he's happy, and saves his work. Later he goes to AppMaker and is able to try his component using the following URL:
https://drive.webmaker.org/components/component.html
This allows Luke (and only Luke) to preview his new component in AppMaker. Later, after editing and fixing bugs, he decides to publish his component. He now shares his work via makes.org:
https://luke.makes.org/components/component.html
He later finds a bug and fixes it, and his public component has the new fix.
* Jen has never used Webmaker before. She visits nimble.webmaker.org and sees an editor with an index.html page. She is able to make changes and save them. After editing this page for a while, she decides to publish it, and claims jen.makes.org, where her new page is now visible.
* A few days later, Jen decides to add an image to her home page on jen.makes.org. She goes back to nimble.webmaker.org, and is able to open her existing work. She drags-and-drops the image into the editor, and it gets "uploaded".
* At work the next day, Jen sees an animated gif that she wants to add to her page. She uses her work computer to visit nimble.webmaker.org. She is able to sign-in and her files appear, where she adds the gif, saves, and publishes, before sharing the link to her jen.makes.org/ page with her colleague.
* Claudia has created many web components for AppMaker using Nimble. While attending a hackathon, she decides to create a new one by using one of her old ones as a template. She doesn't have Internet access at the event, but is able to open nimble.webmaker.org, find her old component, and save it with a new name, before editing it. She uses Nimble's built-in web server (nohost) to preview and demo her work at the event.
* Wei is traveling and has an afternoon to kill. He visits a local library, where he has a great idea for a web page that shows a map of where he's been along with some photos. He visits nimble.webmaker.org, and specifies that he's using an untrusted computer. He is able to access his old files, where some of his images live. He creates a new web page, uses a Map API in JS, saves and publishes everything before emailing his friends the link to his make. When he's done he closes the browser he's been using, which deletes all the files he was accessing locally (they are saved in Webmaker's server).
* Hope is at her brother's house. He's working on a project for school, and struggling to get a piece of JavaScript to work. Hope knows she's done something similar in the past, and pulls out her phone. She's able to view her old Webmaker files using MakeDrive, and finds exactly what she wants. She shares a URL with her brother, and he's able to open her JS file, and they use it to solve his problem.