Adding Thimble projects: the hard way

Manual curation

For the moment (until #229 gets closed), adding projects to Thimble and the Thimble website is somewhat of a manual process. These are the steps as I understand them:

1. Initial creation: * project gets developed in dropbox, paying attention to this and this * creator checks for errors (visual flaws & Thimble errors) at both:

   • http://wpm-dev.org/projects/dropbox/{PROJECT_NAME}
   • http://wpm-dev.org/projects/dropbox/{PROJECT_NAME}/edit * where {PROJECT NAME} is the folder name in dropbox

2. Productionalize it: * an issue is created in webpagemaker github issue to "productionalize" the project * assign to an engineer

3. Slurp it: * engineer imports the project into git * engineer modifies site pages to list the project * and looks it over for errors, kicking back to creator if needed

   • fixes to the project should be done in dropbox and slurped, or you'll blow them away on next slurp

4. Pull request: * pull request is issued to mozilla/webpagemaker * and gets reviewed by a different engineer, who hopefully looks it over for errors, kicking back to the project creator or pull requester as needed

5. Merge: * once pull is merged, the project is available on dev at:

   • http://wpm-dev.org/projects/{PROJECT_NAME}
   • http://wpm-dev.org/projects/{PROJECT_NAME}/edit * and gets QA'd by some non-engineer responsible for the project

6. Move to prod: * upon final ok, someone somehow moves it to staging and production

   • someone who knows should fill in the details here