René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Ensure stylistic consistency across all exercises","articleBody":"All of the copy and code in exercises should conform to a style guide.\n\nFor the JS code, we should just pick a style guide and use it.\n\nFor our own copy and \"starter code\", we should enforce some basic principles. Rules can be discussed in the comment thread here and then added to this description before being ported to an official document.\n\n---\n## JavaScript Exercises Style Guide\n\nAll exercises should live in their own, executable `.js` files.\n\nThe core mechanic of the exercises is to replace missing parts of a script so that it performs as specified in a use case.\n\nMissing parts of a script must be identified by four (4) consecutive underscore `_` characters, as in this example:\n\n``` javascript\nvar ____ = ____(sentence) {\n  return ____._____(____, ____);\n};\n```\n### Environmental constraints\n#### Command line execution with node.js\n\nTest cases must be written at the bottom of the file and wrapped in a `if (!module.parent) { ... }` block.\n#### Single page in browser\n\nMust provide students with a functional skeleton of an HTML file to open in their browser.\n\nTest cases should be written as either:\n- Statements to be executed from the browser's JS console\n- Code wrapped in a `\u003cscript\u003e` tag which produces either a visual result (i.e. changes the DOM) or logs messages to the console\n#### Multiple pages in browser\n\nMust provide students with functional skeletons of all source files.\n\nAll source files must be enclosed in their own named directory.\n","author":{"url":"https://github.com/tannerwelsh","@type":"Person","name":"tannerwelsh"},"datePublished":"2014-12-01T15:02:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/10/javascript-exercises/issues/10"}